Understanding the web script URI

It is important to understand the web script URI. The way the web script URI can be represented in a generic form is http[s]://<host>:<port>/[<contextPath>/]/<servicePath>[/<scriptPath>][?<scriptArgs>]

The terms used in the web script URI are explained as follows:

• http[s]: This is the protocol to invoke the web script. This could be either http or https.
• host: This is the name or address of the server where the web script is deployed.
• port: This is the port where the web script is exposed on the server hosting the web scripts.
• contextPath: This is the path where the application is deployed to. For data web scripts, this would generally be /alfresco.
• servicePath: This is the path where the web script service is mapped with. Generally, this would be /service.
• scriptPath: This is the path to the web script as defined in the web script descriptor document *.desc.xml under the <url> tag.
• scriptArgs: These are the arguments to be passed to the web script as generally defined in the web script descriptor document *.desc.xml under the <url> tag. Arguments can be specified after the web script scriptPath just after ?.

Now you understand the different terms that make up the web script URI, now you can easily understand the URI of our first web script by mapping our web script URI to the generic form of the web script URI. Note that we were not having arguments added to our first web script, hence, you would not be able to map the scriptArgs part. Let's now take a look at what needs to be done to add the arguments to a web script.