Configuring a Production for SOAP Services
This appendix briefly discusses how to configure your system so that you can use HTTP and SOAP services through the Web port. This information is intended to help you set up a development or test system for these services. Complete information about these topics is provided in the documentation. See “Configuring InterSystems IRIS®” in the System Administration Guide for more details.
To set up an InterSystems IRIS development or test system for HTTP or SOAP services, follow these steps:
If you have installed InterSystems IRIS in a locked down installation, Studio access is disabled. Open the Management Portal and enable Studio access:
Start the Management Portal from the InterSystems IRIS launcher. You will have to use your Windows login username rather than _system to access the portal. Enter the password that you specified during installation.
Select System Administration, Security, and Services to get to the Services portal page.
The %Services_Bindings service is disabled by default. Select the service name and check the Service Enabled check box and save the setting.
If you are not using an existing namespace, create a new namespace:
Select System Administration, Configuration, System Configuration, and Namespaces to get to the Namespaces portal page.
Click the Create New Namespace button, specify a name for the namespace, such as SERVICESNS.
Click the Create New Database button for the globals database.
In the Database Wizard, enter a name for the globals database, such as SERVICES_GDB. The wizard uses the name to create a directory for the database.
Click the Next button twice to get to the Database Resource form. Select the Create a new resource radio button. The wizard displays a Create New Resource form. Accept the suggested name, such as %DB_SERVICES_GDB and ensure that Public Permissions Read and Write check boxes are not checked. Click the Save button on the Database Resource form and the Finish button on the Database Wizard form.
Repeat steps c through e for the routines database.
Click the Save button to complete creating the namespace.
Click Close to close the log.
Create an empty role and assign it to the unknown user:
Select System Administration, Security, and Roles to display the Roles portal page.
Click the Create New Role button and name the role, for example, Services_Role, and click the Save button.
Select the Members tab, select the Unknown User, click the right arrow, and click 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, and Web Applications to display the Web Applications portal page. Click the Create New Web Application button.
Name the web application, such as /weatherapp or /math/sum. You must start the name with a / (slash) character.
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, CSP/ZEN, 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, click the right-arrow key to move them to the Selected text box.
Then click the Assign button.
This completes the system configuration.