Create a Business Services Server as a New Managed Instance

Caution:

This Caution is applicable only if you are creating a Business Services Server on a WebSphere application server.

Ensure that you have already installed a version of WebSphere that is compatible with the Business Services Server (refer to Accessing the Certifications (Minimum Technical Requirements) in this guide).

In order to enable Server Manager to install a Managed Instance for a Business Services Server, you must have configured the supported version of WebSphere with a secure profile. For general security settings directly related to Server Manager, refer to Configure WebSphere Application Server to Work With Server Manager When Administrative Security is Enabled in this guide. For recommendations for securing the WebSphere profile, refer to the Business Service Server Reference Guide.

You should also ensure that the server profile associated with the J2EE Server that you created for the Business Services Server is in the Running state before installing the Business Services Server through Server Manager. If this server is not running, the installation will fail.

Note:

To deploy JAX-WS business services to a business services server instance on WebLogic Server or WebSphere Application Server, ensure that your Server Manager Console and Agent (under which the business services server instance on WebLogic Server or WebSphere Application Server are registered) are the same level as the Management Console.

Note:

Starting with Tools release 9.2.1, when you build a new BSSV package for deployment, the files BSSVpackage.EAR and BSSVpackage.JAR are created. You can deploy this JAR file directly from the Server Manager Console

See Deploying the JAR file from the Server Manager Console

See Also

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

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

• Refer to the for details on other tasks and topics extraneous to Server Manager.

To install a Business Services Server Instance:

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

   

2. In the Managed Instances section of the page, click the Create a New Managed Instance button.

   

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

   EnterpriseOne Business Services Server

   

   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.

4. 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.

     Ensure the J2EE Server that you choose is a secure WebSphere 7.0 or 8.5 profile (releases prior to 7.0 are not supported). Otherwise, Server Manager will not allow you to continue the installation.

   • 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

   • 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 the inherited values are seen in the next screen, 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.

5. Click Continue.

   

   

   

   Note:

   This example illustrates an installation by selecting an enterprise server to be propagated.

   

   

   

   Note:

   This example illustrates an installation by selecting NONE under Propagate Enterprise Server Config.

6. On Create/Register a Managed Instance, Confirmation, review the key configuration items. 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

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

   

8. On Create/Register a Managed Instance, Finish, click the Create Instance button to complete the installation of the Business Services Server.

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

   

   Note:

   After you have created the EnterpriseOne Business Services Server Managed Instance, unlike all other web-based server products it does not start automatically. This is because the Managed Instance is not functional until the Business Services components are installed in it through the special JD Edwards EnterpriseOne package build process designed for that product. Refer to the JD Edwards EnterpriseOne Tools Release 9.2 Package Management Guide.

   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.

   • 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 WebSphere Application Server profile.

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