otm 6.4.1 installation guide

Oracle Transportation Management Supplemental Installation Guide for Version 6.4.1

O R A C L E W H I T E P A P E R | J A N U A R Y 2 0 1 6

1 | SUPPLEMENTAL INSTALLATION GUIDE FOR VERSION 6.4.1

Table of Contents

Downloading OTM and other Installers 2

Downloading OTM 6.4.1 6

Installing Java 7 7

Installing Weblogic 12c 7

Installing OHS 13

Installing Weblogic Patch 17968606 19

Creating the ADF Repository via the rcu utility 20

Installing OTM 6.4.1 using the silent installer 26

Editing the example.installer.properties file 26

Running the OTM Silent Installer 41

Post Installation 44

Passwords for the system and guest user in the GL_USER table 45

Starting and Stopping OTM 6.4.1 45

NodeManager 47

Resetting the NodeManager Password 47

Installation Problems 48

2 | Supplemental Installation Guide for Version 6.4.1

Downloading OTM and other Installers

For the OTM 6.4.1 installation you will need to download software packages and have them installed prior to installing OTM. You will need Java 1.7, Weblogic 12c , Oracle HTTP Server 12c , Oracle DB 12c Admin install and client. Log into the edelivery site and download the software needed for the install. https://edelivery.oracle.com

Figure 1. The eDelivery website sign in screen.

Sign In

https://edelivery.oracle.com/


After logging in press the Accept button to accept the export agreement.

Figure 2. The eDelivery acceptance screen.

Start typing in the Oracle Transportation Management and the product selector should appear.

Figure 3. The eDelivery product selection screen.

Accept

Select product


Choose the platform by pressing the Select Platform button, selecting your operating system and pressing the

Select button.

Figure 4. The eDelivery platform selection screen.

Press Continue

Figure 5. The eDelivery after selecting platform screen.

Select platform

Continue


Press Continue

Figure 6. The eDelivery confirm selection screen.

Review and accept the download agreement and press Continue

Figure 7. The eDelivery Agreements screen.

Continue

Continue


Downloading OTM 6.4.1

For the standard 6.4.1 installation you will need to download Oracle Transportation Management 6.4.1.0.0, Oracle Fusion Middleware 12c Infrastructure 12.1.3.0.0, Oracle HTTP Server 12.1.3.0.0 and Oracle Database 12.1.0.2.0 using the links provided below.

Figure 8.File Download

Note: This document does not cover the installation of Fusion Transportation Intelligence or an external report server instance.

Download All


Installing Java 7

Even though OTM provides its own version of Java, you still need to have Java version 7 installed before continuing with the installation. It is required for the installation of Weblogic 12c. Note: If you do not have Java 7 installed on your server you may need to download the Oracle JDeveloper 12.1.3.0.0 or install Java 7 using another method. Check with your system administrator if needed.

Installing Weblogic 12c

Unzip the Weblogic download and run the java -jar command to install Weblogic.

<Path to the 1.7 version of Java>/java -jar fmw_12.1.3.0.0_infrastructure.jar /opt/install/jdk/bin/java -jar fmw_12.1.3.0.0_infrastructure.jar

Verify the Inventory Directory Location and the Operating System Group and press OK.

Figure 9.Install

Verify location

OK


Press Next

Figure 10.Install Welcome screen

Next


Enter the Home Directory for the Weblogic Install and press Next. Note: Keep track of this directory location as it will be needed for the OHS and OTM install.

Figure 11.Installation location screen.

Next


Press Next

Figure 12.Installation Type screen.

Next


Verify the prerequisite checks pass and press Next.

Figure 13. Prerequisite Checks screen.

Next


Verify the information for the installation is correct and press Install.

Figure 14. Installation Summary screen.

Install


Press Finish when the install is complete.

Figure 15. Installation Progress screen.

Installing OHS

Unzip the OHS download and run the OHS installer.

./fmw_12.1.3.0.0_ohs_linux64.bin

Finish


Verify the Inventory Directory Location and the Operating System Group and press OK.

Figure 16. OHS Installer screen.

Press Next

Figure 17. OHS Installer Welcome screen.

OK

Next


Enter the directory where you installed the Infrastructure version of Weblogic. Press Next.

Figure 18. OHS Installer Installation Location screen.

Next


Note: Be sure the Collocated HTTP Server option is selected and press Next.

Figure 19. OHS Installer Installation Type screen.

Next


Verify the prerequisite checks pass and press Next.

Figure 20. OHS Installer Prerequisite Checks screen.

Next


Verify the information for the installation is correct and press Install.

Figure 21. OHS Installer Installation Summary screen.

Install


Press Finish when the install is completed.

Figure 22. OHS Installer Installation Progress screen.

Installing Weblogic Patch 17968606

Note: Be sure all processes associated with Weblogic and OHS are stopped before installing this patch.

1. Download patch Weblogic patch 17968606 from ARU using the following link.

http://aru.us.oracle.com:8080/ARU/ViewPatchRequest/process_form?aru=18134667

2. Copy and unzip the file in the [BEA_HOME] directory. You should see a new directory, 17968606, was created.

For this installation it would be copied to “/opt/home/otm640/kaw/bea_12.1.3”.

3. Change directories to the 17868606 directory

4. Set your environment variables for installing the patch. Set the BEA_HOME to your Weblogic install directory,

the other lines should not need to be changed.

export ORACLE_HOME=[BEA_HOME] export JAVA_HOME=$ORACLE_HOME/oracle_common/jdk export PATH=$JAVA_HOME/bin:$ORACLE_HOME/OPatch:$PATH

Example: The export command for this installation would be:

export ORACLE_HOME=/opt/home/otm640/kaw/bea_12.1.3

5. Install the patch from the 17868606 directory using the following command.

opatch apply Answer "y" to the following question if you are ready to the install the patch

Is the local system ready for patching? [y|n]

Finish


Once the installation is done the following message will be displayed.

OPatch succeeded.

Creating the ADF Repository via the rcu utility

In order to support the ADF changes in 6.4.x the MDS schema and users need to be created. This schema and its

users can be created in the same DB as your OTM instance, but this is not recommended for production instances.

To create the schema and users run the Repository Creation Utility ( rcu )

Go to the [WEB_BEA_PATH]/oracle_common/bin directory and run rcu command

./rcu

Figure 23. RCU utility Welcome screen

Next


Press Next Be sure the Create Repository and System Load and Product Load are selected and press Next.

Figure 24. RCU utility Create Repository screen

Enter the connection information for the MDS database and press Next. This information will be needed for the OTM install.

Figure 24. RCU utility Database Connection Details screen

Next

Next


Press OK after the Prerequisite check completes.

Figure 25. RCU utility status screen

Use the Create New Prefix option and select the prefix you want you use for your installation. This information will be needed for the OTM install. Note: Be sure and check the Oracle AS Repository Components to ensure all of the users are created and press Next.

Figure 26. RCU utility Select Components screen

OK

Next


Press OK the Prerequisite check completes.

Figure 27. RCU utility status screen

Select the password option needed for your implementation, enter and re-enter the password for the MDS users. For this install we will be using the same password for all schemas, but this is not recommended for production installations as it provides limited password security.

Figure 28. RCU utility Schema Passwords screen

OK

Next


Verify the tablespace that will be used when the repository is created and press Next. Note: Typically the tablespace that is created will not exceed more than 1GB unless you have a large number of users on your OTM instance making significant changes to their user screens.

Figure 29. RCU utility Map Tablespaces screen

Press OK

Figure30. RCU utility Map Tablespaces confirmation screen

Next

OK


Press OK after the tablespace is created.

Figure31. RCU utility Map Tablespaces completion screen

Verify the information and press Create.

Figure32. RCU utility Summary screen

OK

Create


Press Close when the process completes.

Figure33. RCU utility Completion Summary screen

Installing OTM 6.4.1 using the silent installer

There are several installation methods available for OTM 6.4.1, GUI, console and silent installer. This document will cover the installation using the silent install method. When you extract the download for OTM you will see the OTM installer, ReadMe.txt, example.installer.properties and the docs.zip file.

Editing the example.installer.properties file

The example.installer.properties will be used by the silent installer to provide the answer to all of the questions asked during the OTM install. Note: Make a copy of the example.installer.properties before making any of the changes needed for you installation. The first section of the file you need to update is related to the user that is going to running the OTM processed on the server. #**********************************************************************

#*** This file is to be used to install Oracle Transportation

#*** Management and Oracle In-Memory Logistics Command Center using

#*** the "silent installer" option. For more information on how to

#*** do that, please see the OTM Admin Guide.

#**********************************************************************

Close


#**********************************************************************

#*** SECURITY NOTE

#**********************************************************************

#*** This file contains passwords in clear text along with other

#*** information that could be used to compromise the integrity of

#*** your software installation. Please safeguard this file

#*** appropriately!

#**********************************************************************

#**********************************************************************

#*** NOTES & TIPS

#**********************************************************************

#***

#*** 1) Unless otherwise indicated, all variables must be assigned a

#*** valid value.

#***

#*** 2) Variables may refer to another variable by enclosing the

#*** referenced variable's name in between dollar signs ($). For

#*** example:

#***

#*** WEB_EXT_PORT=$WEB_PORT$

#***

#*** This will set the value of WEB_EXT_PORT to be the same as the

#*** value WEB_PORT at the moment it is evaluated. This implies

#*** (correctly) that the referenced variable must be defined

#*** before the variable referencing it (i.e. WEB_PORT must be

#*** defined before using it to define WEB_EXT_PORT).

#***

#*** 3) When specifying paths for a Unix-based system, remember to use

#*** forward slashes:

#***

#*** GC3_INSTALL_PATH=/opt/otm

#***

#*** When on a Windows system, remember to use back slashes and a

#*** drive letter:

#***

#*** GC3_INSTALL_PATH=c:\otm

#***

#*** 4) The abbreviation 'FQDN' means 'Fully Qualified Domain Name',

#*** and refers to the full machine name (including TCP/IP domain name) of

#*** the server in question (e.g. mail.oracle.com, where 'mail' is

#*** the name of the machine and 'oracle.com' is the domain name).

#***

#*** 5) The heading sections below will indicate what platform the

#*** variables apply to (not all variables are needed on all

#*** platforms) as well as what type of OTM install they apply to

#*** (e.g. WEB vs. APP)

#***

#*** 6) If the installer cannot determine where the user's home

#*** directory is (either using OS-based rules or the value of

#*** UNIX_USER_HOME) then the installer running in silent mode will

#*** not be able to write out the log file should an error occur.

#***

#*** If the silent installer is run and no log file can be found,

#*** re-run the silent installer with the environment LAX_DEBUG set

#*** to 'true' (without the quotes). This will produce a lot of

#*** output but should also reveal what is going wrong.

#***

#**********************************************************************

#----------------------------------------------------------------------

#--- All configurations, Unix/Linux only

#----------------------------------------------------------------------

# UNIX_USER_NAME - the system user name of the user that will own OTM

# processes (usually the user logged in when doing the install


# itself); please see notes under USER_GROUP_CHECK_FAIL_OK below

UNIX_USER_NAME=otm641wl

# UNIX_GROUP_NAME - the system group name of the user that will own OTM

# processes (usually the user logged in when doing the install

# itself); please see notes under USER_GROUP_CHECK_FAIL_OK below

UNIX_GROUP_NAME=otm641wl

# UNIX_USER_HOME - the home directory of $UNIX_USER_NAME$

UNIX_USER_HOME=/home/$UNIX_USER_NAME$

# USER_GROUP_CHECK_FAIL_OK - if your system is set up so that user or

# group names are not stored locally in the standard files

# (e.g. /etc/passwd, /etc/group) then the installer will not be able

# to validate that the names supplied are valid. In this case, and in

# this case only, you should set this value to 'true' which will

# indicate to the installer that it's OK to fail this check. Valid

# values are (without the quotes): 'true', 'false'.

#

# NOTE: Please do not use this value unless you are absolutely sure

# that the values supplied for UNIX_USER_NAME, UNIX_GROUP_NAME and

# UNIX_USER_HOME are valid and spelled correctly. Setting this

# variable to 'true' while supplying invalid data will result in an

# unusable installation.

USER_GROUP_CHECK_FAIL_OK=false

Update the following lines with the correct values for your installation.

UNIX_USER_NAME=otm641wl UNIX_GROUP_NAME=otm641wl UNIX_USER_HOME=/home/$UNIX_USER_NAME$

The next section that needs to be updated has information related to the installation type as well as information about the Web, App and DB servers that will be used for this installation. #----------------------------------------------------------------------

#--- All configurations, all platforms

#----------------------------------------------------------------------

# CHOSEN_INSTALL_SET - valid values are (without the quotes):

# 'WebServer', 'AppServer' or 'WebAppServer'

CHOSEN_INSTALL_SET=WebAppServer

# USER_INSTALL_DIR - where OTM should be installed to

USER_INSTALL_DIR=/opt/otm

# DOMAIN_NAME - the TCP/IP domain name; not used directly by the

# installer, but could be used elsewhere in this properties file

DOMAIN_NAME=oracle.com

# BEA HOME

BEA_HOME=/opt/bea

# BEA Server Path

BEA_SERVER_PATH=$BEA_HOME$/wlserver

# APP_HOSTNAME - application server's machine name

APP_HOSTNAME=otm-app

# APP_FQDN - the internal FQDN of the OTM app server

APP_FQDN=$APP_HOSTNAME$.$DOMAIN_NAME$

# APP_PORT - the port number that the OTM app server is listening on

APP_PORT=7001


# APP_SSL_PORT - the SSL port number that the OTM app server is listening on

APP_SSL_PORT=7002

# WEB_HOSTNAME - Web server's machine name

WEB_HOSTNAME=otm-web

# WEB_FQDN - The FQDN of the OTM web server; this is the "real"

# machine name (see 'WEB_EXT_FQDN' below)

WEB_FQDN=$WEB_HOSTNAME$.$DOMAIN_NAME$

# WEB_PORT - The port that the OTM web server is listening on

# NOTE: This port number must match what was used during the OHS install

# unless some sort of port redirection was done (see the "Admin

# Privileges" section of the OTM Security Guide)

WEB_PORT=7778

# WEB_EXT_FQDN - The external FQDN of the OTM web server (could be

# different than the internal FQDN of the web server)

WEB_EXT_FQDN=$WEB_FQDN$

# WEB_EXT_PORT - The external port of the OTM web server (could be

# different than the internal port of the web server)

WEB_EXT_PORT=$WEB_PORT$

# WEB_URL_PROTOCOL - Accessing the External url with HTTP or HTTPS

WEB_URL_PROTOCOL=https

# DB_FQDN - the internal FQDN of the OTM database server

DB_FQDN=otmdb.$DOMAIN_NAME$

# DB_PORT - the port that the OTM database instance is listening on

DB_PORT=1521

# DB_CONNECTSTRING - the connect string for the OTM database instance

DB_CONNECTSTRING=otmdb

# DB_SID - the service name for the OTM database instance (this could be

# the service name, the SID or the Scan Listener value)

DB_SID=$DB_CONNECTSTRING$

# DB_CLIENT_PATH - the full path to the Oracle database client install

DB_CLIENT_PATH=/u01/app/oracle/product/11g

# MAIL_SMTP_FQDN - the FQDN of the mail server used to send outbound

# emails

MAIL_SMTP_FQDN=smtp.$DOMAIN_NAME$

# MAIL_REPLYTO_EMAIL - the reply-to email address that all

# notification emails use

MAIL_REPLYTO_EMAIL=OtmAdvisor@$DOMAIN_NAME$

# GC3_MIGRATE - whether or not this instance should migrate custom

# configuration changes from a previous release's glog.properties

# file; see the OTM Admin Guide for more information on when this

# should be used. Valid values are (without the quotes): 'Yes',

# 'No'.

#

# NOTE: OTM has been changed to work off of Service Names instead of

# SIDs. Most non-RAC database instances will have the same value for

# both Service Name and SID, so this should not be an issue. Please

# see the Install Guide for more information.

GC3_MIGRATE=No

# GC3_MIGRATE_PATH - the path with the old glog.properties file is

# located. This is only used if GC3_MIGRATE is set to 'true'.

GC3_MIGRATE_PATH=/opt/old-otm/glog/config


Update the CHOSEN_INSTALL_SET property for the installation type you intend to use. The valid values for your installation can be on the following - 'WebServer', 'AppServer' or 'WebAppServer' without the '. Update the USER_INSTALL_DIR property with the location where you want OTM installed. Be sure the user running the install has write permission to create the directory if it does not exist. Update the DOMAIN_NAME property with the correct value for your installation. This value is used throughout the installation. For this install, if my server’s Fully Qualified Domain Name (FQDN) is otm641.yourcompany.com the DOMAIN_NAME property should be set to yourcompany.com. Update the BEA_HOME property with the path you used when you installed Weblogic. The BEA_SERVER_PATH property should not need to be updated. Update the APP_HOSTNAME property with the beginning of the FQDN of your application server. Using the same FQDN mentioned above, otm641.yourcompany.com this should be set to "otm641"

Note: IP Addresses should not be used. The APP_FQDN property should not need to be updated. Note: During the installation of OTM you will be required to define ports for the Web, App and DB servers being used. If you decide to change any of the port setting from the default values, be sure the same port is not used later in the installation or by another application running on the same server. The APP_PORT and APP_SSL_PORT properties can be left with the ports already defined or changed depending on your installation requirements. Update the WEB_HOSTNAME property with the beginning of the FQDN of your web server. Since we are doing a combined Web and App install the same FQDN mentioned above, otm641.yourcompany.com would be the used for the Web, so this should be set to "otm641" as well. Note: IP addresses should not be used. The WEB_FQDN property should not need to be updated. Update the WEB_PORT with the port you want to use for the installation or leave the port set to 7778. Update the WEB_EXT_FQDN and WEB_EXT_PORT with new values if you are not expecting them to be same as the WEB_FQDN and WEB_PORT defined earlier. This documentation will cover the http installation, so change the WEB_URL_PROTOCOL property to http. Note: Additional post installation steps are needed to enable https connections. Update the DB_FQDN to the correct value for your DB server. In most cases you only need to change otmdb to the name of your DB server, the $DOMAIN_NAME$ variable should pull in the remaining portion of the server name. Update the DB_PORT with the port you are using. Update the DB_CONNECTSTRING property with the Service Name of the DB instance. You can use the following command to check the value you intend to use.

Note: If you are unsure what this setting should be you can connect to the DB Server and check the DB Listener for the instance. Typically this is done using the "lsnrctl status" command. Information similar to this should be displayed if the DB Listener is started.


LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 14-OCT-2015 10:18:17 Copyright (c) 1991, 2014, Oracle. All rights reserved. Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=otm641db.usa.oracle.com)(PORT=1521))) STATUS of the LISTENER ------------------------ Alias LISTENER Version TNSLSNR for Linux: Version 12.1.0.2.0 - Production Start Date 04-AUG-2015 11:41:40 Uptime 70 days 22 hr. 36 min. 37 sec Trace Level off Security ON: Local OS Authentication SNMP OFF Listener Parameter File /u01/app/oracle/product/1212/network/admin/listener.ora Listener Log File /u01/app/oracle/diag/tnslsnr/otm641db/listener/alert/log.xml Listening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=otm641db.usa.oracle.com)(PORT=1521))) (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521))) (DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=otm641db.usa.oracle.com)(PORT=5500))(Security=(my_wallet_directory=/u01/app/oracle/admin/sup64adf/xdb_wallet))(Presentation=HTTP)(Session=RAW)) Services Summary... Service "sup641" has 1 instance(s). Instance "sup641", status READY, has 1 handler(s) for this service... Service "sup641XDB" has 1 instance(s). Instance "sup641", status READY, has 1 handler(s) for this service... Check the connect information is correct by using running the following command.

sqlplus system@"(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<FQDN of DB Server>)(PORT=<Port>))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=<Value listed as the Service>)))" Note: The same value is used for the DB_SID property, so it is important this is set correctly for your instance. Failure to do so could cause connection failures and problems with the DB installation or migration to this version. Update the DB_CLIENT_PATH property with the directory where you installed the Oracle DB client. The Oracle DB Client should be the Administrator Install. Update the MAIL_SMTP_FQDN property. In most cases you only need to change the "smtp" to beginning portion of the FQDN of your SMTP server as long as the domain name is the same as the value you defined previously. We do not recommend changing the value of the GC3_MIGRATE property to Yes. Any custom property settings used in previous versions should be reviewed to see if they are still needed for the new release. If this is changed you also need to update the GC3_MIGRATE_PATH property with the location of the glog.properties file you want the settings copied from.


Note: Review the AIX and HPUX questions of either of these operation systems are being used for your installation.

#----------------------------------------------------------------------

#--- All configurations, AIX only

#----------------------------------------------------------------------

# EXTERNAL_JDK_PATH - OTM requires that a 1.6 JDK be installed on the

# machine prior to installing on one of the above-mentioned platforms.

# The OTM installer will create a symbolic link to this directory.

EXTERNAL_JDK_PATH=/opt/jdk-1.6

#----------------------------------------------------------------------

#--- All configurations, AIX only

#----------------------------------------------------------------------

# NUM_CPUS - the number of logical CPUs present; this is used to tune

# one of the Java garbage collection parameters.

NUM_CPUS=4

The next section allows you to define the App Server settings.

#----------------------------------------------------------------------

#--- App server installations only, all platforms

#----------------------------------------------------------------------

# APP_JVM_MEMORY - amount of memory (in MB) to allocate to the OTM

# application server

APP_JVM_MEMORY=4096

# APP_LAUNCHER_PORT - the port number that the OTM app launcher is

# listening on -- NOTE: this must be unique for every Launcher instance

# on the box as it binds to localhost (127.0.0.1), not a specific IP

# address

APP_LAUNCHER_PORT=32001

# APP Server Domain Settings {NAME, PORT, SSL PORT}

APP_DOMAIN_NAME=otmapp

APP_DOMAIN_LISTEN_PORT=$APP_PORT$

APP_DOMAIN_SSL_LISTEN_PORT=$APP_SSL_PORT$

The APP_JVM_MEMORY is setup by default to use 4GB of memory. You should expect the application to use up to 8GB of memory depending on what actions are being run on the application. Be sure and plan your server resources to account for this additional memory usage. The APP_LAUNCHER_PORT property can be left with the port already defined or changed depending on your installation requirements. The APP_DOMAIN_NAME property can be left with the default or changed depending on your installation requirements. The APP_DOMAIN_LISTEN_PORT property should not need to be updated. The installer will use the same value used for the APP_PORT property value you entered earlier. The APP_DOMAIN_SSL_LISTEN_PORT should not need to be updated. The installer will use the same value used for the APP_SSL_PORT property value you entered earlier. Note: If this is a Windows install update the APP_SERVICE with the service name you intend to use.


#----------------------------------------------------------------------

#--- App server installations only, Windows-only

#----------------------------------------------------------------------

# APP_SERVICE - the Windows service name for the OTM application server

APP_SERVICE=otmapp641

The next section allows you to define the Web Server settings

#----------------------------------------------------------------------

#--- Web server installations only, all platforms

#----------------------------------------------------------------------

# Web Server WebLogic Domain Settings {Name, PORT, SSL PORT, Node Manager Port}

WEB_DOMAIN_NAME=otmweb

WEB_DOMAIN_LISTEN_PORT=8001

WEB_DOMAIN_SSL_LISTEN_PORT=8002

WEB_NODE_MANAGER_LISTEN_PORT=5556

# OHS_COMPONENT_NAME - the name of the OHS component

OHS_COMPONENT_NAME=otm641

#WEB OHS PORT

WEB_OHS_PORT=7777

#WEB OHS SSL PORT

WEB_OHS_SSL_PORT=4443

# OHS admin Port

OHS_ADMIN_PORT=9999

# WEB_SSL_PORT - the SSL port that the web server listens on

WEB_SSL_PORT=4444

# WEB_SERVLET_JVM_MEMORY - amount of memory (in MB) to allocate to

# Tomcat

WEB_SERVLET_JVM_MEMORY=4096

# WEB_LAUNCHER_PORT - the port number that the OTM web launcher is

# listening on -- NOTE: this must be unique for every Launcher instance

# on the box as it binds to localhost (127.0.0.1), not a specific IP

# address

WEB_LAUNCHER_PORT=32000

# Node Manager Service name for Windows

NODE_MANAGER_SERVICE=$WEB_DOMAIN_NAME$_NM

#### MDS DATABASE Settings {DB, PORT, Service Name, Prefix}

MDS_DB_FQDN=mdsdb.$DOMAIN_NAME$

MDS_DB_PORT=1521

MDS_DB_SERVICE_NAME=mdsdb

MDS_PREFIX=OTM

## MDS Schema Name

MDS_SCHEMA_STB=$MDS_PREFIX$_STB

MDS_SCHEMA_OPSS=$MDS_PREFIX$_OPSS

MDS_SCHEMA_IAU_VIEWER=$MDS_PREFIX$_IAU_VIEWER

MDS_SCHEMA_IAU_APPEND=$MDS_PREFIX$_IAU_APPEND

MDS_SCHEMA_MDS=$MDS_PREFIX$_MDS

# OTM Web/App Communication

OTM_APP_USER_NAME=OTMApp

OTM_APP_GROUP_NAME=OTMAppUser


The WEB_DOMAIN_NAME property can be left with the default or changed depending on your installation requirements. The WEB_DOMAIN_LISTEN_PORT property can be left with the default or changed depending on your installation requirements. The WEB_DOMAIN_SSL_LISTEN_PORT property can be left with the default or changed depending on your installation requirements. The WEB_NODE_MANAGER_LISTEN_PORT property can be left with the default value. If this is changed you will encounter a known issue with several of the startup script where the value of 5556 has been hard coded. This will be addressed in version 6.4.2 via this defect. Bug 22354339 - STARTNODEMANAGER.PY, STARTOHS.PY AND STOPOHS.PY SCRIPTS ARE USING PORT 5556 Note: If you use another port you will need to update the [USER_INSTALL_DIR]/install/webserver/ startOHS.py and stopOHS.py scripts and change port 5556 to the port you used before starting the instance. The OHS_COMPONENT_NAME property can be left with the default or changed depending on your installation requirements. The WEB_OHS_PORT property can be left with the default or changed depending on your installation requirements. The WEB_OHS_SSL_PORT property can be left with the default or changed depending on your installation requirements. The OHS_ADMIN_PORT property can be left with the default or changed depending on your installation requirements. The WEB_SSL_PORT property can be left with the default or changed depending on your installation requirements. The WEB_SERVLET_JVM_MEMORY property is setup by default to use 4GB of memory. You should expect the Web instance to use 8GB of memory or more depending on what actions are being run by the users. Be sure and plan your server resources to account for this additional memory usage. The WEB_LAUNCHER_PORT property can be left with the default or changed depending on your installation requirements. The NODE_MANAGER_SERVICE property is only used for Windows based installations and can be left with the default value or changed depending on your installation requirements. The MDS_DB_FQDN should only need to the "mdsdb" value update as long as the DOMAIN_NAME of the MDS DB server is the as the value defined previously. Update the MDS_DB_PORT with the port you are using. Update the MDS_DB_SERVICE_NAME property with the Service Name of the DB instance. Follow the instructions provided earlier to determine the proper value. Failure to do so will cause the installation to fail the Web portion of the installation. Update the MDS_PREFIX with the value you used when you created the ADF Repository. None of the following properties should need to be updated.

MDS_SCHEMA_STB=$MDS_PREFIX$_STB MDS_SCHEMA_OPSS=$MDS_PREFIX$_OPSS MDS_SCHEMA_IAU_VIEWER=$MDS_PREFIX$_IAU_VIEWER MDS_SCHEMA_IAU_APPEND=$MDS_PREFIX$_IAU_APPEND MDS_SCHEMA_MDS=$MDS_PREFIX$_MDS


The OTM_APP_USER_NAME and OTM_APP_GROUP_NAME properties can be left with the default value or changed to me your installation requirements. These are used for Web to App communications and are only used internally by OTM. They do not need to be actual OS users on the servers. Note: Since this installation document is only intended to cover the basic installation of OTM we will not be covering any of the properties related to FTI, ODI or connecting to other third party applications. #----------------------------------------------------------------------

#--- Integration with other Oracle products

#--- Web or App server installations, all platforms

#----------------------------------------------------------------------

#......................................................................

#... Fusion Transportation Intelligence (FTI) integration, OTM-only

#......................................................................

# INSTALL_FTI - whether or not to integrate with an FTI server; valid

# values are (without the quotes): 'true', 'false'

INSTALL_FTI=false

# FTI_WEB_EXT_FQDN - The external FQDN of the OTM FTI web server

FTI_WEB_EXT_FQDN=otmfti.$DOMAIN_NAME$

# FTI_WEB_EXT_PORT - The External Port of the OTM FTI Web server

FTI_WEB_EXT_PORT=7001

# FTI_WEB_EXT_PROTOCOL - Specify the protocol by which url will be access

FTI_WEB_EXT_PROTOCOL=https

# FTI_DB_FQDN - the FQDN of the OTM FTI Database server

FTI_DB_FQDN=otmftidb.$DOMAIN_NAME$

# FTI_DB_PORT - the port that the OTM FTI Database server listens on

FTI_DB_PORT=1521

# FTI_DB_SCHEMA - the OTM FTI Database schema name

FTI_DB_SCHEMA=hdowner

# FTI_DB_SID - the OTM FTI Database SID

FTI_DB_SID=otmrod01

# FTI_DB_USER - the OTM FTI Database user name

FTI_DB_USER=hdowner

#......................................................................

#... Oracle Data Integrator (ODI) integration, OTM-only

#......................................................................

# NOTE: This is only needed when INSTALL_FTI=true, in which case

# this section is required.

# ODI_AGENT_FQDN - the FDQN of the OTM ODI Agent server

ODI_AGENT_FQDN=otmodiagent.$DOMAIN_NAME$

# ODI_AGENT_PORT - the port that the OTM ODI Agent server listens on

ODI_AGENT_PORT=20910

# ODI_WORK_CODE - the ODI Work Repository Code

ODI_WORK_CODE=FTI_WORK

#......................................................................

#... ROD - Replicated Operational Database (formerly ODS)

#......................................................................


# INSTALL_ROD - whether or not to integrate BI Publisher with an ROD;

# valid values are (without the quotes): 'true', 'false'

INSTALL_ROD=false

# DB_ODS_FQDN - the FQDN for the ODS server

DB_ODS_FQDN=otmrod.$DOMAIN_NAME$

# DB_ODS_PORT - the port that the OTM ROD database listens on

DB_ODS_PORT=1521

# DB_ODS_CONNECTSTRING - connect string for the OTM ROD database

DB_ODS_CONNECTSTRING=otmrod

# DB_ODS_SID - the service name for the OTM ROD database

DB_ODS_SID=otmrod

#......................................................................

#... EBS integration

#......................................................................

# INSTALL_EBS - whether or not to integrate with EBS; valid


# Note: no further configuration values needed for this section.

INSTALL_EBS=false

#......................................................................

#... EnterpriseOne integration

#......................................................................

# INSTALL_E1 - whether or not to integrate with BI Publisher; valid


# Note: no further configuration values needed for this section.

INSTALL_E1=false

#......................................................................

#... Oracle MapViewer installation

#......................................................................

# INSTALL_MAPVIEWER - whether or not to integrate with a MapViewer

# instance; valid values are (without the quotes): 'true', 'false'

INSTALL_MAPVIEWER=false

# MAPVIEWER_FQDN - the FQDN of the MapViewer instance

MAPVIEWER_FQDN=mapviewer.$DOMAIN_NAME$

# MAPVIEWER_SERVICENAME - the service name (data source name) for the MapViewer

# instance

MAPVIEWER_SERVICENAME=elocation_mercator

# MAPVIEWER_BASEMAP - the basemap value for the MapViewer instance, defined in

# the format of "data-source-name.map-tile-layer-name".

MAPVIEWER_BASEMAP=$MAPVIEWER_SERVICENAME$.world_map

#----------------------------------------------------------------------

#--- Integration with other Oracle products


#----------------------------------------------------------------------

#......................................................................

#... Oracle Spatial installation

#......................................................................

# INSTALL_SPATIAL - whether or not to integrate with an Oracle Spatial server

# for distance/time lookups and address validation; valid values are (without

# the quotes): 'true', 'false'


INSTALL_SPATIAL=false

# SPATIAL_FQDN - the FQDN of the Oracle Spatial server

SPATIAL_FQDN=spatial.$DOMAIN_NAME$

# SPATIAL_PORT - the port that the Oracle Spatial server listens on

SPATIAL_PORT=7777

# SPATIAL_ROUTE_SERVET_NA - servlet used for US/Canada distance and

# time lookups

SPATIAL_ROUTE_SERVLET_NA=/routeserver/servlet/RouteServerServlet

# SPATIAL_ROUTE_SERVET_EU - servlet used for Western Europe distance

# and time lookups

SPATIAL_ROUTE_SERVLET_EU=/routeserver_eu/servlet/RouteServerServlet

# SPATIAL_GEOCODE_SERVET - servlet used for address validations

SPATIAL_GEOCODE_SERVLET=/geocoder/gcserver

#----------------------------------------------------------------------

#--- Third-party integrations


#----------------------------------------------------------------------

#......................................................................

#... FaxMaker integration

#......................................................................

# INSTALL_FAXMAKER - whether or not to integrate with FaxMaker; valid


# NOTE: see FAX_FROM_NUMBER and FAX_SERVER_EMAIL below

INSTALL_FAXMAKER=false

#......................................................................

#... RightFax integration

#......................................................................

# INSTALL_RIGHTFAX - whether or not to integrate with RightFax; valid


# NOTE: see FAX_FROM_NUMBER and FAX_SERVER_EMAIL below

INSTALL_RIGHTFAX=false

# FAX_FROM_NUMBER - the phone number that faxes will see to originate

# from (required if either INSTALL_FAXMAKER or INSTALL_RIGHTFAX is set

# to 'true')

FAX_FROM_NUMBER=555-555-1212

# FAX_SERVER_EMAIL - the email address that the fax server polls

# (required if either INSTALL_FAXMAKER or INSTALL_RIGHTFAX is set to

# 'true')

FAX_SERVER_EMAIL=otmfax@$DOMAIN_NAME$

#......................................................................

#... SMC RateWare integration

#......................................................................

# INSTALL_RATEWARE - whether or not to integrate with SMC Rateware;


INSTALL_RATEWARE=false

# RATEWARE_FQDN - the FQDN of the SMC Rateware server

RATEWARE_FQDN=rateware.$DOMAIN_NAME$

# RATEWARE_PORT - port that the Rateware server listens on

RATEWARE_PORT=23700


# RATEWARE_NEWAPI = set to 'true' if using SMC RateWare Version 1.2.325

# (or later) or SMC Carrier Connect

RATEWARE_NEWAPI=false

#......................................................................

#... SMC RateWareXL integration

#......................................................................

# INSTALL_RATEWAREXL - whether or not to integrate with SMC RatewareXL;


INSTALL_RATEWAREXL=false

# RATEWARE_USER - username for RatewareXL service

RATEWAREXL_USER=

# RATEWARE_PASSWORD - password for RatewareXL service

RATEWAREXL_PASSWORD=

# RATEWARE_LICENSE - license key for RatewareXL service

RATEWAREXL_LICENSE=

#......................................................................

#... PC*Miler integration

#......................................................................

# INSTALL_PCMILER - whether or not to integrate with PCMiler; valid


INSTALL_PCMILER=false

# PCMILER_FQDN - the FQDN of the PCMiler server

PCMILER_FQDN=pcmiler.$DOMAIN_NAME$

# PCMILER_PORT - the port that the PCMiler server listens on

PCMILER_PORT=8145

#......................................................................

#... PC*Miler Rail integration

#......................................................................

# INSTALL_PCMILER_RAIL - whether or not to integrate with PCMiler

# Rail; valid values are (without the quotes): 'true', 'false'

INSTALL_PCMILER_RAIL=false

# PCMILER_RAIL_FQDN - the FQDN of the PCMiler Rail server

PCMILER_RAIL_FQDN=pcmiler-rail.$DOMAIN_NAME$

# PCMILER_RAIL_PORT - the port that the PCMiler Rail server listens on

PCMILER_RAIL_PORT=2001

#......................................................................

#... Rand McNally IntelliRoute integration

#......................................................................

# INSTALL_INTELLIROUTE - whether or not to integrate with

# IntelliRoute; valid values are (without the quotes): 'true', 'false'

INSTALL_INTELLIROUTE=false

# INTELLIROUTE_FQDN - the FQDN of the IntelliRoute server

INTELLIROUTE_FQDN=192.168.101.103

# INTELLIROUTE_PORT - the port that the IntelliRoute server listens on

INTELLIROUTE_PORT=1998

# INTELLIROUTE_USER - the IntelliRoute user ID (set up during the

# IntelliRoute installation)

INTELLIROUTE_USER=otm


# INTELLIROUTE_PASSWORD - the IntelliRoute user Password (set up during

# the IntelliRoute installation)

INTELLIROUTE_PASSWORD=changeme

# INTELLIROUTE_LOCATION - the IntelliRoute location (set up during the

# IntelliRoute installation)

INTELLIROUTE_LOCATION=company

#......................................................................

#... Rand McNally MileMaker integration

#......................................................................

# INSTALL_MILEMAKER - whether or not to integrate with MileMaker;


INSTALL_MILEMAKER=false

# MILEMAKER_FQDN - the FQDN of the MileMaker server

MILEMAKER_FQDN=milemaker.$DOMAIN_NAME$

# MILEMAKER_PORT - the port that the MileMaker server listens on

MILEMAKER_PORT=1031

#......................................................................

#... Kewill Flagship integration

#......................................................................

# INSTALL_KEWILL - whether or not to integrate with Kewill's Flagship

# server; valid values are (without the quotes): 'true', 'false'

INSTALL_KEWILL=false

# KEWILL_FQDN - the FQDN of the Kewill server

KEWILL_FQDN=kewill.$DOMAIN_NAME$

# KEWILL_PORT - the port that the Kewill server listens on

KEWILL_PORT=1200

# KEWILL_REFNUM_QUAL_GID - the OTM Location Refnum Qualifier GID used

# to cross-reference with Kewill data

KEWILL_REFNUM_QUAL_GID=KEWILL_CUST_NUM

The last section of the file is where you define the passwords for instance.

#----------------------------------------------------------------------

#--- Passwords

#----------------------------------------------------------------------

#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

#+++

#+++ NOTE: The following values MUST BE changed from their default value

#+++ ^^^^^^^

#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

#......................................................................

#... All configurations, all platforms

#......................................................................

# APP_TIER_WEBLOGIC_ADMIN_PASSWORD - password for the WebLogic Admin/system user

APP_TIER_WEBLOGIC_ADMIN_PASSWORD=default

# OTM_APP_WEB_USER_PASSWORD - password used for APP-to-WEB User communication

# authentication; this will not ever be typed in by a user. In an OTM


# Scalability cluster (SCA) setup, the value for this variable must be

# the same on all systems in the cluster.

OTM_APP_WEB_USER_PASSWORD=default

# GUEST_USER_PASSWORD - Guest user account password

GUEST_USER_PASSWORD=default

# GLOGDBA_PASSWORD, GLOGLOAD_PASSWORD - database user

# passwords

GLOGDBA_PASSWORD=default

GLOGLOAD_PASSWORD=default

# FTI_DB_PASSWORD - the password for the FTI_DB_USER

# NOTE: this password MUST be changed from the default value even if

# you are not using Fusion Transportation Intelligence (it may be left

# blank if desired)

FTI_DB_PASSWORD=default

# ODI_AGENT_PASSWORD - the password for the OTM ODI Agent

# NOTE: this password MUST be changed from the default value even if

# you are not using Fusion Transportation Intelligence (it may be left

# blank if desired)

ODI_AGENT_PASSWORD=default

## MDS Schema passworwds

# These password will be same that was enterd during the MDS DB settings

# before the installation

# This will be utlized during the Web or WebApp installation

MDS_SCHEMA_STB_PWD=default

MDS_SCHEMA_OPSS_PWD=default

MDS_SCHEMA_IAU_VIEWER_PWD=default

MDS_SCHEMA_IAU_APPEND_PWD=default

MDS_SCHEMA_MDS_PWD=default

#Web Tier WebLogic Admin Password

WEB_TIER_WEBLOGIC_ADMIN_PASSWORD=default

#**********************************************************************

#***** EOF ***** EOF ***** EOF ***** EOF ***** EOF **********

Note: The old default password of CHANGEME should no longer be used for OTM installations. Using CHANGEME for the APP_TIER_WEBLOGIC_ADMIN_PASSWORD or the WEB_TIER_WEBLOGIC_ADMIN_PASSWORD will cause the installation to fail since CHANGEME does not meet the minimum security requirements for Weblogic. The password you use should be at least 8 characters and contain at least one number. The following characters should NOT be used:

# [ ] $ % ? { } ` \ " ' | Update the APP_TIER_WEBLOGIC_ADMIN_PASSWORD with the password you want to use for this installation. This value should be the same for all App servers for this OTM instances since it is the password assigned to the SYSTEM user in the GL_USER table in OTM. Update the OTM_APP_WEB_PASSWORD with the password you want to use for this installation. This will be used by the OTM_APP_USER_NAME when communicating with the other Web and App servers in this instance. This value should be the same for all Web/App servers for this OTM instances. Update the GLOGDBA_PASSWORD with the password you want to use for this installation. This value should be the same for all Web/App servers for this OTM instances. Update the GLOGLOAD_PASSWORD with the password you want to use for this installation. This value should be the same for all Web/App servers for this OTM instances.


Update the FTI_DB_PASSWORD with the password you want to use for this installation or leave it blank if FTI is not being installed at a later time. This value should be the same for all Web/App servers for this OTM instances. Update ODI_AGENT_PASSWORD with the password you want to use for this installation or leave it blank if FTI is not being installed at a later time. This value should be the same for all Web/App servers for this OTM instances. Update the following properties with the passwords you entered when you created the ADF repository. MDS_SCHEMA_STB_PWD=default MDS_SCHEMA_OPSS_PWD=default MDS_SCHEMA_IAU_VIEWER_PWD=default MDS_SCHEMA_IAU_APPEND_PWD=default MDS_SCHEMA_MDS_PWD=default Update the WEB_TIER_WEBLOGIC_ADMIN_PASSWORD to the value you want to use for this installation. This can be different on each Web instance if needed for your installation requirements. Save the changes and copy the new file to the same directory where you have the OTM 6.4.1 installer.

Running the OTM Silent Installer

Start the silent install by running the following command. Notice the “-f” and name of the installer properties file is listed in the command line.

./otmv641_linux.bin -i silent -f <path and file name of the installer properties file> Note: The path is only needed if the properties file is not in the same directory as the OTM installer. For this install the command would be the following:

./otmv641_linux.bin -i silent -f support641webapp.installer.properties You will only see limited information on the screen during the installation process, although you can monitor the progress by checking some of the logs that are created during the installation. Note: If there is not enough space in the /tmp, the UNIX_USER_HOME, or the USER_INSTALL_DIR to complete the installation, the installer may fail part way through the installation process without generating an obvious error in the logs. The first log to be created will be generated in the /tmp dir and have a filename similar to “7b4d2c815221a227f9.details”. Do an “ls –ltr” in the tmp directory and look for the latest file ending with “.details” to check the beginning of the installation process if needed. This file will be eventually renamed to “Oracle_Transportation_Management_v6.4.1_GA_InstallLog.log” and copied to the USER_INSTALL_DIR later during the install process. The log will show some basic information about the installation method being used, basic environment information, summary of the install and some other steps of the install. Note: If the install stops immediately after you run the install command, check this log for errors. One of the most common problems reported are invalid passwords being used, similar to the error below. OTM Error: Status: FATAL ERROR Additional Notes: FATAL ERROR - Please enter the valid password for the Weblogic System account. A valid password is 1) At least 8 characters long 2) Contains at least one number or special character. {ExitCode: -106}


Another common error would be generated if you try and install OTM 6.4.1 into a directory that already has an OTM installation in it. Status: FATAL ERROR Additional Notes: FATAL ERROR - An existing installation of OTM has been detected under /opt/otm64x. The installer will now exit. {ExitCode: -105} If there are no problems found in the properties you created the installer will create the OTM Home you specified and copy the OTM 6.4.1 installation files to the install directory. You should see the following screen.

Figure34.

The installation will be on this stage for several minutes as it creates the OTM Home and copies all of the files needed for the installation. When you see the screen change to this, the domain creation and deployment scripts are running.


Figure35.

This is the longest part of the installation due to the need to restart Weblogic several times during the Web and App domain deployment. In another console you can monitor the deployment process by tailing one of the following logs in the [USER_INSTALL_DIR]/logs directory.

web_python_exec.log app_python_exec.log

Note: For a combined Web and App install the Web install is completed first. The scripts for the Web deployment run in the following order.

CreateWebDomain.py CreateOHS.py UserGroup.py AuthenticatorAuthorizer.py DeployWeb.py

Note: Failure of any of these scripts will corrupt the Web portion of the installation. The scripts for the App deployment run in the following order.

CreateAppDomain.py DeployApp.py AppServerDomainConfig.py

Note: Failure of any of these scripts will corrupt the App portion of the installation.


Once the installation is complete you will the following will be displayed.

Figure36.

Go to the new OTM Home and check the Summary section of the Oracle_Transportation_Management_v6.4.1_GA_InstallLog.log for any errors. Summary ------- Installation: Successfulnull 63717 Successes 1 Warnings 0 NonFatalErrors 0 FatalErrors The following is a normal warning and can be ignored. OTM Error: Status: WARNING Additional Notes: WARNING - The /opt/otm641was/install/ReadMe.txt file contains important, last-minute information about your new instance. Please be sure to review it before starting up.

Post Installation

Open a new console and log in as the OTM user before running any of the Database scripts required for installation

or migration to 6.4.1. This will ensure the environment variables for the user are properly set.

These can also be set manually by going to the [USER_INSTALL_DIR]/install directory and running the following

command. Notice the “.” a space and then the rest of the command.

. ./gc3env.sh


Follow the instructions in the Installation or Migration Guide depending on your implementation to complete the

database portion of the installation of 6.4.1.

Note: The Webserver and Appserver Weblogic java processes were started and stopped as part of the installation.

The only process that should be running after the installation completes is the NodeManager process. Be sure to run

the DB scripts required for your Installation or Migration before starting the Web or App server java processes.

Information for stopping and starting OTM, NodeManager ( required for the Web Server ) and resetting the

NodeManager password are covered later in this document.

Passwords for the system and guest user in the GL_USER table

When OTM is installed several users are created in the GL_USER table, system and guest. During the installation

process you are no longer able to use CHANGEME for the system user and we highly recommend it not be used for

the guest user.

If you are creating a new instance of OTM you will have the option to set the passwords of the system and guest

user passwords when you run the create_all script.

Note: If you are migrating from an older version of OTM where a non-compliant password was previous used you

will need to run the update_password script after running the dbpatch script to ensure the proper encrypted value is

stored in the database for the OTM system and guest users in the gl_user table. This should be done prior to

starting OTM and trying to log in.

From the [USER_INSTALL_DIR]/glog/oracle/script8 directory run the following command:

./update_password.sh

Answer each of the questions as they are displayed or press enter if the default setting applies to your installation. This should be done for the system and guest user.

No user should run this script except Application Administrator. Enter Application Administrator user name (Press Enter for default of system): Using default administrator user system Enter Application Administrator password: Enter the glog properties path (Press Enter for default of ../../config): Using default property path ../../config Enter user name for which password need to be updated: Enter new password: Enter connection id (Press Enter for default of dbaglogowner) :

Check the update update_password log in the same directory to ensure the password was updated.

Starting and Stopping OTM 6.4.1

Before starting OTM ensure the users environmental variables are properly set. This can be done by logging out of

the console and logging in so the entries in the .bashrc file are read. This can also be done by going to the

[USER_INSTALL_DIR]/install directory and running the following command.

. ./gc3env.sh

Notice the “.” a space and then “./gc3env.sh”.


Once done you can restart the OTM App and Web instance by going into the [USER_INSTALL_DIR]/

install/appserver and [USER_INSTALL_DIR]/install/webserver directories and run the restart scripts provided.

App:

./glogapp-wl restart ./glogapp-wl stop ./glogapp-wl start

If you monitor the [USER_INSTALL_DIR]/log/appserver/console.log.0 during startup, messages similar to the

following indicate the instance is up and running.

INFO | 2015/10/15 14:41:24 | <Oct 15, 2015 2:41:24 PM PDT> <Notice> <Server> <BEA-002613> <Channel

"DefaultSecure[3]" is now listening on 127.0.0.1:7002 for protocols iiops, t3s, ldaps, https.>


"DefaultSecure[1]" is now listening on fe80:0:0:0:f816:3eff:feb5:69c4:7002 for protocols iiops, t3s, ldaps, https.>


"DefaultSecure[2]" is now listening on 0:0:0:0:0:0:0:1:7002 for protocols iiops, t3s, ldaps, https.>


"Default[1]" is now listening on fe80:0:0:0:f816:3eff:feb5:69c4:7001 for protocols iiop, t3, ldap, snmp, http.>


"Default[3]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>


"Default[2]" is now listening on 0:0:0:0:0:0:0:1:7001 for protocols iiop, t3, ldap, snmp, http.>

INFO | 2015/10/15 14:41:24 | <Oct 15, 2015 2:41:24 PM PDT> <Notice> <WebLogicServer> <BEA-000329>

<Started the WebLogic Server Administration Server "gc3app-slc09ugl" for domain "otmapp" running in production

mode.>

INFO | 2015/10/15 14:41:24 | <Oct 15, 2015 2:41:24 PM PDT> <Notice> <WebLogicServer> <BEA-000360> <The

server started in RUNNING mode.>


<Server state changed to RUNNING.>

INFO | 2015/10/15 14:41:38 | -- OTM Event: serverReady

Web:

./glogweb-wl restart

./glogweb-wl stop

./glogweb-wl start

If you monitor the [USER_INSTALL_DIR]/log/webserver/console.log.0 during startup, messages similar to the

following indicate the instance is up and running.



"DefaultSecure[3]" is now listening on 127.0.0.1:8002 for protocols iiops, t3s, ldaps, https.>


"DefaultSecure[1]" is now listening on fe80:0:0:0:f816:3eff:feb5:69c4:8002 for protocols iiops, t3s, ldaps, https.>


"Default[3]" is now listening on 127.0.0.1:8001 for protocols iiop, t3, ldap, snmp, http.>


<Started the WebLogic Server Administration Server "gc3web-slc09ugl" for domain "otmweb" running in production

mode.>

INFO | 2015/10/15 14:36:49 | <Oct 15, 2015 2:36:49 PM PDT> <Notice> <WebLogicServer> <BEA-000360> <The

server started in RUNNING mode.>


<Server state changed to RUNNING.>

NodeManager

NodeManager is a process required to be running in order for the Web instance to startup. This process is started

during the installation of OTM, but will be restarted if needed via the OTM Web startup script.

The NodeManager process can be stopped by running the following command.

[WEB_BEA_PATH]/user_projects/domains/[WEB_DOMAIN_NAME]/bin/stopNodeManager.sh

Note: If you are prompted to enter the Node Manager password during startup you need to enter the same

password as you used for WEB_TIER_WEBLOGIC_ADMIN_PASSWORD, which should be the same the value

assigned to the var.WL_PW= entry in the [USER_INSTALL_DIR]/webserver/weblogic.conf file.

Resetting the NodeManager Password

Note: As long as the NodeManager password was not changed from value used during installation you can use the following steps to fix the password issue. The OTM Web server WebLogic instance must be started for the following steps to complete.

1. Start wlst.sh from [WEB_BEA_PATH]/ohs/common/bin directory

./wlst.sh

2. At the wls prompt, connect to the running WebLogic instance:

connect('weblogic','[WEB_TIER_WEBLOGIC_ADMIN_PASSWORD]','t3://[WEB_FQDN]:[WEB_DOMAIN_LISTEN_PORT]')


3. Run the following command to store the config and properties file:

storeUserConfig('[WEB_BEA_PATH]/user_projects/domains/[WEB_DOMAIN_NAME]/nm-cfg-[WEB_DOMAIN_NAME].props', 'BEA_HOME/user_projects/domains/[WEB_DOMAIN_NAME]/nm-key-[WEB_DOMAIN_NAME].props')

Note: If prompted, enter Y for the confirmation of creating the files.

4. Restart the OTM web server and confirm that the NodeManager password is no longer requested.

Installation Problems

If there are problems with the installation of OTM you will be need to delete domains that were created during the

deployment. If the problems were on the Web portion of the install you will also need to drop and re-create the

repository.

Shutdown OTM Web/App and NodeManager following the instructions provided earlier in the document.

Go to the [WEB_BEA_PATH]/user_projects/domains directory on the Web Server the

[APP_BEA_PATH]/user_projects/domains on the App Server and delete the OTM Web and/or App domain you

intend to re-install.

rm -r [WEB_DOMAIN_NAME]

rm -r [APP_DOMAIN_NAME]

Go to the directory before the [USER_INSTALL_DIR] and run the following command to delete the installed

software.

rm –r [USER_INSTALL_DIR]

Go to the [WEB_BEA_PATH]/oracle_common/bin/ directory and run the repository creation utility.

./rcu


Press Next

Figure37. RCU Welcome screen

Select the option to Drop Repository and press Next again.

Next


Figure38. RCU Drop Repository screen

Enter the connection information for the MDS database and press Next.

Figure39. RCU Database Connection Detail screen

Next

Drop Repository

Next


Press OK when the Prerequisite check completes.

Figure40. RCU Prerequisite check screen

Confirm the schema being deleted before pressing Next.

Figure41. RCU Select Component screen

OK

Next


Press OK when the prerequisite check completes.

Figure42. RCU Check Completion screen

Press the Drop button to remove the repository.

Figure43. RCU Summary screen

OK

Drop


Press Close when the process completes.

Figure43. RCU Completion Summary screen

Go to the OTM users user home directory and edit the .bashrc provide and remove the reference to the gc3env.sh script. You should see lines similar to this when you edit the file. ########################################

# Setup Environment for Otmv641

#---------------------------------------

. /opt/otm641/install/gc3env.sh

########################################

Add a # in from of the line to comment it out, or remove the lines altogether. They will be re-added when you run another install. Log out and back in as the OTM user and start the OTM install process again from the “Creating the ADF Repository via the rcu utility” section in this document. Note: Adding the "LAX_DEBUG=true" in the silent installer command line will generate additional exit codes to the screen. These codes can help troubleshoot installation failures. LAX_DEBUG=true ./otmv641_linux.bin -i silent -f <path and file name of the installer properties file>

Close

Oracle Corporation, World Headquarters Worldwide Inquiries

500 Oracle Parkway Phone: +1.650.506.7000

Redwood Shores, CA 94065, USA Fax: +1.650.506.7200

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the

contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0116 Oracle Transportation Management Version 6.4.1 Supplemental Installation Guide January 2016 Author: Keith Wenyon

C O N N E C T W I T H U S

blogs.oracle.com/oracle

facebook.com/oracle

twitter.com/oracle

oracle.com

otm 6.4.1 installation guide

Technology