Properties, Scripts, Backups, and Troubleshooting

This chapter covers the following topics:

• Updating Configuration Data in the WLST_Config.properties File
• Configuring the Engine Domain Using Scripts
• Creating Managed Servers Using Scripts
• Managing the Managed Servers Using Scripts
• Backing Up Files
• Troubleshooting

Updating Configuration Data in the WLST_Config.properties File

For the initial configuration, the WLST_Config.properties file needs to be up to date with the relevant details. The file is located in the folder WLST_scripts. A sample property file has been attached for reference. Refer to the example below to populate the file with the proper details.

# Weblogic DetailsExample:
#==================
BEA_HOME - 
Provide the WebLogic home directory – the path in which WebLogic is installed
<line break>
# Engine Domain Details
#======================
Engine_Domain_Name – 
Name of Engine Domain provided during installation in 2.1.
Engine_Domain_AdminServer_Name – 
Name of Engine Domain Admin Server provided during installation in 2.1.
Engine_Domain_Url – 
t3://<Machine_Name>:<Port_No>
Protocol used should be t3 and not http
Machine_Name (For ex. rws60144rems)
Port_No :- Listen Port No. for Engine Domain
Engine_Domain_sslEnabled=1
Engine_Domain_sslPort – 
SSL Port Number provided during installation in 2.1.
# <line break>
# Machine Details
#================
Machine_Name – 
Host name of the machine on which the WebLogic server is running (e.g. rws60144rems.us.oracle.com)
Node_Manager_Listen_Address = localhost
Node_Manager_Listen_Port = 5556
# <line break>
# Server_Start_Arguments
#=======================
Engine_Admin_Min_Memory – 
Minimum size of the server memory (like 128M)
Engine_Admin_Max_Memory – 
Maximum size of the server memory (like 256M)

A sample configuration file appears below.

The values below are pre-populated. Do not edit these values.

# JMS Resource details
#=====================
JMS_System_Resource_Name=RPModule
JMS_Que_Name=RPQueue
JMS_Que_JNDI_Name=weblogic.wsee.DefaultQueue
JMS_SubDep_Name=RPSubModule
# <line break>
# JMS Server details
#===================
JMS_Server_Name=RPWSJMSServer
# <line break>
# Engine Domain JDBC Resource Details
#=============================
JDBC_System_Resource_Name – RPPlanningDS2

Configuring the Engine Domain Using Scripts

Perform the following procedure to configure the Engine Domain using scripts:

1. Verify that the Admin Server is running. If the Admin Server is not running, then start it as per the instructions in Starting the Engine Admin Server.

2. Run the InitialSetup.sh script.

   Check the present working directory through command pwd.

   Go to the directory <WLS_HOME>/user_projects/domains directory, and run the script by issuing the following command:

   $ ./WLST_scripts/InitialSetup.sh <Username> <Password>

   The Username and Password are required for Engine Domain Server.

   

3. View the log file InitialSetup.log to verify the servers were successfully created. To view the log file, go to the next directory WLST_log and open the file InitialSetup.log.

   

4. This script sets up the machine and Node Manager. To verify the setup, refer to Setting the Initial Configuration for the Rapid Planning User Interface and Engine.

Creating Managed Servers Using Scripts

Perform the following procedure to create the Managed Servers using a script.

1. Edit the CreateServer.Properties file to create additional Managed Servers and provide the necessary server details for your environment.

   Input the server details in the format below. (Refer to the sample CreateServer.properties file provided in the folder WLST_scripts.)

   • Enter the No_Of_Managed_Servers to be created.

   • For each Managed Server to be created, enter the following values:

     ms_Name_[i]=
     ms_Listen_Port_[i]=
     ms_Listen_Address_[i]=
     ms_sslEnabled_[i]=
     ms_sslPort_[i]=
     ms_Min_Memory_[i]=
     ms_Max_Memory_[i]=

     where i represents the number of the server.

     For example, if No_Of_Managed_Servers is 5, then there should be 5 sets of the values above in the format as mentioned where i has values 1, 2, 3, 4, and 5. Each Managed Server is defined by the following values you define in the CreateServer.Properties file:

     • ms_Name_[i] - Enter the name of the Managed Server.

     • ms_Listen_Port_[i] - Enter the Listen Port for Manager Server.

     • ms_Listen_Address_[i] - Enter the Listen Address for Manager Server.

     • ms_sslEnabled_[i] - Enter '1' to make SSL Port enabled.

     • ms_sslPort_[i] - Enter the SSL Port Number.

     • ms_Min_Memory_[i] - Enter the minimum memory argument for Manager Server.

     • ms_Max_Memory_[i] - Enter the maximum memory argument for Manager Server.

     A sample CreateServer.properties file appears below.

     

2. Run the CreateServer.sh script.

   Check the current working directory using the command pwd.

   Go to the directory <WLS_HOME>/user_projects/domains, and run the CreateServer.sh script by as shown in the example below.

   Example:

   $ ./WLST_scripts/CreateServer.sh <Username> <Password> <ServerName1> <ServerName2>

   The Username and Password for the Engine Domain Server are required when running the CreateServer.sh script. Server Names should be same referenced in the CreateServer.properties file.

   

   

3. View the log file CreateServer.log to verify the servers were successfully created. To view the log file, go to the next directory WLST_log and open the CreateServer.log file.

4. Verify the newly created Managed Server.

   If the log file shows that the Admin Server was shutdown, start the server as per the instructions in Starting the Engine Admin Server.

   • From the WebLogic home page, select Environment from the Domain Structure region.

     

   • Select Servers.

     

   • Select a server name (for example, RP_MS1). The machine details appear.

     

   • From the Domain Structure region, expand the Services tree node and select Data Sources. The Summary of the JDBC Data Sources screen appears.

     

     The Target Servers for the JDBC Resource appear in the Targets column.

   • From Domain Structure region, select Services > Messaging> JMS Servers. One JMS Server is created for each Managed Server.

     

   • In left pane, select JMS Modules. One JMS Module is created. All the Managed Servers will be mapped to a single JMS Module.

     

     A JMS Module contains JMS Queues and Subdeployments.

   • Select the module name (RPModule in this example). One Queue is created for each server.

     

   • From the Settings region, select the Subdeployments tab.

     

     One Subdeployment is created for each server.

     

Managing the Managed Servers Using Scripts

Adding Managed Servers

Refer to the Creating Managed Servers Using Script in order to add Managed Servers to the existing setup.

1. After the necessary Managed Served are added, target all the newly created Managed Servers to the Deployed Application. In order to achieve this, open the WebLogic User Interface for Engine Domain using the procedures in Starting the Engine Admin Server.

2. Select Deployments from the Domain Structure region.

   

   The following page appears.

   

3. Select the Engine Application (rpws in the example).

4. Select the Targets tab.

   

5. Select the check box with the Type "Enterprise Application", and click Change Targets.

   

6. Check all the Managed Servers you want to deploy the application, except the AdminServer, and click Yes. Follow the instructions.

   

Starting Managed Servers

Perform the following procedure to start the Managed Servers using script commands.

1. Check the present working directory through command pwd.

2. Go to the directory <WLS_HOME>/user_projects/domains and run the StartManServer.sh script as shown in the example below.

   Example:

   $ ./WLST_scripts/StartManServer.sh <Username> <Password> <ServerName1> <ServerName2> ….

   Username and Password for the Engine Domain Server are required when running the StartManServer.sh script.

   

3. View the log file StartManServer.log to verify the Managed Servers were successfully started. To view the log file, go to the next directory WLST_log and open the file StartManServer.log file.

   

4. To verify the status of the Managed Servers, select Servers from the Domain Structure region.

   

5. The table displays the status of all the servers.

   

Stopping Managed Servers

Perform the following procedure to stop a Managed Server using script commands.

1. Check the present working directory through command pwd.

2. Go to the directory <WLS_HOME>/user_projects/domains and run the StopManServer.sh script as shown in the example below.

   Example:

   $ ./WLST_scripts/StopManServer.sh <Username> <Password> <ServerName>

   Username and Password for the Engine Domain Server are required when running the StopManServer.sh script.

   

3. View the log file StopManServer.log to verify the Managed Servers were successfully stopped. To view the log file, go to the next directory WLST_log, and open the StopManServer.log file.

   

4. To verify the status of the Managed Servers, select Servers from the Doamin Structure region.

   

   The table displays the status of all the servers.

   

Deleting Managed Servers

Perform the following procedure to delete a Managed Server using script commands.

1. Check the present working directory through command pwd.

2. Go to the directory <WLS_HOME>/user_projects/domains and run the DeleteServer.sh script as shown in the example below.

   Example:

   $ ./WLST_scripts/DeleteServer.sh <Username> <Password> <ServerName 1> <ServerName 2> …. <ServerName N>

   

3. To verify the status of the Managed Servers, select Servers in the left pane.

   The table displays the status of all the servers. In the Servers section, the Managed Servers you specified should no longer appear in the table.

   

Backing Up Files

The following directories are candidates for your ad-hoc backup, scheduled backup, or backup processes and scripts:

• user_projects/domains/WLST_scripts

• user_projects/domains/WLST_scripts/WLST_Config.properties

  It is recommended that this file be backed up periodically for maintaining Managed Server information.

• user_projects/domains/WLST_log

Troubleshooting

What to do if Admin Server runs out of memory?

If the Admin Server runs out of memory, you need to modify the stack size. Follow the steps mentioned below. The following example modifies the JROCKIT memory size from 256K to 1024K:

Inside engine domain <engine_domain_name>/bin/setDomainEnv.sh

In the file setDomainEnv.sh, locate the memory configuration, as shown in the example below. Overwrite this with the New Memory Configuration (which appears below the Original Memory Configuration).

Original Memory Configuration

XMS_SUN_64BIT="256" 
export XMS_SUN_64BIT 
XMS_SUN_32BIT="256" 
export XMS_SUN_32BIT 
XMX_SUN_64BIT="768" 
export XMX_SUN_64BIT 
XMX_SUN_32BIT="768" 
export XMX_SUN_32BIT 
XMS_JROCKIT_64BIT="256" 
export XMS_JROCKIT_64BIT 
XMS_JROCKIT_32BIT="256" 
export XMS_JROCKIT_32BIT 
XMX_JROCKIT_64BIT="768" 
export XMX_JROCKIT_64BIT 
XMX_JROCKIT_32BIT="768" 
export XMX_JROCKIT_32BIT 
<line break>
if [ "${JAVA_VENDOR}" = "Sun" ] ; then 
WLS_MEM_ARGS_64BIT="-Xms256m -Xmx768m"
export WLS_MEM_ARGS_64BIT
WLS_MEM_ARGS_32BIT="-Xms256m -Xmx768m"
export WLS_MEM_ARGS_32BIT 
else
WLS_MEM_ARGS_64BIT="-Xms512m -Xmx768m"
export WLS_MEM_ARGS_64BIT
WLS_MEM_ARGS_32BIT="-Xms512m -Xmx768m" 
export WLS_MEM_ARGS_32BIT fi 
<line break>
if [ "${JAVA_VENDOR}" = "Oracle" ] ; then
CUSTOM_MEM_ARGS_64BIT="-Xms${XMS_JROCKIT_64BIT}m -
Xmx${XMX_JROCKIT_64BIT}m"
export CUSTOM_MEM_ARGS_64BIT         CUSTOM_MEM_ARGS_32BIT="-Xms${XMS_JROCKIT_32BIT}m -
Xmx${XMX_JROCKIT_32BIT}m"
export CUSTOM_MEM_ARGS_32BIT else         CUSTOM_MEM_ARGS_64BIT="-Xms${XMS_SUN_64BIT}m -Xmx${XMX_SUN_64BIT}m"
export CUSTOM_MEM_ARGS_64BIT         CUSTOM_MEM_ARGS_32BIT="-Xms${XMS_SUN_32BIT}m -
Xmx${XMX_SUN_32BIT}m"
export CUSTOM_MEM_ARGS_32BIT
fi 

New Memory Configuration (Overwrite the old configuration with the following.)

XMS_SUN_64BIT="256" 
export XMS_SUN_64BIT 
XMS_SUN_32BIT="256" 
export XMS_SUN_32BIT 
XMX_SUN_64BIT="768" 
export XMX_SUN_64BIT
XMX_SUN_32BIT="768"
export XMX_SUN_32BIT 
XSS_SUN_64BIT="1024" 
export XSS_SUN_64BIT
XSS_SUN_32BIT="1024"
export XSS_SUN_32BIT 
XSS_JROCKIT_64BIT="1024"export XSS_JROCKIT_64BIT 
XSS_JROCKIT_32BIT="1024" 
export XSS_JROCKIT_32BIT 
XMS_JROCKIT_64BIT="256"
export XMS_JROCKIT_64BIT
XMS_JROCKIT_32BIT="256" 
export XMS_JROCKIT_32BIT
XMX_JROCKIT_64BIT="768" 
export XMX_JROCKIT_64BIT 
XMX_JROCKIT_32BIT="768" 
export XMX_JROCKIT_32BIT 
<line break>
if [ "${JAVA_VENDOR}" = "Oracle" ] ; then
CUSTOM_MEM_ARGS_64BIT="-Xms${XMS_JROCKIT_64BIT}m -
Xmx${XMX_JROCKIT_64BIT}m -Xss${XSS_JROCKIT_64BIT}k"
export CUSTOM_MEM_ARGS_64BIT
CUSTOM_MEM_ARGS_32BIT="-Xms${XMS_JROCKIT_32BIT}m -
Xmx${XMX_JROCKIT_32BIT}m -Xss${XSS_JROCKIT_32BIT}k" 
export CUSTOM_MEM_ARGS_32BIT 
else
CUSTOM_MEM_ARGS_64BIT="-Xms${XMS_SUN_64BIT}m -
Xmx${XMX_SUN_64BIT}m -Xss${XSS_SUN_64BIT}k"
export CUSTOM_MEM_ARGS_64BIT         CUSTOM_MEM_ARGS_32BIT="-Xms${XMS_SUN_32BIT}m -
Xmx${XMX_SUN_32BIT}m -Xss${XSS_SUN_32BIT}k"
export CUSTOM_MEM_ARGS_32BIT 
fi

When configuring the machine from the Rapid Planning Admin User Interface, the machine is not created in the Engine AdminServer. How can I resolve this issue?

This might occur due to multiple reasons. Please write down the remedial steps.

Reason 1

Engine Server is not running.

Action required: Start the Engine service.

Reason 2

MSC: Rapid Planning Scripts Home profile value is not set correctly.

Action required:

• Ensure that you have provided the correct path precisely as mentioned in the pre-configuration section.

• Ensure the path is accessible and has full permissions for the UNIX user who started the UI Domain Admin Server.

Reason 3

Machine could not be configured due to port conflict.

Action required: Ensure the port numbers specified are available.

I am unable to open the Rapid Planning Administration User Interface or the Rapid Planning Simulation Planner User Interface.

Log in to EBS home page.

• For Rapid Planning Administration User Interface, select Advanced Planning Administrator responsibility Rapid Planning (Setup and Configuration)

• For Rapid Planning Simulation Planner User Interface, select Supply Chain Simulation Planner responsibility Supply Chain Simulation Planner (Plans, Inputs and Simulations)

• If the responsibility is not available in your home page, contact your System Administrator to add this responsibility to your EBS user.

• In case of any error message regarding User credentials/security, ensure that this step is executed properly.

While performing the configuration steps, “Lock & Edit” mode is not available. Why?

The domain has been created in the Development mode. Production mode is recommended.

When starting the WebLogic Server, the server does not prompt for credentials. Why?

Check if your server is in Development mode or Production mode. Production mode is recommended.

Refer to the instructions in Creating the User Interface Domain and Creating the Engine Domain.

Unable to view Analytics/KPI graphs in the Simulation Planner User Interface. What could be the reason?

The application requires browser plug-ins to enable the KPI views/graphs. If this situation is encountered even after verifying the browser plug-ins are available, you might have missed this setup step in Creating the Engine Domain.

Create output/ and log/ directories as follows:

$ mkdir -m 777 output/

$ mkdir -m 777 log/

Unable to run a plan in the Simulation Planner User Interface. Plan run fails.

Verify in Creating the Engine Domain that this setup step was executed.

Create output/ and log/ directories as follows:

$ mkdir -m 777 output/

$ mkdir -m 777 log/

After deploying the Rapid Planning Admin User Interface (UI) application, the UI does not appear in the browser. Instead an error message "Error 500 - Internal Server Error" appears.

Verify the classpath settings. Make sure that the CLASSPATH, JAVA_HOME have been unset before you start WebLogic Server.

You can try the following to clear its settings: export CLASSPATH= ”

Unset the above mentioned variables and try restarting the server.

SQL failure/error occurs when you set up a database link from a 11g to 10g database.

This is due to a bug in the DMS JDBC driver (ojdbc6dms.jar) regarding connecting from a 11g database to a 10g database.

Find the following in file setDomainEnv.cmd on Windows or in file filesetDomainEnv.sh on UNIX:

if NOT "%PRE_CLASSPATH%"=="" (
set PRE_CLASSPATH=%
COMMON_COMPONENTS_HOME %\modules
#oracle.jdbc_11.1.1
\ojdbc6dms.jar;%PRE_CLASSPATH%
) else ( 
set PRE_CLASSPATH=%
COMMON_COMPONENTS_HOME %\modules
\oracle.jdbc_11.1.1\ojdbc6dms.jar  )

Replace it with the following:

if NOT "%PRE_CLASSPATH%"=="" (  
set PRE_CLASSPATH=%WL_HOME%\lib
\ojdbc6.jar;%PRE_CLASSPATH%
) else (  
set PRE_CLASSPATH=%WL_HOME%\lib\ojdbc6.jar

Saved queries do not retain the query condition.

In Rapid Planning User Interface Domain, folder bin, find file startWebLogic.sh.

Below line 'SAVE_JAVA_OPTIONS="" line, add the following line

JAVA_OPTIONS="${JAVA_OPTIONS} -Doracle.mds.validatelocaluniqueattr=false

Example:

SAVE_JAVA_OPTIONS="${JAVA_OPTIONS}"
SAVE_CLASSPATH="${CLASSPATH}"
# Start Derby 
DERBY_DEBUG_LEVEL="0"
if [ "${DERBY_FLAG}" = "true" ] ; then ${WL_HOME}/common/derby/bin/startNetworkServer.sh >"${DOMAIN_HOME}/derby.log" 2>&1 
fi
JAVA_OPTIONS="${SAVE_JAVA_OPTIONS}"
SAVE_JAVA_OPTIONS="" 
JAVA_OPTIONS="${JAVA_OPTIONS} -Doracle.mds.validatelocaluniqueattr=false"

Rapid Planning authentication leads to redirect loop

Use the same protocol in access URLs for the Oracle e-Business Suite and the Oracle Rapid Planning User Interface application. If Oracle e-Business Suite is:

1. SSL enabled: Use https:// for both access URLs

2. Not SSL enabled: Use http:// for both access URLs

Use the appropriate port number.