Configuring communication between the order server and promising server

Enabling access to the AuthorizationOnlyApiServlet

To enable access to AuthorizationOnlyApiServlet, edit the web.xml file of the deployed Promising server EAR to include the following:

<context-param>
		<param-name>bypass.uri.X</param-name>
		<param-value>/interop/AuthorizationOnlyApiServlet</param-value>
</context-param>
<context-param>
		<param-name>request.validation.bypass.uri.yfc.X</param-name>
		<param-value>/interop/AuthorizationOnlyApiServlet</param-value>
</context-param>
<servlet id="Servlet_X">
		<servlet-name>AuthorizationOnlyApiServlet</servlet-name>
		<servlet-class>com.yantra.interop.client.AuthorizationOnlyApiServlet</servlet-class>
</servlet>
<servlet-mapping id="ServletMapping_X">
		<servlet-name>AuthorizationOnlyApiServlet</servlet-name>
		<url-pattern>/interop/AuthorizationOnlyApiServlet</url-pattern>
</servlet-mapping>

where
X is a numerical value.

Restricting access to the AuthorizationOnlyApiServlet

To restrict access to the AuthorizationOnlyApiServlet, edit the web.xml file of the deployed Promising server EAR:

<security-constraint>
		<web-resource-collection>
				<web-resource-name>AuthorizationOnlyApiServlet</web-resource-name>
				<url-pattern>/interop/AuthorizationOnlyApiServlet</url-pattern>
				<http-method>GET</http-method>
				<http-method>POST</http-method>
		</web-resource-collection>
		<auth-constraint>
				<role-name>prmsappuser</role-name>
		</auth-constraint>
</security-constraint>
<login-config>
		<auth-method>BASIC</auth-method>
		<realm-name>default</realm-name>
</login-config>
<security-role>
		<role-name>prmsappuser</role-name>
</security-role>

Notes:

• In the above coding, replace prmsappuser with the same user name that was used when creating a new user and group at the application server where the Promising server EAR will be deployed.
• In the above coding, replace default with the realm name of prmsappuser.
• Set up the appropriate authentication mechanism (BASIC, SSL, or CLIENT-CERT) in the <auth-method> tag.

Configuring application servers

Configuring WebLogic

The following configurations have to be made on a WebLogic application server:

1. Make the following changes in the weblogic.xml of IBM® Sterling Order Management System Software EAR.

   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application
   8.1//EN" "http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
   <weblogic-web-app>
   <security-role-assignment>
   <role-name>prmsappuser</role-name>
   <principal-name>prmsappuserGroup</principal-name>
   </security-role-assignment>
   </weblogic-web-app>

   Note: When setting up the Users and Groups, ensure that the user name is the same as that provided in the role-name tag of the web.xml file of the Promising server.
2. Refer to the application server documentation to set up the authentication mechanism that you are using and that is mentioned in the web.xml file.

Configuring WebSphere

1. Ensure that you have a deployment manager with administrative security turned on.
2. Deploy the Sterling Order Management System Software in a server within the deployment manager.
3. In Users and Groups>Manage Groups and Manage Users, create Users and Groups.

   Ensure that the user name is the same as provided in the role-name tag of the web.xml file of the Promising server, and assign them to this group.

4. In Enterprise Applications (Promising Server) > Security role to user/group mapping. WebSphere reads the web.xml file and populates the user role in the table. Map the user role to the group created in step 3.
5. In Security, click Global security.

   Select the Enable application security checkbox.

6. Refer to the application server documentation to set up the authentication mechanism that you are using and that is mentioned in the web.xml file.

Configuring properties on the order server

Configure the following properties in the yifclient.properties file on the Order server and rebuild the resources.jar file before building the EAR file:

Creating and authorizing users

When you run the Promising server Activator in non-enterprise mode on both the Order server and Promising server, an application user, PRMSIntegrationUser, is created with the required permissions to access the Promising server.