15 Register or Create a JD Edwards Enterprise Server as a New Managed Instance

This chapter discusses these topics that are necessary to register an existing or create a new managed Enterprise Server as a Managed Instance:

15.1 Visual Studio Requirements for Microsoft Windows-based Enterprise Servers

Server Manager detects the supported and installed versions of Visual Studio for Microsoft Windows-based Enterprise Server.

Caution:

Not all JD Edwards EnterpriseOne Applications and Tools releases support various Visual Studio versions. Refer to the JD Edwards EnterpriseOne Certifications (MTRs) and Package Management Guide for support levels.

The JD Edwards EnterpriseOne Administrator can navigate to the Compiler Selection screen by navigating to the Enterprise Server Instance and clicking the Package Builds link.

As shown below, the supported and detected versions of Visual Studio on Microsoft Windows-based JD Edwards EnterpriseOne Enterprise Server. The Administrator can select the appropriate version of Visual Studio and click the Apply button. As a result, Server Manager updates the entries in the [JDE_CG] section and [BSFN BUILD] section of the jde.ini file.

Surrounding text describes build_settings.gif.

15.2 Prerequisites and Recommended Registration or Creation Sequence for an Enterprise Server as New Managed Instance

The following steps represent the prerequisites and recommended sequence for creating an Enterprise Server as a new Managed Instance:

  1. Prerequisite: Management Agent is installed on target machine.

    Refer to Chapter 1, "Getting Started".

  2. Prerequisite: The Enterprise Server Software Component is uploaded to the Management Console.

    Refer to Chapter 9, "Upload Software Components".

  3. Prerequisite: The Enterprise Server Software Component is distributed to the target Managed Home.

    Refer to Chapter 9, "Distribute Software Components to Managed Homes".

Prerequisite and recommendation for registering an Enterprise Server as a new Managed Instance:

Prerequisite: Management Agent is installed on target machine.

Refer to Chapter 1, "Installing the Server Manager Management Console and Agent".

15.3 Register an Existing Enterprise Server as a New Managed Instance

The only Managed Instance that can be registered after being installed by a method other than Server Manager is a JD Edwards EnterpriseOne Enterprise Server. The Enterprise Server may have been installed using the Platform Pack installer or manually created outside of Server Manager. Regardless of the method of creation any Enterprise Server running Tools Release 8.91 (and later) may be registered with Server Manager in preparation for upgrading to 8.97 (and later). Management of Tools Releases 8.96 outside the immediate upgrade steps is not supported.

Only JD Edwards EnterpriseOne Enterprise Servers that are registered with the Management Console can be managed by the Management Console. The Enterprise Server may have been installed using the Platform Pack installer or manually created outside of Server Manager. Regardless of the method of creation, any Enterprise Server running Tools Release 8.97 (and later), including multi-foundation Enterprise Servers, is fully supported.

Note:

Registration of an Enterprise Server requires that a Management Agent first be installed on Enterprise Server. Refer to Chapter 1, "Installing the Server Manager Management Console and Agent".

Registration of Tools Release prior to 8.97 is only intended to facilitate an upgrade to Tools Release 8.97 (and later). Once you have upgraded to Tools Release 8.97 and later you cannot use Server Manager to revert to a release prior to the base release of Tools Release 8.97. If you want to run simultaneous releases of 8.97 (and later) and releases prior to 8.97, you should use Multiple Foundations, which is described in the JD Edwards EnterpriseOne Tools Release 9.2 Reference Guide.

UNIX Installation Note.

On UNIX-based platforms, you must install and run the Management Agent as the same operating system user as the JD Edwards EnterpriseOne Enterprise Server.

To register an existing Enterprise Server instance:

  1. Select the Managed Home with which you wish to register the Enterprise Server.

    This image is described in surrounding text.
  2. Click the Create a New Managed Instance button to create the Managed Instance within the Managed Home.

    This image is described in surrounding text.
  3. On Create/Register a Managed Instance, Instance Type, select this radio button:

    Register an Existing Enterprise Server

  4. Click Continue.

    This image is described in surrounding text.
  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.

    • Instance Name

      Enter a unique name for the instance name.

    • Install Location

      Enter a valid install location for the existing Enterprise Server. For example:

      UNIX:

      /u02/jdedwards/e920

      Windows:

      c:\jdedwards\e920

      For both Windows and UNIX, you must specify the Install Location as the full path.

      IBM i:

      e900SYS

      IBM i Enterprise Servers. These systems do not require a full path. Instead, you should only enter the library name that corresponds to the IFS directory in which JD Edwards EnterpriseOne is installed. Ensure that there are no slash characters in the Install Location.

      For example, E920SYS , E920SYS_1 , E920SYS_2.

      Based on this Install Path, the requested path code libraries and IFS directories are created accordingly by appending the addendum at the end of the pathcodes. For example,

      E920SYS will create the requested path codes in this format: DV920 , PY920, PS920, PD920.

      E920SYS_1 will create the requested path codes in this format: DV920_1 , PY920_1, PS920_1, PD920_1

      E920SYS_A will create the requested path codes in this format: DV920_A , PY920_A, PS920_A, PD920_A

  6. Click Continue.

    This image is described in surrounding text.
  7. On Create/Register a Managed Instance, Confirmation, review the key configuration items, where the web page displays a variety of fields depending on the database and environments of your installation

    You can further configure any item as required.

    Note:

    If the server was installed using the Platform Pack installer, typically you are not required to perform further configuration. Server Manager reads these values from the existing Enterprise Server installation; they are valid if the Enterprise Server was functioning properly at the time of registration.
  8. Click Continue.

    This image is described in surrounding text.
  9. On Create/Register a Managed Instance, Finish, click the Create Instance button to complete the registration of the Enterprise Server.

    This image is described in surrounding text.

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

    You must re-link the Business Functions after you install the 9.2 or later Tools Release to an IBM i-based Enterprise Server using the Server Manager. For instructions, refer to the chapter entitled: Re-Linking Business Functions in the JD Edwards EnterpriseOne Tools Release 9.2 Reference Guide.

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

    • General

      • Software Component Version

        Displays the version of this software component.

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

      • E1 Application Component Version (Release 9.2.1)

        Displays the EnterpriseOne application component version.

      • Path Codes (Release 9.2.1)

        Displays the path codes.

    • Instance Properties

      Install Location

      Displays the full path for the install location of the selected Managed Instance.

      Instance Name

      Displays a clickable link for the name of the selected Managed Instance.

For information on log files, refer to the chapter entitled Chapter 26, "Available Log Files".

15.4 Create (Install) an Enterprise Server as a New Managed Instance

You can use Server Manager to install new Enterprise Servers. However, these Enterprise Servers only contain a system (foundation) and no package or path-code. These Enterprise Servers are not fully functional. Additional steps are required to convert them into functional servers. Additionally, at least one Enterprise Server in your installation must be installed outside of Server Manager using the Platform Pack installer which includes the platform- and database-dependent application data and path codes.

To create an Enterprise Server as a new Managed Instance using Server Manager, you must obtain the appropriate Enterprise Server software component either directly from the Management Console or from Customer Connection using Change Assistant. The Managed Software Component must be uploaded to the Management Console and distributed to the Management Agent to which you wish to install the new Enterprise Server. For additional information, refer to Chapter 9, "Managed Software Components".

To create an Enterprise Server as a new Managed Instance:

  1. Select the Managed Home with which you wish to create the Enterprise Server as a new Managed Instance.

    This image is described in surrounding text.
  2. Click the Create a New Managed Instance button to create the Managed Instance in the Managed Home.

    This image is described in surrounding text.
  3. On Create/Register a Managed Instance, Instance Type, select this radio button:

    Install New Enterprise Server

  4. Click Continue.

    This image is described in surrounding text.

    Note:

    If you are using Windows platform, the following screen is displayed. Surrounding text describes windows.png.
  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.

    • Instance Name

      Enter a unique name for the instance name.

    • Install Location

      Enter a valid install location for the existing Enterprise Server.

    • Foundation Component and Application Component

      Use the drop-down menu to select the foundation and application components from the list of Enterprise Server components distributed to this Management Agent.

    • Path Code (Release 9.2.1)

      Select the required path code.

  6. Click Continue.

    This image is described in surrounding text.
  7. On Create/Register a Managed Instance, Confirmation, review the key configuration items. The web page displays a variety of fields depending on the database and environments of your installation.

    You can further configure any item as required.

  8. Click Continue.

    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 Enterprise Server.

    Surrounding text describes pathcodes.png.

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

    After you have used Server Manager to install your 9.2 (and later) Tools Release to an IBM i-based Enterprise Server, as in previous JD Edwards EnterpriseOne Tools Releases, you must re-link the Business Functions. For instructions, refer to the chapter entitled: Re-Linking Business Functions in the JD Edwards EnterpriseOne Tools Release 9.2 Reference Guide.

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

    • General

      • Software Component Version

        Displays the version of this software component.

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

      • E1 Application Component Version (Release 9.2.1)

        Displays the EnterpriseOne application component version.

      • Path Codes (Release 9.2.1)

        Displays the path codes.

    • Instance Properties

      • Install Location

        Displays the full path for the install location of the selected Managed Instance.

      • Instance Name

        Displays a clickable link for the name of the selected Managed Instance.

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

15.5 Configuring an IBM i Enterprise Server to an Existing DB2 Database (Release 9.2.2.4)

After Installing an IBM i Enterprise Server as explained in Section 15.4, "Create (Install) an Enterprise Server as a New Managed Instance", you must configure it to point to a Pre-Existing DB2 Database.

Make changes to the jde.ini file as shown in the following example to get the Enterprise Server up and running by pointing it to an existing Database Server. These ini file changes may be different depending on the environment you are using.

[DB SYSTEM SETTINGS]

Base Datasource=DENQAS7 - 920 Server Map

Database=DENQAS7 - 920 Server Map

DatabaseName2=SVM920

Default Env=DV920

Default PathCode=DV920

Default Pwd=JDE

Default Role=*ALL

Default User=JDE

Server=DENQAS7

ServerPort=0

[JDENET]

serviceNameConnect=6099

serviceNameListen=6099

[SECURITY]

DataSource=System - 920

SecurityServer=DENQAS1

[SVR]

ApplicationPathAddendum=_I

SpecPath=spec

[WORKFLOW]

WRIPassword=JDE

[SITE_KEYS]

CurrentKey=ADGkvS9o6gamyEF5Uwrqh7M54AX1mfNypjsLrksh4uiK4XG4bdgidkEkKqyOcXjwmYzCEfpsNnogl6tosZae0=

Note:

Configure the Spec.ini file to point to the Correct values.

15.6 Change Component for the Enterprise Server (Tools Release 9.2 Update 3)

This section discusses the changes in Server Manager to apply the Tools release including how to uplift the Enterprise Server to 64-bit.

Note:

See the section 14.2.1, "Setting Up the Password" to set up the password for the Enterprise server component change.

To change the Enterprise Server Component:

  1. Sign in to the Server Manager console, and access the Enterprise Server.

  2. Click the Change button.

    Surrounding text describes ent1.png.
  3. Select the EnterpriseOne Enterprise Server 9.2.3.0_X64 option to change your component from 32-bit to 64-bit.

  4. On the login window, enter the Username and Password for the Database Server, and then click the Login button.

    Note:

    Ensure that you have set the password correctly. For more information see Section 14.2.1, "Setting Up the Password".
    Surrounding text describes ent2.png.
  5. On the window that is displayed, as shown in the following image, click the OK button to change the Enterprise Server Foundation from 32-bit to 64-bit.

    Surrounding text describes ent3.png.
  6. On the window that is displayed, as shown in the following image, click the OK button.

    Note:

    This message is displayed only if your Enterprise Server requires an Oracle Client.
    Surrounding text describes ent4.png.
  7. On the 64-bit Database Client home directory window, enter the correct path, and then click the OK button.

    Note:

    Make sure that the 64-bit Database Client install directory has permissions to allow the Server Manager Agent to read and write contents into it's files.

    If you are on Unix, make sure that the system user has the permission to start the SVM Agent process.

    Surrounding text describes ent5.png.
  8. On the 64-bit JRE Path window, enter the correct path, and then click the Submit button.

    Surrounding text describes ent6.png.
  9. Wait for the process to complete.

    Surrounding text describes ent7.png.
  10. Verify that the component change is successful on the EnterpriseOne Enterprise Server window.

    Surrounding text describes ent8.png.
  11. Verify that the values in the Installation, Package Builds, and JVM Location in the Miscellaneous section are updated with the 64-bit information.

    Note:

    To revert to a 32-bit component, access the Change Component window, and select a 32-bit component that ends with _X86.