1. Application Interface Services Server Reference Guide
  2. Configuring Multiple AIS Servers (Release 9.2.5)

Configuring Multiple AIS Servers (Release 9.2.5)

You can deploy a single enterprise server for all environments and associate that enterprise server with AIS servers in multiple environments. This configurability facilitates the segregation of AIS servers across environments, such as development, test, and production, while making it possible for a single enterprise server to serve all the environments.

You use the Web Service Soft Coding Records program (P954000) to configure web service soft coding records based on web service soft coding templates. The administrator can create a soft coding record with the AIS_CONNECTION soft coding key.SeeWorking With Soft Coding.

You can also set up these connections using the Orchestrator Studio. See Creating a Soft Coding Record for an Enterprise Server AIS Connection section in the orchestrator guide for more information.

Before Release 9.2.5, the AIS endpoint string was built using the values in AISProtocol, AISHost, and AISPort that are available in the JDE.INI file as shown in the following example:

[FORMSERVICE]

AISProtocol=https
 AISHost=MyAISHost
 AISPort=8001
 AISMaxConcurrentCalls=1

As of Release 9.2.5, the endpoint string is obtained from a table and these three JDE.INI settings are used as a fallback if the data does not exist in the table.

The endpoint string value is read from the F954001 table, column when the value of WSTPNAME column is AIS_CONNECTION. The row used in this process depends on the user/ role and environment of the signed-in user.

This is the hierarchy rule of the soft coding application:

  1. If the user and environment exist in the F954001 table (column UGRP or ENVH, respectively), the system uses the endpoint value in the WSTPVAL column (Template Value field) for that record. If the user and environment does not exist, the system performs step 2.

  2. If the user is signed in for the role *ALL, then the system goes through all the roles in *ALL in a hierarchical order. The system will use the endpoint value in the WSTPVAL column for the first role or environment that exists in the F954001 table (column UGRP or ENVH, respectively). If the user is not signed in to the *ALL role, the system performs step 3.

  3. If the user is signed in using a specific role, and if that role and environment exists in the F954001 table (column UGRP or ENVH, respectively), the system uses the endpoint value in the WSTPVAL column (Template Value field) for that record. If not, the system performs step 4.

  4. If *PUBLIC and environment exists in the F954001 table (column UGRP or ENVH, respectively), the system uses the value in the WSTPVAL column for that record. If *PUBLIC and environment does not exist in the F954001 table, the system looks into [FORMSERVICE] in the JDE.INI file.