1. Server Manager Guide
  2. Create an Application Interface Services (AIS) Server as a New Managed Instance

Create an Application Interface Services (AIS) Server as a New Managed Instance

You must use Server Manager to install a new EnterpriseOne AIS Server instance.

If you are using Oracle WebLogic Server 12.2.1 to host the AIS Server, then you must upgrade the AIS Server and Server Manager to EnterpriseOne Tools 9.2.0.5. You cannot run AIS Server releases 9.2.0.4 and lower on Oracle WebLogic Server 12.2.1.

See also:
Note: Starting with Tools Release 9.2.7, you can select the JAS server while creating an AIS server as a New Managed Instance. The Propagate JAS settings column enables you to choose the JAS server and the settings for JDBj.ini and tnsnames.ora are copied directly from the JAS server to the AIS instance.

To install an AIS Server instance:

  1. Select the Managed Home in which you wish to install the AIS Server.

    AIS Managed Home Location.

  2. Click the Create a New Managed Instance button to create the Managed Instance in the Managed Home.

    AIS Selection.

  3. On Create/Register a Managed Instance, Instance Type, select this radio button:

    EnterpriseOne Application Interface Services

  4. Click Continue.

    AIS Create Input Fields.

  5. On Create/Register a Managed Instance, Instance Properties, complete these fields:

    • Server Group

      Use the dropdown menu to select the Server Group where you want this instance to belong.

      Also refer to Administer Server Groups

    • Instance Name

      Enter a name for the instance.

      Tip: A good business practice is to name your instances so that they are easily and consistently identifiable. For example:PRODUCT_SERVER_PORTwhere PRODUCT is the JD Edwards EnterpriseOne server type, such as JAS, RTE, CollabPortal, AIS, or BusSvcs; where SERVER is the machine on which the instance is installed; where PORT is the HTTP port which is defined for use by this server.

    • J2EE Server

      Use the dropdown to select a valid J2EE server.

    • HTTP Port

      You must ensure that the port that you specify is available and is not being used by any other application currently installed and running on the server on which the application server is running.

      See also:

    • Software Component

      Use the dropdown to select the version of this Software Component that you wish to install.

    • Propagate JAS Settings (Tools Release 9.2.7)

      Use the dropdown to select the JAS instance to propagate the JDBj.ini and tnsnames.ora file of the JAS instance into the AIS instance.

  6. Click Continue.

    This image is described in surrounding text.

  7. On Create/Register a Managed Instance, Confirmation, review the key configuration items. The page displays the settings that are typically required to successfully start your instance. The values on this form must be confirmed manually. You should validate or update, as appropriate, all configuration items.

    Note: When setting up an AIS server instance, you should also review the Allowed Hosts setting for the corresponding EnterpriseOne HTML server instance.
    Tip: For help, click the Information icon next to the title of a field.
    See also: Configure the Default Server Group Configuration Settings

  8. After you have validated and updated all configuration items, click Continue to proceed to the next installation step.

    This image is described in surrounding text.

  9. On Create/Register a Managed Instance, Finish, click the Create Instance button to complete the installation of the AIS Server.

After you have completed the installation, if you are running on WebSphere, the HTTP server associated with the J2EE Server must be restarted manually. If you do not restart the HTTP server, you will not be able to login to the AIS instance.

AIS EnterpriseOne Application Interface.

You can verify the updated fields for JDBj.ini and tnsnames.ora after you have created the new managed instance. To check

  1. Open the newly created managed instance.
  2. Navigate to the Configuration section on the left
  3. Click Database.
  4. Scroll down to view the JDBj.in and tnsnames.ora sections. The information is updated, except the password fields, as per the JAS server you selected while creating the managed instance.
If you want to use TLS with AIS server, ensure that you update the field Use TLS to true under JDBj Runtime Properties section.
Note: AIS instances created prior to this enhancement will also have the Database configuration with default values for JDBj.ini and tnsnames.ora. You can configure the fields as per your requirement.

To verify the installation is successful:

  1. Navigate to the AIS Server instance.

  2. Click on the Test connection link.

    Note: The Test connection link is only enabled when the server is running.

  3. Review the DefaultConfig file.

Note: Click here to view recordings on monitoring the AIS Server.

After you have completed the installation, the browser is redirected to the Management Console page for the newly registered AIS Server. This server also appears as a Managed Instance in the corresponding Managed Home.

For each registered Managed Instance, the Management Console displays appropriate information at the top of the page:

  • General

  • Instance Properties

    • Instance Name

      The name assigned to the Managed Instance at the time it was created or registered.

    • HTTP Port

      Displays the HTTP Port for this server and also provides a link to the HTTP server.

    • Application Server Instance

      Displays the application server into which this EnterpriseOne server is installed and also provides a link to the application server instance and associated managed server (Oracle WebLogic Server) or profile (WebSphere Application Server).

For information on log files, refer to the chapter entitled: Available Log Files