Create a Transaction Server as a New Managed Instance

You must use Server Manager to install a new Transaction Server instance.

See also:

• Prerequisites and Recommended Installation Sequence for Managed Instances for Web-Based Server Instances

• Refer to the JD Edwards EnterpriseOne Transaction Server Reference Guide for details on additional tasks and topics related to Server Manager.

To install a Transaction Server instance:

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

   

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

   

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

   EnterpriseOne Transaction Server

4. Click Continue.

   

   Note:

   The Propagate Enterprise Server Config drop-down appears only if any enterprise server is registered within the Server Manager console. The Propagate Enterprise Server Config drop-down contains the available enterprise server instances registered with the SM console within a particular selected server group. NONE is added to the drop-down by default.

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

   • Server Group

     Use the dropdown to select the Server Group to which 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_PORT

     where PRODUCT is the JD Edwards EnterpriseOne server type, such as Enterprise_Server, HTML_Web_Server, RTE_Transaction_Server, Collaborative_Portal, or Business_Services, and

     where SERVER is the machine on which the instance is installed, and

     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:

     • Verify HTTP Ports

     • HTTP Ports on UNIX Operating Systems

   • Software Component

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

   • Propagate Enterprise Server Config

     Select the enterprise server from the drop-down list to propagate the configurations.

     Note:

     By default, the selected item is set to NONE. Selecting NONE signifies that you do not wish to propagate configurations from any available enterprise server. If any enterprise server is selected, all of the inherited values are seen in the next scree, otherwise the properties are seen with blank/default values. If propagated, the propagated values are not editable on the confirmation page, however they can be modified post installation.

6. Click Continue.

   

   

   Note:

   This example illustrates an installation on a WebSphere Application Server by selecting an enterprise server to be propagated. If installing on WLS, the HTTP Server (WAS Only) field is not displayed.

   

   

   Note:

   This example illustrates an installation on a WebSphere Application Server by selecting NONE under Propagate Enterprise Server Config. If installing on WLS, the HTTP Server (WAS Only) field is not displayed.

7. On Create/Register a Managed Instance, Confirmation, review the key configuration items. The page displays a variety of fields depending on your application server (WAS or WLS). The values on this form must be confirmed manually. You must validate or update, as appropriate, all configuration items.

   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.

   

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

   Note:

   This process may take fifteen or more minutes to complete.

   After you have completed the installation, the HTTP server associated with the J2EE Server (WAS) must be restarted manually. If you do not restart the HTTP server, you will not be able to login to JD Edwards EnterpriseOne.

   

   After you have completed the installation, the browser is redirected to the Management Console page for the newly registered Transaction 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

     • Status

       Valid values are:

       Running

       When the status is Running, the Stop button is available.

       Stopped

       When the status is Stopped, the Start button is available.

       See also:

       Start or Stop a Managed EnterpriseOne Software Component

     • Software Component Version

       Displays the version of this Software Component.

       See also:

       Change a Managed EnterpriseOne Software Component

   • 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 domain (Oracle WebLogic Server) or profile (WebSphere Application Server).

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