8 Working With the Enterprise Server

This chapter contains the following topics:

8.1 Starting and Shutting Down Network Services on the Enterprise Server

The network services are automatically started when you run the RunOneWorld.sh startup script using these steps:

  1. Log on to the Enterprise Server as jde910.

  2. Change to this directory:

    cd $SYSTEM/bin32

  3. Run the RunOneWorld.sh startup script using this command:


  4. Check the status of the services by running the netwm program.


    You should always shut down services before shutting down a VM Guest. When a VM Guest is shutdown and restarted, the Server Manager Agent may need to be manually restarted by logging in as jde910 and running the restartAgent script.

    To shutdown services, repeat the above steps substituting EndOneWorld.sh for RunOneWorld.sh.

    For example, your console might look like this when running the RunOneWorld.sh startup script:

    [root@custent ~]# su - jde910
    $ cd $SYSTEM/bin32
    $ ./RunOneWorld.sh
    Wed Jun 10 18:33:14 EDT 2011   Starting JD Edwards OneWorld on custent
    Wed Jun 10 18:33:16 EDT 2011   JD Edwards OneWorld startup complete.
    $ netwm
    Initializing JDEIPC
    About to setupWorkManagementStruct
    setupWorkManagementStruct ok
    getJDENetWorkManagement ok
    1 net processes
    pid-2926  start-Wed  Jun 10 18:33:14 2011 dport-6015 sport-6015 in-0  out-0   total-0
    4 kernel processes
    pid-2927        parent-2926     start-Wed Jun 10 18:33:17 2011  kdef-13         requests-0      outstanding-1   UserCount-0
    pid-2934        parent-2926     start-Wed Jun 10 18:33:18 2011  kdef-30         requests-0      outstanding-0   UserCount-0
    pid-2935        parent-2926     start-Wed Jun 10 18:33:19 2011  kdef-4  requests-0      outstanding-1   UserCount-0
    pid-2937        parent-2926     start-Wed Jun 10 18:33:20 2011  kdef-4  requests-0      outstanding-0   UserCount-0

8.2 Verifying the Release 9.1 Enterprise Server Installation Using PORTTEST


When running PORTTEST after installing the Enterprise Server, the test returns a failure message. This is because it is not able to access the F0902 table at this time, (the format of the F0902 table changes during the Table Conversion Workbench). Ignore any errors relating to accessing the F0902 table. For example:

Select all on table F0902 failed - rcode=0

Once the Workbench tasks are all complete, and the Enterprise Server is configured, rerun PORTTEST.

To verify the Enterprise Server installation using PORTTEST:

  1. Log on to the Enterprise Server as jde910.

  2. To verify that Release 9.1 is installed correctly on the Enterprise Server, enter these commands:

    cd $SYSTEM/bin32

    porttest userid password environment

    where userid is a valid Release 9.1 user ID, password is the user password, and environment is the environment you want to verify.

    For example:

    porttest JDE JDE DV910

    These parameters are case-sensitive. Enter this command for each environment.

    This program initializes a user and an environment (assuming Release 9.1 is installed and configured correctly). The program displays messages that indicate the selection of records from a Release 9.1 table. If it does not, review the jde_xxxxxx.log file in the directory path $EVRHOME/log.


    If PORTTEST fails to run, for diagnostic assistance refer to the chapter entitled: ”Using the PORTTEST Checklist” in the JD Edwards EnterpriseOne Applications Release 9.1 Installation Guide for Oracle on Unix.