Configuring a Web Application for a Pass-through Business Service
This appendix describes how to configure a web application for a pass-through business service. To configure a web application for the Public Service Registry REST API, see “Configuring a Web Application for the Public Service Registry API”.
Create an empty role and assign it to the unknown user as follows:
Select System Administration > Security > Roles to display the Roles portal page.
Select the Create New Role button and name the role, for example, Services_Role, and Select the Save button.
Select the Members tab, select the Unknown User, Select the right arrow, and Select the Assign button.
Define a web application that will handle calls to the Web port. The web application name defines the root of the URL that will call the service. A single web application can support multiple business services but they must all have a class that is the same or a subclass of the web application dispatch class.
Select System Administration > Security > Applications > Web Applications to display the Web Applications portal page. Select the Create New Web Application button.
Name the web application, such as /restpassthrough or /soappassthrough. You must start the name with a / (slash) character. All alphabetic characters in the name should be in lower case.
Set the Namespace to the namespace that the production is running in, such as SERVICESNS. Leave the Namespace Default Application unchecked.
You can check the Application, Web file, and Inbound Web Services check boxes.
Leave the Resource Required and Group By ID fields empty.
Check the Unauthenticated check box on the Allowed Authentication Methods line.
Select the Matching Roles tab.
In the Select a Matching Role: field, select the role that you created in the previous step.
In the Select target roles to add to the selected matching role field, select the role or roles associated with the namespace globals and routines. The globals and routines may be in the same database or in separate databases. If your service, accesses another InterSystems IRIS® database, you should also select its role. You can select multiple roles while holding the Ctrl key.Note:
The globals database also may have a secondary database and a corresponding role, such as %DB_GDBSECONDARY. This secondary database is used to store passwords. You don’t need access to this database for pass-through services and operations, but if you create a custom web service that uses password access, you should also add the secondary database role to the target database.
After the roles are highlighted, select the right-arrow button to move them to the Selected text box.
Then select the Assign button.
If your web application allows both unauthenticated and authenticated service, then it will prompt for a password, but if you do not enter a password, the web applications grants you unauthenticated access.