1. Administration Guide
  2. Understanding Enterprise Server Startup for UNIX or Linux

Understanding Enterprise Server Startup for UNIX or Linux

You can start the enterprise servers either manually at the command line or automatically when the server boots. The manual process is the same for all supported platforms, but the automatic process varies slightly by platform.

Note: If you are running JD Edwards EnterpriseOne on the same server as the Oracle database, you must make sure that Oracle is running before you start JD Edwards EnterpriseOne. In particular, if you are starting JD Edwards EnterpriseOne at system boot time, you must make sure the Oracle startup processes are completed first.

RunOneWorld.sh is the script that starts the JD Edwards EnterpriseOne system on the enterprise server. This script:

  • Checks for existing JD Edwards EnterpriseOne processes.

    The script returns an error if it detects that JD Edwards EnterpriseOne is already running.

  • Runs the rmics.sh script to clear IPC resources.

    This script ensures no IPC resources conflict with other software.

  • Starts jdenet_n, which is the JD Edwards EnterpriseOne network listener that receives requests from JD Edwards EnterpriseOne workstations.

  • Runs a program called cleanup that checks for unfinished batch processes from a previous shutdown.

The default database parameters for UNIX might not fully support multiple users. You might reach the maxprocess or *.processes limit for the database. The initial settings are for a small database, so you should change these parameters to a medium setting to avoid database problems. These settings reside in the init.ora or spfile. These paths are an example of where you might typically find these files:

/u01/app/oracle/product/12.1.0/dbhome/dbs/init.ora
/u01/app/oracle/product/12.1.0/dbhome/dbs/spfileORASID.ora