Transportation Install Admin Guide 8.1

Installation/Administration
Guide
JDA® Transportation
Release 8.1.0.0
JDA Software Group, Inc.
Legal notice
Rights to the content of this document
Copyright © 1995-2014 JDA Software Group, Inc. All rights reserved.
Printed in the United States of America.
Reproduction of this document or any portion of it, in any form, without the express written consent of JDA
Software Group, Inc. ("JDA") is prohibited.
These materials are protected by the Copyright Act of 1976, as amended, as an unpublished work and the foregoing
notice and legend shall not be deemed to constitute publication or an intent to publish thereunder. These materials
are proprietary and confidential information of JDA and may be disclosed and used only as authorized in a signed,
written agreement controlling such disclosure or use.
The fact that a particular name or logo does not appear on this notice does not constitute a waiver of any
intellectual property rights that JDA has established in any of its products, feature or service names, or logos.
Modifications to the contents of this document

JDA reserves the right, at any time and without notice, to change these materials or any of the functions, features,
and specifications of any of the software described herein. JDA shall have no warranty obligation with respect to
these materials of the software described herein, except as provided in the JDA software license agreement with an
authorized licensee.
Rights to the functionality of this document

Described functionality may not be available as part of a customer's maintenance agreement or the JDA Investment
Protection Program. New features and products are subject to license fees. JDA warranty and support obligations
apply only to the documentation as delivered by JDA, and are void if the documentation is modified or
supplemented by anyone other than JDA. This document embodies JDA valuable trade secrets, is confidential to
JDA, and must be kept in confidence and returned upon the expiration or termination of your JDA license
agreement. You are not permitted to copy, extract, distribute, transfer, or share the contents of this document with
anyone except authorized individuals within your organization.
Technical documentation
NOTICE: This design or technical documentation is supplied as a courtesy only and does not form part of the
"Documentation" as defined in your JDA license agreement. This design or technical documentation is supplied in
the English language only and is supplied "as is" and without warranties. JDA, at its discretion, may choose to offer
this document in additional languages, but is under no obligation to do so. JDA undertakes no obligation to update
this design or technical documentation.
Patents
This product may be protected by one or more US patents. Please see the JDA Patents website
(http://jda.com/JDAPatents).
This product may be protected by one or more of the following non-US patents:
Europe Patent No. 0861474 (E) Taiwan Patent No. 161120 Taiwan Patent No. I222584
Europe Patent No. 0861474 (UK) Taiwan Patent No. 161181 Taiwan Patent No. I222585
German Patent No. 10195871 Taiwan Patent No. 161494 Taiwan Patent No. I222586
German Patent No. 69507020.7 Taiwan Patent No. 163816 Taiwan Patent No. I225208
German Patent No. DE10195968 Taiwan Patent No. 384430 Taiwan Patent No. I242952
Taiwan Patent No. 100569 Taiwan Patent No. 425517 Taiwan Patent No. I251760
Taiwan Patent No. 146038 Taiwan Patent No. 544598 Taiwan Patent No. M377652
Taiwan Patent No. 154327 Taiwan Patent No. 544599 Taiwan Patent No. NI-158220
Taiwan Patent No. 157467 Taiwan Patent No. I221578 Taiwan Patent No. NI-182974
Taiwan Patent No. 159609 Taiwan Patent No. I221978
Software implementation advisement

IMPORTANT: Although JDA licenses packaged software, JDA solutions offer complex capability and
scalability requiring trained, experienced personnel to install and implement. Even robust
documentation is no substitute for JDA certified consultants. JDA implementation experience in
addition to training, both on the JDA solutions and on their underlying technologies as defined in JDA
solution documentation, are the keys to success. Given JDA’s mission to ensure customers achieve
optimal results, JDA strongly recommends you use certified consultants who understand JDA
applications and delivery methodologies. Without this guidance, you can expect to experience
implementation challenges that cannot be addressed effectively under your JDA support agreement. In
these circumstances, JDA Support Services will refer you to the Consulting Services team who can be
engaged to answer questions and guide the implementation.
Software support
The JDA Solution Investment Policy includes three support levels to maximize your benefit. By
supporting only the newest software versions, JDA can provide you with exemplary service, allowing
you to realize an evolving return on your software investment. Through the JDAUser website
(http://www.jdauser.com), you can access a comprehensive summary of your licensed applications
and their current levels of support.
Provide feedback on this document

JDA values your opinion and strives to ensure that the documentation you receive is clear, concise,
and provides the appropriate information required for you to use each JDA application efficiently.
If you would like to provide feedback on this document, you can submit your questions or suggestions
to the JDA Documentation Management team (mailto:publication_services@jda.com) and they will
be forwarded to the appropriate development teams for review and consideration in a future release.
Table of Contents
Chapter 1. Overview ........................................................................................................ 1
Roadmap of installation .............................................................................................. 1
Deployment strategies................................................................................................ 1
Transportation Manager ..................................................................................... 1
Transportation Planner....................................................................................... 4
Deploy Transportation Planner components........................................................... 4
Chapter 2. Pre-requisites ................................................................................................. 6

Transportation Manager .............................................................................................. 6
Supported software and platforms ....................................................................... 6
License requirements......................................................................................... 6
Standard Oracle requirements ............................................................................ 6
Transportation Planner ............................................................................................. 12
Supported platforms and system requirements .................................................... 12
Modules ................................................................................................................. 13
Carrier Equipment Availability ........................................................................... 13
Approval Chain ............................................................................................... 14
Freight Auction ............................................................................................... 15
Transportation Manager Mobile .................................................................................. 16
ABPP project archive ....................................................................................... 16
ABPP runtime license key ................................................................................. 16
Database requirements .................................................................................... 16
Ports Configuration.......................................................................................... 16
Chapter 3. Pre-installation............................................................................................. 17
Transportation Manager ............................................................................................ 17
Overview of the upgrade process....................................................................... 17
Install third-party and other JDA components...................................................... 18
Install database components on Oracle .............................................................. 18
Install distance calculation engines .................................................................... 28
Send reports and notifications through fax and email ........................................... 33
Transportation Planner ............................................................................................. 36
Install third-party and other JDA components on Windows .................................... 36
Upgrade from an earlier version of TP on Windows ............................................... 38
Install third-party and other JDA components on Solaris ....................................... 39
Upgrade from an earlier version of TP on Solaris .................................................. 40
Install third-party and other JDA components on AIX ........................................... 40
Upgrade from an earlier version of TP on AIX ...................................................... 42
Chapter 4. Installation................................................................................................... 44
Install Transportation Manager server ......................................................................... 44
Prepare for the installation ............................................................................... 44
Install Transportation Manager server ................................................................ 45
Install the TM-Web interface for WebLogic ................................................................... 47
Prepare to Install the Web interface ................................................................... 47
Install the Web Interface .................................................................................. 48
Change the WebLogic configuration and ports ..................................................... 52
Configure web servers for proxy requests to TM .................................................. 54
Access the TM-Web interface on WebLogic .......................................................... 56
Install the TM-Web interface for WebSphere ................................................................ 56
Prepare to install the Web interface ................................................................... 56
Install the Web interface for WebSphere ............................................................. 58
Administer the WebSphere application server ...................................................... 60
Install the TM RIA-Web interface for WebSphere .......................................................... 65

TM installation directories for RIA ............................................................................... 66
Install Transportation Manager Mobile......................................................................... 66
CIS configuration ............................................................................................ 66
Service Parameters ......................................................................................... 67
Documents and Tables ..................................................................................... 67
Client Provisioning Service (CPS) Configuration ................................................... 67
Update TMGR Permissions ................................................................................ 67
Single Sign On (SSO) Configuration ................................................................... 68
Uninstall Transportation Manager ............................................................................... 69
Uninstall the TM-Web interface.......................................................................... 69
Uninstall Transportation Manager server ............................................................. 69
Uninstall Transportation Manager Mobile ............................................................ 69
Install Transportation Planner on Windows .................................................................. 70
Install TP programs on Windows........................................................................ 70
Installation results on Windows ......................................................................... 73
Uninstall TP programs on Windows .................................................................... 76
Install Transportation Planner on Solaris ..................................................................... 76
Install TP programs on Solaris .......................................................................... 77
Uninstall TP programs on Solaris ....................................................................... 81
Install Transportation Planner on AIX.......................................................................... 82
Install TP programs on AIX ............................................................................... 82
Uninstall TP programs on AIX ........................................................................... 87
Configure web servers for proxy requests to TP ............................................................ 87
Configure Apache to forward requests to the WebLogic server for TP ...................... 87
Other web servers ........................................................................................... 88
ABPP application package contents ............................................................................. 88
Deploy JDA Transportation Manager ABPP ................................................................... 89
Approval Chain ........................................................................................................ 91
Installation steps ............................................................................................ 91
Freight Auction ........................................................................................................ 91
Carrier Equipment Availability .................................................................................... 91
Chapter 5. Post-installation ........................................................................................... 92

Configure Transportation Manager.............................................................................. 92
Configure the Distributed Service Coordinator (DSC) ............................................ 92
Use parameter sets ......................................................................................... 96
Server logging levels ....................................................................................... 96
Preconfigured servers ...................................................................................... 97
Alternative configurations ................................................................................. 98
Servers for Routing and Rating calls ................................................................ 100
Single active instance servers ......................................................................... 101
Servers configuration .................................................................................... 101
Configure the Distance Calculator server .......................................................... 102
Configure the JDA infrastructure services interface............................................. 102
Configure the CIS adapter for TM event notification (Outbound) ........................... 104
Configure the monitoring server ...................................................................... 104
Configure the Process Monitor ......................................................................... 105
Configure SSL transport ................................................................................. 107
Configure TP on Windows........................................................................................ 113
WebLogic ..................................................................................................... 113
Configure TP on Solaris .......................................................................................... 115
Configure TP with WebLogic on Solaris ............................................................. 115
Configure WebLogic CLASSPATH information for CIS port.................................... 115
Deploy JDA Applications in Development Mode .................................................. 115
Deploy JDA Applications in Production Mode ...................................................... 116
Set up the TP help for deployment ................................................................... 116

Deploy applications from the WebLogic console ................................................. 116
Configure TP on AIX ............................................................................................... 117
Configure WebSphere with TP components ....................................................... 117
Deploy TP components on WebSphere ............................................................. 117
Configure the application server for use with TP ................................................ 117
Install TP as a new application ........................................................................ 118
Install the documentation library as a new application ........................................ 118
Start TP as an enterprise application ................................................................ 119
Configure Transportation Manager Mobile .................................................................. 119
Additional post-installation steps ..................................................................... 119
TM Mobile server configuration ........................................................................ 119
Transportation Manager System configuration ................................................... 120
Set CIS to ignore time zone information on dates .............................................. 120
Run the JDA Transportation Manager ABPP application ................................................ 120
Prerequisites ................................................................................................ 120
Run the application ....................................................................................... 120
Approval Chain ...................................................................................................... 122
Post-installation steps .................................................................................... 122
Directory locations ........................................................................................ 122
Configuration steps ....................................................................................... 122
Freight Auction ...................................................................................................... 130
Carrier Equipment Availability .................................................................................. 133
SSO configuration for Windows/WebLogic.................................................................. 136
Directory locations ................................................................................................. 136
JDA Infrastructure Services configuration .................................................................. 136
Enable Java security............................................................................................... 137
Enable SSO for JDA Transportation Manager web user interface.................................... 137
Set the SSO flag for application deployment ..................................................... 137
Configure the JDA Transportation Manager login module ..................................... 137
Enable SSO for JDA ABPP ............................................................................... 138
Validate SSO configuration ............................................................................. 141
SSO configuration for AIX/WebSphere ...................................................................... 142
Directory locations ........................................................................................ 142
JDA Infrastructure Services configuration ......................................................... 142
Enable SSO for JDA Transportation Manager web user interface ........................... 143
Chapter 6. Utilities and common tasks ........................................................................ 149

User interface extension ......................................................................................... 149
Transportation Smartbench ............................................................................ 149
Add Location Throughput Group Capacity Maintenance operations to the Transportation
Manager ...................................................................................................... 149
Test the servers .................................................................................................... 152
Test general connectivity ............................................................................... 153
Test Transportation Manager server functions ................................................... 153
Test email and fax connectivity ....................................................................... 158
Test the Web interface ................................................................................... 159
Environment ................................................................................................ 159
Environment ................................................................................................ 160
Test Oracle objects........................................................................................ 160
Download JDA TM App from Apple Store ................................................................... 160
Chapter 7. Troubleshooting ......................................................................................... 161

Install Gnome Display Manager (GDM) under Solaris 11-TM and TP ............................... 161
Remove IPV6 entries from the hosts file under Solaris 11-TM and TP ............................. 162
Appendix A. Software ordering information................................................................. 163
Appendix B. Server platform information .................................................................... 165

Servers available on both UNIX and Windows ............................................................ 165
Servers available only on Windows ........................................................................... 165
Index ........................................................................................................................... 166

Overview
Chapter 1. Overview
Roadmap of installation
This section describes the high-level tasks that are required to install Transportation Manger,
Transportation Planner, and the optional products.
Task Description Required or Optional

Step 1: Install CIS Agent Install JDA Infrastructure Services Required
Step 2: Install Transportation Install the Transportation Manager Distributer Required
Manager Server Service Contributor setup
Step 3: Install Transportation Install the Transportation Manager Web Required
Manager Web Interface interface
Step 4: Install Transportation Select the applicable Transportation Planner • Routing and Rating
Planner component to install is required
• Routing and Rating • OPT is required
• OPT (Optimization) • TP UI is optional
• TP UI (Transportation Planner Web User • SS is optional
Interface)
• SS (Shipment Scheduler)
Step 5: Install Modules • Carrier Equipment Availability Optional
• Freight Auction
• Approval Chain
Step 6: Install Single Sign-On Install Single Sign-on between Transportation Optional, applicable
Manager and ABPP modules only if you have
installed ABPP
modules in Step 5
Step 7: Install WebServer Web Servers to redirect the appropriate the
web traffic to the application server within the
network
Step 8: Install language packs Optional
Deployment strategies
Transportation Manager
Hardware and Network requirements
Following are the hardware and network requirements to install Transportation Manager.
Hardware
Servers
The hardware requirement for the size and configuration of servers depends on your storage
requirements, transaction volumes, and number of users. These numbers are obtained from a Sizing
Questionnaire. This is part of the Standard Sizing Worksheet, which is available from JDA Support. If
your numbers do not match one of the standard configurations in the Worksheet, request a custom
sizing engagement. The questionnaire is then processed by JDA to produce a recommended
configuration of servers including the number of servers required, number of CPUs, DASD, and RAM.
JDA Transportation Installation/Administration Guide 1
© 1995-2014 JDA Software Group, Inc.- Confidential
Overview
Server hardware must consist of a minimum of two server machines:
• one for the RDBMS

• one or more application servers running on a supported platform. see Software and Platforms.
Note: Configurations of four or more servers are common.
Clients
Assuming no other applications are significantly competing for client resources, the following client
workstation configurations are recommended:
Browser Clients
Platform Processing RAM * Free Disk *
Recommended Windows P4-2000+ 4 GB+ 2 GB
Minimum Windows P3-1000+ 2 GB 1 GB *
Notes:
• For more information on the supported Windows platform, see the JDA Transportation Manager
Release Notes.
• *Needed for smooth operation of the O/S. TM-Web application does not install components.
• The client machine must be configured with a supported operating system, along with a network
card and TCP/IP connectivity to the application servers (possibly through the Internet, for browser
clients). The product requires a video resolution of at least 1024 x 768 to be used effectively.
Network
Topology
If you are using Transportation Manager on UNIX or in a customized multi-host environment, then the
DSC processes need to communicate with each other using datagrams over UDP. These messages can
be transferred through switches and routers, but the servers require good bandwidth and low latency
between them to work efficiently.
LAN
A LAN speed of 100 Mbps (megabits per second) or more is recommended for communication between
servers (including the database server). However, 10 Mbps suffice for environments of up to 100,000
shipments per month. If a low speed LAN is being heavily utilized, performance issues can arise when
the Transportation Management environment is installed.
WAN: Browser clients

The average page size is about 40 KB, with large pages taking up to 60 KB. Assuming up to five page
refreshes per minute (which could include scrolling regions), the bandwidth requirement is about 25
Kbps. This is the minimum recommended bandwidth per active user.
In an actual deployment, you might require a large number of users to have simultaneous access to
the application. However, a much smaller number is anticipated to be active at any given time. The
others read the information on the page, or perform activities not involving the browser client.
Firewall
TM is designed to work closely with the database and must always be installed behind the firewall. Use
a proxy web server (such as. Apache or IBM HTTP Server), if you want to access TM WebUI outside the
firewall.

Overview
Test environments and Test plans

Each release is subjected to a thorough regression and functional testing process before it is available
for distribution. However, the application is highly configurable, and each customer environment is
unique. JDA recommends every customer to develop a formal test plan and run it thoroughly in a test
environment before applying any upgrade to the production servers.
Ensure an upgrade, that has passed the test acceptance criteria, provides reliable processing along
with all required functionality in the production environment of the customer. This is the best
protection against unexpected integration or customer-specific problems and potential downtime.
The upgrade must be tested on a separate physical machine (or logical partition if on UNIX) before
applying to the production server, since conflicts can arise from attempting to install multiple versions
of dependent software on the same server. Additionally, any installation of new software can put a
server at risk.
Depending on the volumes of transactions being tested, it is not necessary to use a server of the same
power as the production server. It is possible for all application components of Transportation Manager
and Transportation Planner to run on a single server, volume permitting (although RDBMS services
must be run on another machine). 1.6 GHz computer with 3 GB RAM, and 18 GB of DASD is sufficient
for moderate-volume application testing (less than 500 transactions per day). For UNIX environments,
you require a minimum of one 1.5 GHz processor, 4 GB of RAM, and 18 GB of DASD.
Fault tolerance, backup and recovery, and disaster recovery

These issues need to be addressed as part of the implementation process. Tolerance for the amount of
risk and downtime varies significantly between customers. The IT department of a company
establishes the requirements in this area. In many cases, customers have one or more cold stand-by
servers that can be manually brought into service in the event of a failure of any of the servers and
server functions they describe. Customers processing high volumes of transactions can elect for the
additional security (and expense) of an automatic fail-over solution that ensures uninterrupted service
in the event of any hardware failures.
The frequency and method for backups depend on how much downtime can be tolerated (if cold
backups are required), and loss of transaction processing can be tolerated in the event that the system
must be restored from backups.
It is important to have a backup and disaster recovery plan prepared in advance, and to periodically
test the integrity of system and database backups.
Personnel
Many companies are staffed with people capable of fulfilling multiple roles. Clarification and
commitment to the role assignments, response times, and level of involvement must be obtained in
the initial stage of the project to ensure a successful implementation.
Following are the technical roles required to implement and maintain Transportation Manager
installation:
DBA
• Creates instance and tablespaces based on JDA requirements before install date. See Standard
Oracle requirements (on page 6).
• Participates in planning and deployment of the RDBMS.
• Monitors space utilization and performance on an on-going basis to ensure maximum throughput
and sufficient available storage.
• Closely monitors the system as volumes pass one million containers shipped per month (for
example, 100,000 shipments with an average of 10 containers each).

Overview
Note: See Transportation Manager product integrity (on page 6) for warnings about changing the
database.
Application Administrator
• Works with support from JDA to perform the initial installation.
• Monitors server status and provides first level support in case you are not able to log on or perform
certain tasks.
• Performs product upgrades.
System Administrator (UNIX and Windows)

• Builds and configures application and RDBMS servers.
• Monitors system performance and resource utilization.
• Works with Application Administrator and/or DBA to resolve system performance or operating
system errors.
• Performs operating system upgrades (within application requirements).
Network Analyst
• Evaluates LAN and WAN readiness for product implementation.
• Monitors network performance and resource utilization.
• Resolves performance issues (including routing, latency, and uptime).
Transportation Planner
Deploy Transportation Planner components
This section provides information about deployment options for Transportation Planner (TP)
components and illustrates how these components are often installed within customer environments.
Note: These are general guidelines only. You should consider your own deployment requirements and
contact JDA for further guidance, if required.
Components
The Transportation Planner product suite includes several products with specific functionalities. The
Transportation Planner components integrate with other JDA products, including Transportation
Manager.
The major Transportation Planner components are:
• Routing and Rating Server

• Optimizer Server
• Shipment Scheduler Engine
• Transportation Planner web interface
• Shipment Scheduler web interface
Deployments
Typical deployments of the components are:
• Routing and Rating Server is installed to allow Transportation Manager to make rating calls. You
can deploy one or more instances of the Routing and Rating server.
Select RouteRate and Optimizer Server Install Set (RRO) to deploy this server.

Overview
• Optimizer server can be deployed as a stand-alone deployment or for use with Transportation
Manager.
You can deploy one or more instances of the Optimizer server and use the Transportation Planner
web interface in either type of deployment. Select RouteRate and Optimizer Server Install Set
(RRO) to deploy this server.
When you use the Optimizer Server with Transportation Manager, the requests for optimization are
generated from Transportation Manager. The Transportation Planner web interface can access
requests using the Transportation Manager Request server. You can display input in the interface,
send data to the Optimizer server, and review the output before sending the results to the
Transportation Manager Request server. The Transportation Manager Request server processes the
optimization results and writes the results to the Transportation Manager database.
The Transportation Manager Request server can also automatically access requests from the
Transportation Manager database, send them directly to the Optimizer server, and process and
write back the results to the database. This process does not require the Transportation Planner
web interface or any user interaction.
For deployment, select RouteRate and Optimizer Server Install Set (RRO).
When using the Optimizer server in a stand-alone deployment, the installed components are:
• Optimizer Server
• Transportation Planner web interface
The data source is typically XML files. Use the Transportation Planner web interface to select input
plans, send data to the Optimizer server, and review results. You can commit the results to files or
the database.
Select Custom Install Set > Route Rate and Optimization Server > Transportation Planner
UI Install Set (TPUI).
Optional deployments of the components are:
• Shipment Scheduler, in this deployment, the installed components are:

• Shipment Scheduler Engine
• Shipment Scheduler web interface
These components integrate to Supply Chain Planner through data in the Manufacturing ABPP
Basic (formerly Operational Data Store (ODS)) database or to JDA Fulfillment through data in
SCPO. You can deploy many instances of the Shipment Scheduler engine and each instance can
solve specific plans. For example, you may want to deploy separate instances to process plans
from different business units. The Shipment Scheduler user interface can connect to any of the
available instances. Shipment Scheduler Engine can handle multiple requests simultaneously based
on the number of threads configured in the Setup XML file. You can deploy one instance of
Shipment Scheduler engine and use it to solve different plans. A single instance can read and write
to different databases by overriding the Setup XML file together with the plan ID and instance ID.

Pre-requisites
Chapter 2. Pre-requisites
Supported software and platforms
To install Transportation Manager, you require:
• An operating system (for both the client and the application server)
• A web browser
• A relational database (RDBMS)
• A web server.
• Additional third party software (required, recommended, or optional).
See the Transportation Manager Release Notes for more information.
See Software ordering information (on page 163) for ordering the products that are not included.
License requirements
The software provided by JDA is protected by license keys. Ensure to order these keys in advance from
Product Support. You can order using JDAUser website (http://www.jdauser.com) by clicking
Online Support and selecting Request License Key.
Database upgrades are also packaged into Setup programs and require a product install key to open.
This is the same key that is used to install the Transportation Manager Servers and Web Interface, but
it changes between releases.
Third party products such as PC*Miler and WebLogic may have their own licensing requirements.
Ensure to procure any applicable license files or keys along with your software.
Standard Oracle requirements

The following section details the standard Oracle requirements for Transportation Manager.
Transportation Manager product integrity

Changes to the schema objects or data are not permitted, except as performed by the application, or a
JDA Support representative correcting a problem. The schema must contain only the standard objects
supplied by JDA.
Note: Any addition, modification, or deletion, or linking of foreign objects will void the warranty, and
might require a complete database reload from bootstrap to rectify, resulting in a loss of data.
Schema naming conventions

The following schema names are suggested. You can conform to your own naming requirements.
Standard schemas Optional additional schemas
Name Purpose Name Purpose

jdatm_prod Production jdatm_crp CRP
Schema
jdatm_train Training jdatm_at Acceptance Testing

i2tm_pstl Postal Data jdatm_demo Demo

Pre-requisites
Oracle Client configuration requirements (on Application servers)

• Install the correct version of the Oracle client on the application servers. See JDA Transportation
Manager Release Notes for supported database clients.
• For multi-byte environments (for example: Korean), set NLS_LANG=american_america.al32utf8
• Ensure that the NLS_LANG setting matches the server, if you are not using multi byte. For U.S.
English installs, the default is sufficient if you select the default character set. Otherwise, set it
explicitly. For example: NLS_LANG=american_america.WE8ISO8859P1.
• If a non-English version of Oracle is installed:
• Ensure to install US English messages into the Oracle rdbms\mesg folder for all application
servers. For example, C:\oracle\11g\rdbms\mesg. The application depends on these.
• Set a system environment variable NLS_SORT to match your server settings. For example,
BINARY, or KOREAN_M.
Oracle server configuration requirements

• Install the correct version of Oracle. For more information, see JDA Transportation Manager
Release Notes.
• Set the system to same time zone as TM and TM-Web servers.
• Oracle Client software on each server machine, and SQL*Net client/server connectivity.
• Character Set - if multi-byte is required, use AL32UTF8. Set Language to american, and Territory
to america (so, NLS_LANG=american_america.al32utf8).
• Character Set - if no multi-byte is required, use WE8ISO8859P1 (or another 8-bit Western
European set). US ASCII also works, but requires manual upgrade and configuration steps
(described later), and is therefore not recommended.
• Run the catalog and catproc scripts when instance is created.
• Separate Schema IDs for Transportation Manager data (and indexes) and Postal data (and
indexes).
• Schema IDs must have unlimited quota or no quota at all on their respective tablespaces, and
require privileges for connect, resource, and create materialized views.
• During setup, Schema IDs must have create view privileges so the required views are created
during import. The easiest way to accomplish this is to have the DBA run grant create view to
connect.
• Separate tablespace for each of Transportation Manager data, index, postal data, and postal index.
• Current size for Postal tablespaces is at least 350 MB for postal data and 450 MB for postal index.
• Temp tablespace of 500 MB, with appropriate extent sizes.
• UNDO management is recommended. However, if this is not being used, you need a minimum of
20 rollback segments: 19 with a minimum of 1 MB each, and 1 segment of at least 50MB for
upgrades (add more segments if required, there should be one segment for every four
transactions).
• Separate User and Tools tablespaces are not used by our application.
• Set archive log mode off during installation.
• Set minimum Redo Logs to 4 groups, 500M per log (groups must be multiplexed).
• INIT parameters:
• db_cache_size: Minimum: 20 MB, Recommended: 100 MB (see note below)

Pre-requisites
• shared_pool_size: Minimum: 150 MB, Recommended: 150+ MB (see note below)

• java_pool_size: Minimum: 150 MB (see note below)
• log_buffer: Minimum: 10 MB (see note below)
• open_cursors: Minimum: 500
• optimizer_mode: ALL_ROWS (default)
• compatible: 11.2.0.4
• cursor_sharing: EXACT (default)
• db_block_size: Minimum: 8192, Recommended: 16K
• job_queue_processes: Minimum: 100
• optimizer_index_caching: 90
• optimizer_index_cost_adj: 10
• processes: Minimum: 512, Recommended: 1000
Note: From Oracle 11g, Oracle recommends using Automatic Memory Management (AMM) feature of
the Oracle database. This is achieved by setting MEMORY_TARGET and MEMORY_MAX_TARGET parameters.
It is a total of sga_target(SGA) + pga_aggregate_target(PGA) internally. This parameter can be set to
an appropriate value based on the requirement. This causes Oracle to auto-tune the settings for DB
Buffer Cache, Shared Pool, Java Pool, Large Pool, SGA target and PGA target. This would also take care
of server-based sorting.
Oracle configuration recommendations

• Create a separate instance for use with Transportation Manager or Transportation Planner. This
helps to diagnose any performance issues.
• For a production environment, it is optimal to have a dedicated machine for the database server. If
the production installation is a critical part of the enterprise, then the production schema must be
the only schema within the production instance (separation of testing from production).
• The multi-thread server (MTS) is not recommended since the application manages its own
connection pooling.
• Start with a flat temp tablespace of 512 MB (must be flagged as temporary) and create it to be
locally managed. See Sample Scripts (on page 9) for examples of scripts to create locally managed
tablespaces.
• You can split large tablespaces into multiple files for back-up.
• For performance in a non-RAID environment, Redo Logs and Undo Tablespace (or Rollback) must
be on separate devices. It is also recommended the Temp Tablespace, Data Tablespace, and
indexes are on separate devices.
• Maintain separate tablespaces and devices for Materialized View data and indexes (apart from
those for regular data and indexes). Use a separate 30MB rollback segment during refresh and
other off-hours processing.
• In a RAID-5 environment, separation is not an issue provided there are sufficient number of
separate devices. However, for performance, it is recommended that under a RAID configuration,
Redo Logs must be set up on a Journalled Filesystem.
• Archiving must be activated in a production environment. The size of the archive logs must match
the redo logs (500 MB), and the log_buffer parameter in the Oracle initialization file must be
large enough to support this structure.
• Oracle 11g includes Automatic UNDO Management in response to performance and administrative
difficulties associated with rollback segments. In order to implement it, you must create the UNDO
tablespace, and add the following parameters to your INIT parameters file:
Pre-requisites
undo_management AUTO
undo_retention 1800
undo_suppress_errors FALSE
undo_tablespace UNDOTS1
Note: These are basic configuration recommendations. A production environment must be tuned by a
qualified DBA to maximize throughput, and address issues such as fault tolerance, backup and
recovery, and disaster recovery. A DBA is also required to monitor and manage database growth. (For
example: keeping the database from running out of extents or getting extremely fragmented and
requiring a reorg.)
Notes on installation
Sample scripts are provided for defining both the tablespaces and users, and the required schema.
These must be reviewed by the DBA and can be tuned to your requirements. The cr_usr.sql and
cr_tblspc.sql scripts must be run and the DBA must perform instance configuration in advance. You
require DBA access to run cr_usr.sql, revoke some rights after installing postal data, and create
synonyms to the postal data objects.
During installation, more scripts are run to define the actual schema. Note that the examples shown
here use separate tablespaces for main data and postal data. Indexes are also defined on separate
tablespaces for both types of data.
Materialized views and import errors

You cannot import materialized views from a schema export that has a different schema name than
the target schema (name hard coded in the DDL). Therefore, you must either drop the materialized
views and the associated package before exporting (not always possible on a production system), or
ignore the resulting errors upon import (the import terminates with an error code), and recreate the
views later. There are currently six materialized views, so the errors are repeated in groups of six.
This section includes instructions on how to recreate materialized views in the schema. This must be
done either in the source schema after the export is complete, or in the target schema after the import
is complete. The scripts drop_mviews.sql and create_mviews.sql are located in the database script
installation to help with these tasks.
The dump files do not include active materialized views.
Sample Scripts
The following are sample scripts that can be used when configuring Oracle to work with Transportation
Manager.
Create tablespaces
• create temporary tablespace temp
tempfile '/u04/oradata/qa2/temp01.dbf' size 512m
autoextend on next 512m maxsize unlimited
extent management local
uniform size 1m;
• create tablespace i2tm_pstl_data

logging datafile '/u04/oradata/tsdata/i2tm_pstl_data_1.dbf' size 350m
reuse extent management local uniform size 256k
segment space management auto ;

Pre-requisites
• create tablespace i2tm_pstl_index

logging datafile '/u03/oradata/tsdata/i2tm_pstl_data_1.dbf' size 450m
reuse extent management local uniform size 256k
• create tablespace i2tm_data

logging datafile '/u04/oradata/tsdata/i2tm_data_1.dbf' size 500m
reuse autoextend on next 100m maxsize unlimited
extent management local uniform size 256k
• create tablespace i2tm_index

logging datafile '/u03/oradata/tsdata/i2tm_index_1.dbf' size 500m
reuse autoextend on next 100m maxsize unlimited
extent management local uniform size 256k
Create users
/* cr_usr.sql – sample script for creating users */
/*
Create Schema: jdatm_crp
Description:
Application schema for Transportation Manager CRP
*/
create user jdatm_crp identified by jdatm_crp
default tablespace i2tm_data
temporary tablespace temp
quota unlimited on i2tm_data
quota unlimited on i2tm_index
grant connect , create view, resource, create materialized view
to jdatm_crp
alter user jdatm_crp default role all

Pre-requisites
/*Create Schema: jdatm_train
Description:
Application schema for Transportation Manager training data
*/
create user jdatm_train identified by jdatm_train
default tablespace i2tm_data
grant connect , create view, resource, create materialized view
to jdatm_train
alter user jdatm_train default role all
/*
Create Schema: i2tm_pstl
Description:
Postal validation data owner for Transportation Manager
*/
create user i2tm_pstl identified by i2tm_pstl
default tablespace i2tm_pstl_data
grant connect , resource
to i2tm_pstl
alter user i2tm_pstl default role all;

Pre-requisites
Supported platforms and system requirements

For more information, see the Transportation Planner Release Notes.
Note: Transportation Planner components and required software can be installed in various
configurations. Contact the JDA implementation team for an optimal configuration.
Software requirements by component

DB App ODS PC*
Componen SCP Rate MA
Clien Serv CIS /ABP LDAP VRML SVG
t O Miler Ware P
t er P
Optimizer Yes No Yes No No No Opt Opt No No No
Server
(SCE)
Routing Yes No Yes No No No Opt Opt No No No
and Rating
Server
(SCE)
Shipment Yes No Yes Yes2 Yes6 No No No No No No
Scheduler
Engine
Transportat No1 Yes Yes No3 No7 Yes5 No No Yes4 Opt No
ion Planner
Web UI
Shipment No1 Yes Yes No3 No7 Yes5 No No Yes4 No Yes
Scheduler
Web UI
Notes:
• Opt: Optional software, based on user requirements.
• No1: Even if you are using an Oracle database as a source, the web client machine does not
require the database client software to be installed.
• Yes2: Required if NOT using XML only; required only if using ODS/ABPP Basic as a data source.
• No3: Even when using the ODS/ABPP Basic as a data source, the web client machine does not
require the ODS/ABPP Basic software to be installed. This is handled by the Shipment
Consolidation Engine or Shipment Scheduling Engine.
• Yes4: Required to view Shipment Containers in the Transportation Planner or Shipment Scheduler
web user interface.
Caution: For the VRML viewer and Map viewer, you must adhere to the manufacturer’s terms of
use available at the manufacturer’s web site.
• Yes5: Required when using LDAP as the authentication method for the Transportation Planner web
user interface. You can use alternate authentication modules.
• Yes6: Required if NOT using XML only; required only if using SCPO as a data source.
• No7: Even when using SCPO as a data source, the web client machine does not require the SCPO
software to be installed. This is handled by the Shipment Scheduling Engine.

Pre-requisites
Modules
Before you install JDA Transportation Manager components, you should verify that the following
installation prerequisites are met:
• JDA Transportation Manager: JDA Transportation Manager must be successfully deployed. See
the JDA Transportation Manager documentation for details on installation and configuration.
• JDA CIS Adapter for JDA Transportation Manager: JDA Transportation Manager ABPP uses
CIS APIs to communicate with JDA Transportation Manager. See the JDA Transportation Manager
and JDA CIS documentation for details.
• JDA Transportation Manager Web UI: The JDA Transportation Manager web UI is required for
JDA Transportation Manager ABPP and JDA Transportation Manager to participate in a single sign
on session using the default JDA Transportation Manager login module. See Transportation
Manager Web Interface documentation for details.
The JDA ABPP runtime engine is installed as part of the JDA Transportation Manager ABPP
installation. The license key for JDA ABPP runtime 8.1 must be provided during this process.
• JDA CIS: JDA Infrastructure Services is a required component for JDA Transportation Manager.
See the JDA Infrastructure Services documentation for details.
Note: The database administrator creates tablespaces and an empty schema for JDA Transportation
Manager ABPP as specified in the installation guide for the application. The details of the schema are
required during application deployment.
Supported platforms and system requirements

To install Transportation Manager ABPP components, you require an operating system, web browser,
and relational database (RDBMS). See the Transportation Manager Release Notes for more
information.
Carrier Equipment Availability

JDA Transportation Manager Carrier Equipment Availability 8.1 requires the following software to be
installed and configured before you start the application.
• JDA Transportation Manager 8.1: Carrier Equipment Availability (CEA) is delivered as part of
the JDA Transportation Manager server installation. JDA Transportation Manager must be
successfully deployed before CEA is run.
• CIS Adapter for JDA Transportation Manager 8.1: Carrier Equipment Availability uses
Common Infrastructure Services (CIS) APIs to communicate with JDA Transportation Manager.
• Transportation Manager Web Interface for JDA Transportation Manager 8.1: Carrier
Equipment Availability requires access to a running Transportation Manager Web Interface.
Note: For more information on these software components, including the current versions, see the
JDA Transportation Manager Release Notes.
JDA CIS 8.1: JDA Infrastructure Services is a required component for JDA Transportation Manager.
For details on deploying the JDA CIS Agent and JDA CIS SSO Server, see the JDA Infrastructure
Services documentation.
Installation prerequisites
Agile Business Process Platform (ABPP) project archive
1. Locate deployCEA.jar in the installation package. It contains the Transportation Manager Agile
Business Process Platform component for CEA.
2. Select this jar file when prompted for the ABPP project archive during the installation.
Pre-requisites
ABPP runtime license key

The JDA Agile Business Process Platform (ABPP) runtime engine is installed as part of the JDA
Transportation Manager ABPP application installation. The license key for the JDA ABPP runtime 8.1
must be provided during this process. Contact JDA Support Services to request the JDA ABPP runtime
license key.
Database requirements
Create the following tablespaces for data and index, and associate the user and schema to use this
tablespace. See Create tablespaces (on page 9) for the standard Oracle tablespace creation
procedure.
Tablespace Purpose
jdatm_cea_data Data
jdatm_cea_inde Index
x
Note: The schema generation step fails if the listed tablespaces do not exist. You can skip the schema
generation during installation and reconfigure the table space later. See "Configure for different
tablespaces" (on page 135) for more information.
Approval Chain
JDA Transportation Manager Approval Chain 8.1 requires the following applications to be installed and
configured before you start the application.
• JDA Transportation Manager 8.1: Approval Chain is delivered as part of the JDA Transportation
Manager server installation. Transportation Manager must be successfully deployed before you run
Approval Chain. Refer to the Transportation Manager documentation for details on installation and
configuration.
• CIS Adapter for Transportation Manager 8.1: Approval Chain uses CIS APIs to communicate
with Transportation Manager. Refer to the Transportation Manager documentation for details on
how to configure this module.
• Transportation Manager Web Interface for Transportation Manager 8.1: Approval Chain
requires access to a running Transportation Manager Web Interface. Refer to the Transportation
Manager Web Interface documentation for details on how to install and configure this module.
• JDA CIS 8.1: JDA Infrastructure Services is a required component for Transportation Manager as
well. Refer to the Infrastructure Services documentation for details on deploying the JDA CIS Agent
and JDA CIS SSO Server.
• ABPP 8.1: Approval Chain requires ABPP 8.1.
Installation prerequisites
ABPP project archive
deployApprovalChain.jar file is located in the installation package and contains the Transportation
Manager ABPP component for Approval Chain.
Select this jar file when prompted for the ABPP Project Archive during the installation.

The ABPP runtime engine is installed as part of the JDA Transportation Manager ABPP installation. The
license key for the JDA ABPP runtime 8.1 must be provided during this process.
Contact JDA Customer Support Services to request the JDA ABPP runtime license key.

Pre-requisites
Create the following tablespaces for data and index, and associate the user and schema to use this
tablespace. See Create tablespaces (on page 9) for the standard Oracle tablespace creation
procedure.
Tablespace Purpose
jdatm_AC_data Data
jdatm_AC_index Index
Note: The schema generation step fails if the listed table spaces do not exist. You can skip schema
generation during installation and reconfigure the table space later. See Configure different tablespace
(on page 122) for more information.
Freight Auction
JDA Transportation Manager Freight Auction 8.1 requires the following software to be installed and
configured before you start the application:
• JDA Transportation Manager 8.1: Freight Auction is delivered as part of the JDA Transportation
Manager server installation. JDA Transportation Manager must be successfully deployed before
Freight Auction is run. For details on installation and configuration, see the JDA Transportation
Manager documentation.
• CIS Adapter for JDA Transportation Manager 8.1: Freight Auction uses Common
Infrastructure Services (CIS) APIs to communicate with JDA Transportation Manager. For details
on configuring this module, see the JDA Transportation Manager documentation.
• Transportation Manager Web Interface for JDA Transportation Manager 8.1: Freight
Auction requires access to a running Transportation Manager Web Interface. For details on
installing and configuring this module, see the Transportation Manager Web Interface
documentation.
Note: For more information on these software components, including the current versions, see the
JDA Transportation Manager documentation.
• JDA CIS 8.1: JDA Infrastructure Services is also a required component for JDA Transportation
Manager. For details on deploying the JDA CIS Agent and JDA CIS SSO server, see the JDA
Infrastructure Services documentation.
• JDA Agile Business Process Platform 8.1: Freight Auction requires ABPP 8.1.
Installation pre-requisite
Agile Business Process Platform project archive
Locate deployFreightAuction.jar in the installation package. It contains the Transportation Manager
Agile Business Process Platform (ABPP) component for Freight Auction.
Select this jar file when prompted for the ABPP project archive during the installation.

Transportation Manager ABPP application installation. The license key for the JDA ABPP runtime 8.1
must be provided during this process. Contact JDA Support Services to request the JDA ABPP runtime
license key.
Create the following tablespaces for data and index, and associate the user or schema to use this
tablespace. For standard Oracle tablespace creation procedure, see the Create tablespaces (on page 9)
.
Pre-requisites
Tablespace Purpose
jdatm_FA_dat Data
a
jdatm_FA_ind Index
ex
Note: The schema generation step fails if these table spaces do not exist. You can skip the schema
generation during installation and reconfigure the table space later. For more information, see
Configure for different tablespaces (on page 132).
Transportation Manager Mobile

ABPP project archive
The TmMobile.jar file, located in the installation package, contains the ABPP components for the TM
Mobile installation. Select this jar file when prompted for the ABPP project archive during installation.

Transportation Manager ABPP installation. The license key for the JDA ABPP 8.1 runtime is provided
during this process.
Contact JDA Support Services for the JDA ABPP runtime license key.
Create the following tablespaces for the data and index, and associate the user and schema to use this
tablespace. See "Create Tablespaces" (on page 9).
• jdatm_mobile_data
• jdatm_mobile_index
Note: Schema generation fails if these tablespaces do not exist. You can skip the schema generation
during installation and reconfigure the table space later.
Ports Configuration
Following is the recommend setup for the ports:
• CIS Webservices: 8088 (cisport)

• TM Weblogic: 7001 (tmport)
• Oracle Weblogic and ABPP: 7010 (abppport)
By default, TM Weblogic and Oracle Weblogic both install on 7001. So, for the connections to work, you
need to make sure during installation that these are configured to be on separate ports. This is
specified during installation. All ABPP webservice requests from the mobile app run through port 7010.
ABPP communicates to TM over port 7001. TM communicates with CIS for authentication, and web
service requests over port 8088.

Pre-installation
Chapter 3. Pre-installation
Overview of the upgrade process
Note: On UNIX systems, installers cannot run if you have not already installed the required version of
the Java Development Kit (JDK) and made this the default version in your PATH. Run java -version
to confirm you are using the correct Java version.
1. Use the following steps to upgrade an existing installation of Transportation Manager:
2. Order your installation Product Keys from support in advance.
3. If your schema is older than version 6.0.1, contact JDA support to upgrade.
4. Back up all servers and databases.
5. Ensure that you have created postal tables (for example, pstl_cd_t) in the existing version even if
they are just empty ones. The schema upgrade fails if they do not exist.
6. Ensure there is enough free space in the tablespaces. See Upgrade existing schemas (on page 21).
7. Export your databases and upgrade the Oracle server to current supported version. See JDA
Transportation Manager Release Notes for the supported database version.
8. Verify if the Oracle server parameters meet the current requirements as specified in JDA
Transportation Manager Release Notes.
9. Upgrade the schemas to the current version. See Upgrade existing schemas (on page 21). These
steps also include the process for upgrading your postal schema.
10. If you are using Materialized views (Reporting center), ensure you recreate them as instructed in
Upgrade existing schemas (on page 21).
11. Verify if the Oracle database clients on all application servers (including the Transportation Planner
and Web Application servers) are upgraded to the applicable version.
Note: When upgrading an Oracle client, your default Oracle domain (for example: world) can be
cleared out. This can be reset from the Oracle Net Manager by navigating to Local > Profile and
resetting the Default Domain.
12. Ensure that all Oracle clients are properly configured with NLS settings and US English error
messages. See Oracle Client configuration requirements (on Application servers) (on page 7).
13. Ensure that your application servers, clients, and browsers are upgraded to the required operating
system version and patch level, see JDA Transportation Manager Release Notes.
14. Upgrade to the required version of third party software on your application servers, see JDA
15. Uninstall any old versions and install the current Transportation Manager servers. See Install
Transportation Manager server. (on page 44)
16. Purge your cached distances if the Distance Engine has been changed or upgraded and you are
using Distance Caching. See Install distance calculation engines (on page 28).
17. Install the Web Interface. See the chapter which applies to your platform.
18. Uninstall or reinstall the Transportation Planner.
19. Update the dependent software and data to meet the current requirements. See JDA

Pre-installation
Install third-party and other JDA components

Install the required JDA and third-party components for specific platforms before installing
Transportation Manager. For the full list of required software, see the JDA Transportation Manager
Release Notes.
Install database components on Oracle

The following procedures describe how to install the database components for an Oracle database. Run
the program on a supported application server platform (Windows, Solaris, or AIX) even if your
database is running on another platform. The machine on which you install the database utility and
scripts must be installed with a compliant version of either the Oracle Server, or the Oracle client and
utilities, and include the Java utilities and jdbc libraries.
Configure the Oracle server

Transportation Manager uses server-based sorting to improve the response time of row order resorting
in the user interface, and uses materialized views to enhance the reporting performance.
Ensure that the Oracle server is properly configured so that these activities do not adversely affect the
overall database performance. Some suggested settings are provided below. If you have not previously
installed Transportation Manager, see JDA Transportation Manager Release Notes.
1. Ensure that your database is using a supported character set: AL32UTF8, or WE8* (any 8-bit
Western European), or US ASCII. Verify this using the following SQL;
select value from v$nls_parameters where parameter='NLS_CHARACTERSET';
2. Set the database block size INIT parameter to at least 16384 bytes (16 KB) to accommodate large
indexes in the application. For example:
db_block_size = 16384
3. Set the job queue processes INIT parameter to at least 100 as shown below:
job_queue_processes = 100
4. If importing a schema (bootstrap, training data, or a copy of your own schema), ensure that the
create view privileges have been granted as described in Oracle server configuration requirements
(on page 7).
5. Restart the Oracle server to implement the changes you have made.
Install Oracle database scripts

Run the setup program before the Database utility program, to install the Transportation Manager
Database scripts. Ensure to run the program on the applicable Windows system, or a supported UNIX
system with the required Oracle client or server software and Javasoft JDK. See JDA Transportation
Manager Release Notes.
1. Run DBSetup from the \Database directory in the product for Windows.
2. Run sh DBSetup.bin from an X window such as xterm for UNIX. You do not need X windows if
using the silent install.
3. Click Next to dismiss the Introduction screen.
4. Read the Software License Agreement Terms and select I accept if you agree and wish to
continue. Click Next.
5. Enter the full path to the Signed License File issued by JDA Support. Click Next.
6. Select a path to install Transportation Manager Database scripts, for example:
C:\jda\tmgr\8.1\Database. Click Next.
7. Enter the path to your JDK installation and click Next.

Pre-installation
8. Select Oracle as your database type and click Next.

9. Enter the path to your database client software and click Next.
10. Click Install to copy the database scripts to the selected location.
Note: The installation pauses for a couple of minutes at the end while it configures the files to
match your operating system.
11. Click Done to complete the installation.
You are now ready to create a bootstrap schema, or upgrade an existing schema.
Create a bootstrap schema

Use the following procedure to create a new schema that initially contains only bootstrap (system)
data. It will not contain any user data until later. You need the system user password to perform this
process.
Create a bootstrap schema using GUI mode

1. If running on Windows, start the Database Utility program by double-clicking on
run_DButilityGUI.bat in the directory where you installed the Database scripts.
2. If running on UNIX, start the Database Utility from an X window such as xterm by running sh
run_DButilityGUI.sh from the directory where you installed the Database scripts.
3. Select Oracle as the database and click Create Bootstrap.
4. Enter the path to the location of the script files, for example:
./Oracle/scripts
5. Enter the System Password.
6. Enter the Schema Name for the new schema, and the desired Schema Password.
Note: Ensure that you use a valid format for your schema name, for example, no dashes.
7. Enter the TNS Alias name for accessing the Oracle database.
8. Enter the required Data Tablespace and Index Tablespace.
9. Enter the Temporary Tablespace for the new schema to use.
10. Click OK to proceed with the database check.
11. Check the Console window for any errors, and click Start Selected Task.
The program now creates the schema and loads the bootstrap data, including the Reporting Views.
It takes around half an hour.
Complete the bootstrap schema configuration

1. Once the program completes, it verifies the logs automatically and informs you if any errors are
detected. Bootstrap logs are located at Oracle\scripts\Logs, that is under the directory where
you installed the database scripts. If needed, you can also verify manually, by running the
following command from that directory:
On Windows: findstr /ni ORA- boot*
On UNIX: grep -i ORA- boot*
2. If the system is not using postal data, connect to the new schema using sqlplus and create empty
postal objects using the Pstl_obj_create.sql script located in the Oracle\scripts directory where
you installed the database scripts as follows:
@Pstl_obj_create.sql

Pre-installation
It prompts you for the postal data and index tablespace names. You can just use the standard
tablespaces in this case, for example, i2tm_data and i2tm_index. Run the recompile.sql script
to update the address package.
3. If you are using postal data, and this schema was added after the postal data was created,
initialize the postal availability flags by running the setPstlFlag command from the Tools directory.
This must be done on a Windows Transportation Manager server system with a database client
using the following format:
setPstlFlag <DB User Name> <Password> <Database>
For example, setPstlFlag jdatm_crp jdatm_crp jdatmdb
Set the Distance Engine ID for Distance/Transit

The default Distance Engine setting for bootstrap data is PC*Miler for U.S and Canada only. Modify this
within the application if you are using a different distance engine or additional countries. See Configure
the Distance Calculator server (on page 102).
You can now create the materialized views.
Materialized views
Materialized views (or snapshots) are used to minimize the impact of ad-hoc reporting on database
performance. Certain web reports fail if these views are not created. The bootstrap and training
schemas are shipped without materialized views activated to allow your administrator to customize the
configuration to your needs and to avoid import errors that occur when the target schema name is
different from the source. For requirements and additional information, see JDA Transportation
Manager Release Notes. Further details are also available in the Oracle documentation.
Click Reporting Center on the Database Utility program and enter the applicable fields to create the
materialized views.
Note: Data and Index tablespaces must be different from the schema defaults to improve
performance. The Refresh Frequency for materialized view data is typically 24 (once every 24
hours).
Create a bootstrap schema using command mode

1. Open a command window in the directory where you installed the database scripts.
2. Edit the DbUtility.cfg file (save a backup copy) and update the following values:
• script_path =./Oracle/scripts
• database_type =oracle
• task_to_perform =Boot
• # parameters for oracle - various - set your Oracle connect info here
• # bootstrap parameters for oracle - various - set your tablespace info here
3. Run the run_DButilityCMD command (run_DButilityCMD.sh on UNIX) to perform the requested
operation.
The program now creates the schema and loads the bootstrap data, including the Reporting Views.
It must complete within 15 minutes (command mode is faster than GUI mode for bootstrap
creation).
4. Proceed with the completion steps. see Complete the bootstrap schema configuration (on page
19).

Pre-installation
Update postal data

See the instructions in postal data or in the localized zip file received from JDA Support. This process
initializes postal availability flags in your new schema. Ensure to run the required steps as each
schema is created.
Upgrade existing schemas

The Database utility program used for creating Bootstrap data is also used for upgrading your
schemas. The program scans the error logs after each phase of the upgrade to avoid running the
processing scripts again, which is time consuming.
The standard upgrade program for the current version is used for both patch upgrades and major
upgrades.
Note: If your Oracle schema is older than version 6.0.1, contact JDA support for the required steps to
upgrade.
You need the password to the Oracle system account, and the upgrade must be run from a supported
application platform installed with the correct version of the Oracle Client software and utilities. See
JDA Transportation Manager Release Notes.
Perform the following procedures for all applicable schemas. In the event of an error during the
upgrade, the program instructs you what to check, and how to continue. In case where an error is not
recoverable, you must reload the schema from backup, correct the problem, and then run the upgrade
again.
Prepare for the upgrade

1. Ensure that no one is logged into the Oracle database instance.
2. Ensure that there is free space available in the tablespaces (10% is minimum, 20% is ideal).
3. Connect to the database using the "system" account, for example:
sqlplus system/manager@jdatmdb
4. Grant materialized view privileges to the schema to be upgraded, for example:
grant create materialized view to jdatm_crp;
5. Grant unlimited quota to the schema on relevant tablespaces, for example:
alter user jdatm_crp quota unlimited on i2tm_data;
alter user jdatm_crp quota unlimited on i2tm_index;
6. Reserve the instance and schema for exclusive use by temporarily changing the passwords, for
example:
alter user system identified by locked4upgrade;
alter user i2tm identified by locked4upgrade;
7. Exit from sqlplus.
8. Stop and restart the database instance.
9. Back up the schema you are about to upgrade by exporting it to a .DMP file. To do this, open a
command prompt and type the exp command in the following format:
exp <Schema_ID/Password@dbalias> file=<filename>
For example:
exp jdatm_crp/jdatm_crp@jdatmdb file=jdatmcrp.dmp
10. Upgrade Oracle to the applicable version. See JDA Transportation Manager Release Notes.
11. Ensure that you have installed the Database scripts and utility. see Install Oracle database scripts
(on page 18).
12. You need the following information ready before continuing:

Pre-installation
Min. free Your information

Item
space here
Oracle system password n/a *******
Schema name to be upgraded n/a

Schema password n/a *******
Data tablespace name 25%
Index tablespace name 25%
Materialized view information n/a
Data Tablespace 30 MB
Index Tablespace 30 MB
Desired data refresh rate in hours (6, 12, n/a
or 24)
13. Check that your database is using a supported character set. (See Configure the Oracle server (on
page 18)). If not, contact JDA Support for further instructions.
Note: You are now ready to upgrade the postal schema.
Upgrade the Oracle postal schema

If you only have empty postal tables, there are two scripts that need to be installed by the DB utility in
the Oracle\scripts subdirectory: Pstl_obj_delete.sql and Pstl_obj_create.sql. In this case, you
can connect to your TM schema using sqlplus and run the delete script and then the create script to
update your empty postal objects. Run recompile.sql to update the address package, and you can
then skip the rest of the postal upgrade section.
Note: Pstl_obj_delete.sql cannot run if there are rows in the city_t, pstl_cd_t, or pstl_cd_rng_t
tables. If only pstl_cd_rng_t has rows, you can delete them before running pstl_obj_delete.sql.
This table can be regenerated in your postal schema later as described in "For Older Schemas" (on
page 24).
If your postal data is not empty, proceed with the following steps:
Upgrade postal schema to version TM 6.2.1 (for older schemas)

You do not need to do these steps if you have previously upgraded the postal schema to this level.
This procedure has a step to check for that.
1. Open a command window in the directory where you installed the database scripts, for example,
c:\jda\tmgr\8.1\Database
2. Change to the Oracle\scripts directory that is found beneath it.
3. Connect to the database as the postal schema user, for example,
sqlplus i2tm_pstl/i2tm_pstl@MyDBAlias
4. Run @Pstl_cd_rng.sql to ensure that the pstl_cd_rng_t table is up to date (this script can be
re-executed without doing any harm). If you get a message that the table does not exist, you can
ignore it. For more information , see "For Older Schemas" (on page 24).
5. Enter a commit; command to commit the changes.
6. Check that other postal tables have not already been upgraded for TM 6.2.1 with the following
command:
describe pstl_cd_t;
If the PSTL_ID field already exists, exit from sqlplus and skip to the next section.
7. Exit from the sqlplus program.

Pre-installation
8. Edit the pstl_upgrade_621.sql file and replace &INDEX_TABLESPACE with your postal index
tablespace name, for example, i2tm_pstl_index.
9. Execute the postal upgrade script using a command in the form shown below. It will take 30
minutes or more, depending on the number of records in your table.
sqlplus i2tm_pstl/i2tm_pstl@MyDBAlias @pstl_upgrade_621.sql
10. Exit the sqlplus program.
Upgrading postal schema to version TM 6.3.1.
1. Extract the files from pstl_upgrade_631.zip under scripts folder, for example,
c:\jda\tmgr\8.1\Database\Oracle\scripts\pstl_upgrade_631.zip to a temporary directory,
for example C:\temp.
2. Connect to your postal schema and run the pstl_upgrade_631.sql script, for example, sqlplus
i2tm_pstl/i2tm_pstl@myalias @pstl_upgrade_631.sql
The script will prompt you for :
• logfile name
• index tablespace (for postal indexes - for example, i2tm_pstl_index)
• data tablespace (for postal data - for example, i2tm_pstl_data)
It will then create the new ctry_pstl_t table and index, populate it from pstl_cd_t and city_t, and
recreate sequences pstl_cd_rng_tseq and pstl_cd_tseq based on the latest pstl_cd_rng_id
and pstl_id values, respectively. It also does a grant select on the new table to public.
3. There is another script called cleanTMschema.sql which drops specific postal objects from your TM
schema, since they should now all be located only in the postal schema. This script should be run
for each TM schema as in the following example (you can ignore missing object errors - not all TM
schemas have these objects):
sqlplus tmschema/tmschema@myalias @cleanTMschema.sql
4. You need to create public synonyms so that users other than just the postal schema user can
access the postal data. This is done using a DBA login and the pstl_cr_synonyms.sql script as in
the following example (assuming your postal schema is i2tm_pstl and your system password is
passwd).
sqlplus system/passwd@mydbalias @pstl_cr_synonyms.sql i2tm_pstl
5. Finally, if you will be using the postal data APIs to update postal data, you need to grant
permissions to the TM schema user to update postal tables. Login to your postal schema (for
example, i2tm_pstl) using sqlplus and run the following grants (substitute your own TM schema
name for tmschema):
grant select on pstl_cd_rng_tseq to tmschema;
grant select on pstl_cd_rng_t to tmschema;
grant delete on pstl_cd_rng_t to tmschema;
grant insert on pstl_cd_rng_t to tmschema;
grant update on pstl_cd_rng_t to tmschema;
grant select on addr_pars_t to tmschema;
grant delete on addr_pars_t to tmschema;
grant insert on addr_pars_t to tmschema;
grant update on addr_pars_t to tmschema;
grant select on city_t to tmschema;
grant delete on city_t to tmschema;
grant insert on city_t to tmschema;
Pre-installation
grant update on city_t to tmschema;

grant select on ctry_pstl_t to tmschema;
grant delete on ctry_pstl_t to tmschema;
grant insert on ctry_pstl_t to tmschema;
grant update on ctry_pstl_t to tmschema;
grant select on pstl_cd_tseq to tmschema;
grant select on pstl_cd_t to tmschema;
grant delete on pstl_cd_t to tmschema;
grant insert on pstl_cd_t to tmschema;
grant update on pstl_cd_t to tmschema;
commit;
quit
If your postal schema has a pstl_cd_rng_t table, you can skip the next section.
For older schemas

Some older installations that have not updated postal data in many years may only have a
pstl_cd_rng_t table in the TM schema, not the postal schema. It is now possible to regenerate this
table using the new processPostalCodeRangesRebuild API.
If you have no pstl_cd_rng_t in your postal schema, you can run the Pstl_obj_create.sql script
(found in the Oracle\scripts directory from your DB Utility install) to create any missing postal
objects - existing ones are unaffected.
Next, you must login to the postal schema, for example i2tm_pstl, and grant the following privileges
to the TM schema (substitute the correct name for tmschema):
grant select on pstl_cd_rng_tseq to tmschema;

grant select on pstl_cd_rng_t to tmschema;
grant delete on pstl_cd_rng_t to tmschema;
grant insert on pstl_cd_rng_t to tmschema;
grant update on pstl_cd_rng_t to tmschema;
Once the TM application has been installed, you can use the processPostalCodeRangesRebuild API
to rebuild the pstl_cd_rng_t for each applicable country. The XML file for this is very simple, as in the
following example for USA:
<?xml version="1.0" encoding="UTF-8" ?>

<CISDocument>

<CountryCode>USA</CountryCode>
</CISDocument>
It could then be executed from the CIS_HOME\bin directory using the following command (assuming
you named your file C:\temp\PostalRngUSA.xml and VENTURE is a valid TM user and password):
launch cisRequestEx.py TransportationManager processPostalCodeRangesRebuild

c:\temp\PostalRngUSA.xml user=VENTURE password=VENTURE

Pre-installation
Note: In case of error, refer to the CISSrv_pid* log files under TM_HOME\logs. One common error
is "cannot create object because it already exists", which occurs when you have not granted proper
privileges as listed above. You are now ready to upgrade the TM schema to the current version of
Transportation Manager.
Upgrade the schema using GUI mode

1. If running on Windows, double-click run_DButilityGUI.bat in the directory where you installed
the Database scripts to start the Database Utility program.
2. If running on UNIX, start the Database Utility from an X window such as xterm by running sh
run_DButilityGUI.sh from the directory where you installed the Database scripts.
3. Select Oracle as the database and click Upgrade Schema.
4. Enter the path to the location of the script files, for example:
./Oracle/scripts
5. Enter the System Password.
6. Enter the Schema Name and Schema Password for the schema to be upgraded.
7. Enter the TNS Alias name for accessing the Oracle database.
8. Enter the required Data Tablespace and Index Tablespace.
9. Click OK to proceed with the database check.
10. Check the Console window for any errors, and click Start Selected Task.
The program now upgrades the schema and loads the Reporting Views. Depending on the size of
your schema, it can take several hours for very large databases (50 GB). The program
automatically verifies the logs for any errors. When this task is finished, skip the next section and
proceed with Complete the upgrade (on page 26).
Note: If errors are detected, you can verify the logs by running the following command in the
Oracle\scripts\Logs directory where you installed your Database scripts:
On Windows: findstr /ni ORA- h*
On UNIX: grep -i ORA- h*
Upgrade the schema using command mode

1. Open a command window in the directory where you installed the Database scripts.
2. Edit the DbUtility.cfg file (save a backup copy) and update the following values:
• script_path = ./Oracle/scripts
• database_type = oracle
• task_to_perform = Upgrade
• # parameters for oracle - various - set your Oracle connect info here
• # upgrade for oracle - various - set your tablespace info here
3. Run the run_DButilityCMD command (run_DButilityCMD.sh on UNIX) to perform the requested
operation.
The program now upgrades the schema and loads the Reporting Views. Depending on the size of
your schema, it can take several hours for very large databases (50 GB). The program
automatically verifies the logs for any errors.
Note: If errors are detected, you can verify the logs by running the following command in the
Oracle\scripts\Logs directory where you installed your Database scripts:
On Windows: findstr /ni ORA- h*
On UNIX: grep -i ORA- h*

Pre-installation
Migrate country code of Romania from ROM to ROU

Note: These steps are required only to migrate the country code of Romania from ROM to ROU. The
script aborts if the postal schema data tables are not accessible to TM schema.
Note: These steps are not required:
• If you are installing Transportation Manager for the first time and using the latest schema. The
script is already included in the bootstrap schema to have new country code, ROU.
• If you have already migrated to a new country code, ROU.
• If upd_ROU_ctry_810.sql has been run after the upgrade to TM 8.0.
1. After the installation (DB creation, schema creation etc.), login to the TM schema through
SQLPLUS using the following command:
sqlplus <tm_Schema>/<password>>@<<DB_name>
2. Run the following command to execute the upd_ROU_ctry_810.sql script:

SQL> @<fully qualified path>\upd_ROU_ctry_800.sql
Note: No parameters must be passed to the script.
Complete the upgrade

1. Verify the default distance engine settings for each country in use. See Configure the Distance
Calculator server (on page 102).
2. Connect to the database using the system account, for example:
sqlplus system/manager@jdatmdb
3. Release the instance and schema from exclusive access by changing back the passwords modified
during preparation.
4. If your database is using a US ASCII character set, connect to your schema as the schema owner,
and run the code_Latin.sql script to initialize the character set for the schema. This script is found
in the Oracle\scripts directory where you installed your Database scripts.
Analyze the schema and indexes

A qualified DBA must analyze the schema whenever there has been a significant change to the amount
or distribution of data and indexes. This process ensures that the Oracle query optimizations are
relevant and effective. Each version updates several indexes, so the schema must be analyzed to
ensure that there is no deterioration in performance.
The following process can be run by an administrator with access to the schema. It can take several
hours to complete a large schema.
1. Run the analyze.sql script in the command window in the existing C:\scripts directory as
follows:
sqlplus <Schema_ID/Password@dbalias> @analyze.sql
For example,
sqlplus jdatm_crp/jdatm_crp@jdatmdb @analyze.sql
This command performs a statistics estimate on the schema.
2. Run the analyze_ind.gen script to generate SQL for the next step as follows:
sqlplus <Schema_ID/Password@dbalias> @analyze_ind.gen
For example,
sqlplus jdatm_crp/jdatm_crp@jdatmdb @analyze_ind.gen
This command generates an SQL file (@analyze_ind.sql). Do not exit from the SQL prompt.
Pre-installation
3. Run the following command from the SQL prompt, to run the SQL script just created (performs a
compute statistics on all the indexes in the schema):
@analyze_ind.sql
Note: A script called analyze_pstl.sql is also provided in the same directory. This script is run to
analyze the schema and indexes for the postal data. This is required when the postal data is initially
created, and also if you use the postal APIs to change postal data.
For example, sqlplus i2tm_pstl/i2tm_pstl@jdatmdb @analyze_pstl.sql
Materialized views
If you are using the Reporting Center, ensure to drop and recreate the Materialized Views as instructed
in Materialized views (on page 20).
Create a training schema (optional)

Use the following procedure to create a schema that contains training data. You must also create
Materialized views once these steps are completed, if using the Reporting Center.
1. Create a new schema ID with an appropriate default tablespace, temporary tablespace, resource,
connect, and materialized view privileges. For example, see the crusr.sql script in Standard Oracle
requirements (on page 6).
2. Install the Database scripts (if not already done in a previous step) by running DBSetup from the
\Database directory in the product directory. See Installing the Oracle database scripts (on page
18) for details on running this installer.
3. Open a command prompt window in the \Oracle\scripts directory where you installed your
database scripts.
4. Import the training data into the correct schema using the following format (buffer size is 30
followed by six zeros or 30 million bytes):
imp <Schema_ID/Password@dbalias> file=<dump file> full=y buffer=30000000
For example:
imp jdatm_train/jdatm_train@jdatmdb file=train63.dmp full=y buffer=30000000
Note: The reporting views are already included in the training schema.
5. Connect to the training schema using SQLplus.
For example:
sqlplus jdatm_train/jdatm_train@jdatmdb
6. Recompile the schema objects using the @recompile command.
7. Check for objects in the schema that are not valid.
select * from user_objects where status <> ‘VALID’;
9. Create the Materialized views where applicable. See Materialized views (on page 20).
10. Modify the distance engines for the schema if you are not using PC*Miler, or if you are using
countries other than the U.S. and Canada. See Configure the Distance Calculator server (on page
102).
11. If this system is not using postal data, connect to the new schema using sqlplus and create empty
postal objects using the Pstl_obj_create.sql script (found in the Oracle\scripts directory where
you installed the Database scripts) as follows:
@Pstl_obj_create.sql

Pre-installation
It prompts you for the postal data and index tablespace names. You can use the standard
tablespaces in this case, for example, i2tm_data and i2tm_index. You must then run the
recompile.sql script to update the address package.
12. If using postal data, and this schema is added after the postal data was created, initialize the
postal availability flags by running the setPstlFlag command from the Tools directory. This must
be done on a Windows Transportation Manager server system with a database client using the
following format:
setPstlFlag <DB User Name> <Password> <Database>
For example, setPstlFlag jdatm_crp jdatm_crp jdatmdb.
Install distance calculation engines

If you require distance-based ratings, install one or more of the following distance calculation engines.
The following steps describe how to install the third party software. For information on configuring
Transportation Manager to use your distance engine, see Configure the Distance Calculator server (on
page 102).
Note: Software must be installed on each server that calls the distance interface. In general, all
machines hosting servers for Transportation Manager and Transportation Planner, except for a stand-
alone Web Application server, that requires an installation of distance software.
If you are using the distance cache feature, ensure that you purge cached distances any time you
change or upgrade the distance engine. You cannot perform the following steps until you install the
latest TM-Web Interface software.
Purge cached distances

1. Start the DSC process and the TMweb interface.
2. Start the FinancialAndBatchServer.
Note: This process also controls the purge request queue.
3. Use a browser client to login to the TM-Web UI as an administrator.
4. Navigate to Environment > Supplementary Purge from the Navigation Pad on the left.
Note: If you cannot see this item, see the next section for the steps that enable you to access this
function.
5. Select the Purge Distance Cache check box.
6. Select your applicable Distance Engine from the drop-down box to the right.
7. Click Submit to create a purge request.
Note: You can monitor the status of the request by navigating to Miscellaneous > Requests from
the Navigation Pad. The request takes up to six minutes to process, depending on the parameter
setting for ProcessInterval (in seconds) in the FIN parameter set.
Enable user access to Supplementary Purge

1. Login to the TM-Web Interface as an administrator.
2. Navigate to Environment > User Groups.
3. Select the Security User Group and click Nav Pad Modules.
4. Select Environment and click Contents.
5. Select Supplementary Purge and click Properties.
6. Set the Function Authorization to Authorized.
7. Click Submit.

Pre-installation
8. Log out and login again to see the new Navigation Pad item.
ALK PC*Miler
If an older version of PC*Miler was previously installed on the Windows system, remove it.
Uninstall PC*Miler.
1. Uninstall all components: Mapping, Server (or Connect), and PC*Miler. This is done using the
Uninstall feature found in the PC*Miler program group under the Windows Start menu.
Note: For some versions, uninstall using Add/Remove Programs in the Control Panel, or remove it
manually from the disk, Windows Start menu, and registry.
2. Delete the PC*Miler directory if it still remains (for example, C:\PMW261).
3. Delete the PC*Miler folder from Start (menu)\Programs folder for all users.
Note: You can now install the new version of PC*Miler. Call ALK product support to get the registration
key to match the serial number on the PC*Miler product CD/DVD.
Install PC*Miler on Windows systems

Note: Install PC*Miler with the same admin user that installs and runs Transportation Manager. If you
are using the TM Process Monitor service, it has to be started using the same user that is used to
install PC*Miler. See Configure the Process Monitor (on page 105).
1. Insert the CD/DVD, run the setup program and follow the prompts and instructions. Ensure to
install the Connect (Server) and Mapping components.
2. Change the system PATH environment variable and insert your PC*Miler App directory at the
beginning, for example, C:\PMW261\App;
Note: This is required to avoid a known DLL conflict between Oracle and PC*Miler. The symptom is
that the Distance Server does not stay up.
3. Ensure that the setting for the PC*Miler distance unit of measure is set the same as the
Transportation Manager Unit of Measure Type in the Global Settings (found in Web UI under
Environment > Global Settings > Defaults > Defaults). In PC*Miler, you can check this value
from the PC*Miler menu - select Default Options > Route and check the setting for Distance In.
Note: If using PC*Miler Worldwide, the North America region defaults to Miles, and Europe
defaults to Kilometers. One of these must be changed and the Global Setting in Transportation
Manager must match them both.
4. Ensure to reboot after installing PC*Miler.
Install PC*Miler on UNIX systems

1. Login to the system as an administrator. You must have root level access to perform the
installation.
2. Mount the PC*Miler product CD/DVD.
3. From the CD/DVD directory, run sh SETUP.SH.
4. Enter the directory where you want the product installed, for example, /opt
Note: PC*Miler creates and installs to a pcm* subdirectory (for example, pcm250) under the install
directory you select.
5. Enter your name and company when prompted (for the install record).
6. Enter y to confirm the information if correct.
7. Enter the serial number from the product CD/DVD.
8. Enter the registration code supplied by ALK support.
9. Enter y to continue.
Pre-installation
10. Enter y when prompted to install the basic file set, PCMServe, and PC*Miler Server (or Connect).
No other modules are required unless you have purchased the optional Canadian Postal Codes
data.
11. Follow prompts to complete the installation. It displays successfully installed when done.
Note: If you purchased the optional module of Street Level Data, follow the instruction of the
Street Level Data DVD to have it installed.
12. Edit the TM_HOME/tmsrvenv.sh file. Uncomment the line for PCMiler and set PCMiler_HOME to
the directory where you just installed it (for example, /opt/pcm250).
13. If you are upgrading PC*Miler on AIX without re-installing Transportation Manager Server, ensure
to delete the old symbolic link called libpcmsrv.so in the TM_HOME directory. A new link is
established when tmsrvenv.sh is run.
Rand McNally IntelliRoute

If this is your distance engine, perform the following steps to install it. If IntelliRoute and MileMaker
exist on the same system, Transportation Manager only recognizes the IntelliRoute software. Install
IntelliRoute for use with Transportation Manager using the methods mentioned below.
Note: Each installation requires separate install media.
Standalone/LAN
For Intelliroute StandAlone/LAN product, TM supports only the StandAlone installation, not the LAN
configuration.
Express server
This software is the required version if you are running your distance engine on a UNIX server. For this
configuration, you must install the Express Server on a Windows machine and the client software on
your UNIX server. Configure the Express Server and the application with one or more users, user
groups, and client location records. The Express Server can also be used with Windows clients, but not
for ad-hoc or unrelated distance calls to avoid impact on the performance of Transportation Manager.
The Windows client install is not included with the Express Server install media.
UNIX Client API libraries

Install the client API software on your UNIX machine if you are running the distance engine on UNIX.
You also need a Windows Express server running to service the client requests.
Windows Client
Install the client software on your Windows machine if you are running the distance engine on more
than one Windows server and do not wish to share a single Standalone/LAN installation to service
multiple Transportation Manager servers. You also need a Windows Express Server running to service
the client requests.
Install IntelliRoute Standalone/LAN

1. Run Setup.exe from the product installation media. The Welcome screen is displayed.
2. Click Next.
3. Click No when asked if you have an IntelliRoute startup diskette unless this was provided with
your product package.
4. Call Rand McNally for the 20 character unlock code and enter it in the required field, when
prompted.
5. Select your Destination Folder and click Next. The default is c:\Program Files\Rand McNally.
6. Click Next to acknowledge the disk space usage message.

Pre-installation
7. Click Next to accept the default program folder Rand McNally, or change as needed.
8. Click Next to begin the installation.
9. Click Finish to complete the installation.
10. Search the ApiBin\ directory where you installed IntelliRoute. If there is no DLL file called
STMEMAPI.DLL, copy it to here from the IntelliRoute Bin\ directory. It must be in the ApiBin
directory for the distance server interface to work.
The installation is now ready to use with Transportation Manager (once it has been properly configured
in that system). You can also use the client software included during the installation process.
Install IntelliRoute express server

2. Click Next.
prompted.
5. Select your Destination Folder and click Next. The default is c:\Program Files\Rand
McNally\IntelliRoute Server.
8. Click Next to begin the installation.
10. Start the IntelliRoute Server using the desktop icon or from Start (menu) > Programs > Rand
McNally > IntelliRoute with MileMaker Server.
11. Login using the default admin user MMAdmin1 and password mmadmin1.
12. Select Tools > Maintenance > Location from the menu and create a client Location ID record.
For example, your geographic location.
13. Create a user Group and an application User similarly.
Note: Use the User, User password, client Location ID, and Group to connect to the IntelliRoute
Server from the client installation.
14. To start the server, select Server Administration from the navigation pad and click Start
Server.
in that system).
Install IntelliRoute UNIX Client API libraries

1. Log into your UNIX system using the appropriate installation user.
Note: Create a user called iroute, or install as root. However, any user works.
2. Create the directory where the software resides. For example, /home/iroute on AIX or
/u/iroute on Solaris. Ensure that you have access to the directory for installation.
3. Mount the installation CD as instructed in the product documentation.
4. Navigate to the newly created iroute directory.
5. Extract the required archives using the tar command, for example,

Pre-installation
AIX
tar -xvf /cdrom/AIX/irg19.tar
Solaris (extracts to /u/iroute)
tar -xvf /cdrom/Solaris/irg19.tar
6. Edit the TM_HOME/tmsrvenv.sh file. Uncomment the line for IROUTE and set IROUTE_HOME
to the directory where you just installed it. For example, /home/iroute.
7. Unmount the installation CD as instructed in the product documentation.
The IntelliRoute UNIX Client API Libraries are now ready to use with Transportation Manager (once it
has been properly configured in that system). If you want to run the actual IntelliRoute UNIX Client
program, see the product documentation and call Rand McNally for any required support.
Install IntelliRoute Windows Client

2. Click Next.
prompted.
5. Enter the Client Location ID you set up during Express Server installation.
6. Enter the IP Address (or hostname) and Port Number for your Express Server (default port is
1998).
7. Select your Destination Folder and click Next. The default is c:\Program Files\Rand
McNally\IntelliRoute Client.
10. Click Next to begin the install.
in that system).
You must also be able to use the IntelliRoute Graphical Client to connect to your Express Server by
entering a valid User ID and password.
Note: The client LocationID, IP ServerAddress, and ServerPort for the Graphical Client are all
stored in the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Rand
McNally\DispatchAssistant\Client\AdminOptions. After installation, they can only be changed
using a registry editor such as regedit.
Rand McNally MileMaker

If this is the distance engine you require and it is not already installed or is at an older version, install
MileMaker from the CD onto a Windows server.
Install MileMaker on a Windows server

1. Log into the Windows system as an administrator.
2. Ensure that you uninstall any prior versions.
3. Insert the product install CD and run Setup.exe.

Pre-installation
4. Click Next to dismiss the Welcome screen.

prompted.
6. Click Next.
7. Click Next to accept the default Destination Folder C:\Program Files\Rand
McNally\MMaker32, or Browse to modify it.
8. Click Next to dismiss the disk usage summary.
9. Click Next to accept the default program folder.
10. Click Next to start installing files.
12. Create a network share for the MileMaker directory if required. Ensure that all applicable users
have full access rights.
13. By default, MileMaker does not use default zip codes. This setting must be changed to avoid failed
calls to the distance engine.
a. From the MileMaker application menu, select Features > Route Processing Options. Select
Use Default Zip Codes and deselect Reset to Do Not Use at Startup check box. Also, if you
are using Canadian addresses, select NL for the Newfoundland Abbreviation.
b. Click OK to accept the changes just made.
14. Reboot and ensure that the MileMaker bin\ directory was added to the system PATH, for example,
C:\Program Files\Rand McNally\MMaker32\bin.
i2 Distance
Transportation Manager uses the i2 Distance engine to interface with distance databases outside of
North America and Europe. It is also used by Transportation Planner for these alternate distance data
sets, or where the interface to the Transportation Manager distance engine is too slow (volumes are
very high or very fast solve times are required).
This feature is ordered through JDA Support. It is based on PC*Miler data and therefore requires a
valid PC*Miler license. The instructions for loading i2 Distance data are provided with the data
package, along with the required configuration settings.
Send reports and notifications through fax and email

How it works
The Transportation Manager Report Server can be configured to send reports (including load tenders)
and notifications using SMTP (Simple Mail Transfer Protocol), or the Microsoft MAPI messaging
standard. Irrespective of the protocol used, most fax server products are implemented using
connectors that detect email messages intended for fax delivery, and reroute them to the fax server.
When a fax or an email is to be transmitted, the report server calls the embedded Crystal routines to
export a report as an Adobe Portable Document Format (PDF) document. If the call is made using the
Send MAPI option, Crystal sends a MAPI message using the Exchange email client (or the Fax client
software), with the report as an attachment. The Mail From value is based on the email client
configuration. Microsoft Messaging takes over to send the message through the email server to the
final destination (an email or fax address).
If SMTP mode has been configured, the report server calls Crystal without the Send MAPI option.
Crystal returns the attachment to the report server, which uses the SMTP protocol to send a message
to the SMTP server, with the PDF document attached. Since there is no email client required, the Mail
From value is based on the Created By user from the Report Queue entry.

Pre-installation
Note: The SMTP server must support the EHLO (extended Hello) verb if you are using multibyte
characters or the message can be corrupted (SMTP client reverts to 7 bits).
Since Transportation Manager supports two standard protocols (SMTP and Microsoft Messaging) to
forward the messages, it theoretically supports all email and fax servers with the compatible
Connectors. In practice, this is not necessarily the case – not all products tested were able to connect
in this way, or were robust enough to support dozens or more faxes per day. Transportation Manager
has been successfully tested with Microsoft Exchange Server as the email server, in combination with
the fax servers shown in the software pre-requisites marked as Optional.
Fax server software

Install the preferred fax server software on the appropriate server. This should normally be separate
from your application servers to minimize resource contention. For those using FaxMaker for Exchange,
note that the fax server software must be installed directly on the Email server.
Each product has its own installation requirements, but some general principles apply to most
products:
• Use intelligent fax ports for more than a few dozen faxes per day.
• Install the fax or modem board before installing the fax server software.
• Select the correct fax board or modem while installing and configuring the fax server.
• It is required to Add and configure the users that have permission to send faxes for most of the
products.
• Set the applicable Windows service (if any) to autostart, so that fax services are available after a
reboot.
• Install the correct version of the Adobe Acrobat Reader so the fax server can process the PDF
attachments.
Fax client software

Install the client software for your fax product (if applicable) on the same Windows machine as the
Transportation Manager Report server. Some products only require the installation of an email client,
which can then be employed to send the request through the email, to the fax server.
Email client
If you are not using SMTP mode, you need email client software. Install the Outlook client onto the
same Windows machine as the Transportation Manager Report server. For MAPI, Outlook has been
successfully tested.
Note: Outlook Express does not work for send reports and notifications via fax and email. Also,
Outlook creates pop-up windows which can only be cleared by manually closing them or using software
that monitors and closes them automatically.
Place a shortcut to the email client program in the Startup folder so that it is available to send reports
and notifications whenever the system and its server processes are restarted.
Configure Outlook client

1. After installing the Outlook software, create the Exchange Server mail profile as described below.
2. Verify if Outlook can successfully send emails through the server.
3. Set Microsoft Outlook as the default mail program. Navigate to Start Menu > Control Panel >
Internet Options, click the Programs tab, and set the value for E-mail. Click OK to save your
changes.

Pre-installation
Note: For TM-Web UI users, this setting is over-ridden by their browser settings when sending
reports from the report server. This can be configured in their Internet Explorer settings by
selecting Tools > Internet Options and clicking the Programs tab (almost the same navigation
path as the previous step).
4. Ensure your RPT parameters are set correctly as described in Configure parameter set (on page
35).
Create the Exchange server mail profile

1. In the Control Panel, double-click the Mail or Mail and Fax icon. Then click Show Profiles.
2. Click Add to add a profile, or edit the existing profile. If you click Add, a wizard guides you
through the setup.
3. Select the services needed, for example, Microsoft Exchange Server, which then requests the
Exchange server and mailbox name. For LanFax or VSI-FAX services, specify the Fax Server name.
4. Remove any additional profiles. There must be only one set up to avoid confusion in the
application.
Configure parameter set

The reporting parameter set (default is RPT) must be set based on your choice of email and fax server.
Use parameter sets (on page 96) by accessing Server Configuration > TM Hosts > Parameter Sets in
the Transportation Manager web user interface. The relevant parameters are MapiConfig,
MapiTransport, and SmtpHost.
MapiConfig parameter
This parameter must be set to Logon:Y when using an Exchange server. It is not used for SMTP
environments.
MapiTransport parameter
MapiTransport consists of a pair of settings separated by a comma as illustrated in the examples
below. The first value in the pair represents the e-mail server and the second is for the fax server. This
parameter is not used for SMTP environments.
E-mail Server
Microsoft
Exchange
Tested fax
servers
Fax for Domino N/A
FaxMaker smtp,faxmaker
Other Fax
Servers
Alcom LanFax smtp,lanfax
VSI-FAX smtp,fax
Note: These settings are case-sensitive.
SmtpHost parameter
This parameter causes the Report Server to use SMTP mode, if present. It must be set to the name of
the SMTP server (for example, smtp.jda.com). You can specify a comma-separated list of SMTP
servers here if required. The program cycles through them until it is able to make a connection.

Pre-installation
Configure Transportation Manager

On Windows servers, the installation process creates shortcuts for all servers (processes) that start
manually.
On UNIX servers, template shell scripts are provided to set up the required paths and environment
variables, and to launch the DSC process. They can also launch servers that must be started manually.
For all platforms, there are pre-configured servers, and servers that require additional configuration
specific to your environment.
Install third-party and other JDA components on Windows
Install the required JDA and third-party components before installing TP. For the list of required
software, see JDA Transportation Planner Release Notes.
Note: This guide only offers guidelines for installing third-party products; specific instructions are
provided where these differ from the products’ default installation instructions. Refer to the third-party
product manufacturer’s documentation for complete installation and setup information.
See "Configure TP on Windows" (on page 113) for configuration instructions for TP and other software
required for implementing TP on the supported Windows version.
Install the application server

Install the supported version of WebLogic Server. For more information, see JDA Transportation
Planner Release Notes.
Install WebLogic server

When installing WebLogic Server, use the default settings. See the Oracle Corporation website
http://www.oracle.com for more information.
Install the web server

Install the supported version of Microsoft Internet Information Services. For more information, see JDA
Transportation Planner Release Notes.
Install database
TP requires the supported Oracle Client to be installed on each client machine.
For more information on the supported version of Oracle, see JDA Transportation Planner Release
Notes.
Install Oracle Client

If you use Oracle as your database (server and client), install the supported Oracle Client on each
client machine. When you install Oracle Client, use the default settings. For more information, see the
Oracle Corporation Website (http://www.oracle.com).
Notes.
Install JDK/JRE
TP requires supported version of Oracle Hotspot Java. For more information on the supported version
of Oracle Hotspot Java, see JDA Transportation Planner Release Notes.
See the Oracle Corporation website (http://www.oracle.com) for more information.

Pre-installation
Install Light Weight Directory Access Protocol (LDAP)

You can optionally use LDAP with the TP and Shipment Scheduler web interfaces; these web interfaces
also support alternate authentication modules. The MS Active Directory is provided with Windows
2012. When you install MS Active Directory, use the default settings. See the Microsoft website
(http://www.microsoft.com) for more information. For specific setup information, see Microsoft
support website (http://support.microsoft.com/kb/324753).
Note: During the installation, create a password of at least eight characters.

After installing MS Active Directory and the TP or Shipment Scheduler web interface, load the
authorization directory structure provided with TP. This file, tpui.ldif, is installed into the
\tpui\ldif folder under your TP installation folder (typically c:\JDA\tp\8.1) when you install the TP
user interface.
Install web browser

TP requires supported version of Microsoft Internet Explorer as the browser on your Windows client
machine. For more information on the supported version of Microsoft Internet Explorer, see JDA
See the Microsoft Corporation website (http://www.microsoft.com) for more information.
Install Cortona VRML Client

TP requires supported version of Cortona VRML Client as the VRML viewer to view containers in the TP
web interface or Shipment Scheduler web interface. Use the default settings to install Cortona VRML.
The default renderer setting is DirectX Renderer. For more information on the supported version of
Cortona VRML Client, see JDA Transportation Planner Release Notes.
See the Parallel Graphics Limited website

(http://www.parallelgraphics.com/products/cortona3d/download/) for more information.
Caution: You must adhere to the manufacturer’s terms of use if you plan to use the VRML viewer in
the TP web user interface or Shipment Scheduler user interface.
Set up the Map Viewer

TP supports Google map viewer for use with the TP web user interface. The map view is optional. No
additional software is required to use the map viewer. However, the license key needs to be obtained
from Google.
For more information on how to obtain license key, see the website
(https://developers.google.com/maps/licensing).
Use the settings in the tpConfig.xml file to set up the map viewer. The settings are:
• TPUI_MAPS_ENABLE: Specifies whether to show the map button in the TPUI.

• TPUI_MAPS_KEY: Specifies the key used to enable the map API.
Caution: The map viewer has its own specific terms of use and you must adhere to those terms. JDA
does not guarantee the terms of use for the viewers. The manufacturer retains the right to change
these terms.
For information about reconfiguring the map viewer after installation, see Transportation Planner User
Guide.
Install PC*Miler
TP requires supported PC*Miler/North America version or PC*Miler/Worldwide version. To use the
PC*Miler distance engine, you must install the PC*Miler Connect (which includes the PC*Miler location
database) after you install the TP Engine Program files. For more information on the supported version
of PC*Miler, see JDA Transportation Planner Release Notes.
Pre-installation
Note: You can have only one version of PC*Miler installed at any given time.
When you install PC*Miler, you should use the default settings. For more information, see the PC*Miler
website (http://www.alk.com).
Note: If you use a distance engine provided by JDA, you must also have a PC*Miler license, although
you do not have to install PC*Miler software.
Install RateWare Tariff Data and Rating software

TP supports the use of RateWare XL or RateWare Server in rating using CZAR tariff data. For more
information on the supported versions, see JDA Transportation Planner Release Notes.
Both products and the tariff data are available from SMC3 website (http://www.smc3.com).
Note: When possible, install the RateWare server on the same machine as the TP component that calls
it (Shipment Consolidation Engine).
Use RateWare server with TP

You obtain RateWare server directly from SMC3. Follow the manufacturer’s installation instructions.
Set up RateWare for use in TP

Ensure that the following settings are in your setup.xml file. The settings should be included in the
RatingEngineEntry for your Transportation Manager rating engine:
• <RateWareServerName>serverName</RateWareServerName>
where serverName is a string containing the name of the server that hosts the RateWare server.
• <RateWareServerPort>portNumber</RateWareServerPort>
where portNumber is a string containing the port number on the server that hosts the RateWare
server. The default port is 23700.
Install the common database/data repository

If you are using the Manufacturing ABPP as a TP data source, install JDA Manufacturing ABPP 8.1
before installing TP. You need this to use the Shipment Consolidation Engine, Shipment Scheduling
Engine, or TP web interface with an Oracle database if you are not using Transportation Manager and
not using JDA Fulfillment. For complete installation instructions, see the JDA Manufacturing ABPP
documentation.
If you are using JDA Fulfillment as a TP data source, install JDA Fulfillment 8.1 before you install TP.
You need this to use the Shipment Scheduling Engine if you are not using Transportation Manager and
not using JDA Manufacturing ABPP. For complete installation instructions, see the JDA Fullfilment
documentation.
Install the Integration Infrastructure

Install JDA Infrastructure Services 8.1 before installing TP. For complete installation instructions, see
Infrastructure Services Installation Guide.
Upgrade from an earlier version of TP on Windows

The default path for TP is C:\JDA\tp\8.1. If you have an older version of TP, install the new version
without uninstalling your older version since it will be located in a different path. If the older version is
TP 8.1, uninstall the existing version as described in "Uninstall TP programs on Windows" (on page
76).
Before upgrading, you are advised to back up your files, including:
• setup files
• strategy files
Pre-installation
• optimization parameter files

• rating files
Install third-party and other JDA components on Solaris

You must install the required third-party components before installing TP. For more information, see
This guide offers only guidelines for installing third-party products; specific instructions are provided
only where these differ from the products’ default installation instructions. You must refer to the third-
party product manufacturer’s documentation for complete installation and setup information.
Note: When installing third-party or JDA software, if you do not accept the default folder names in the
installation, ensure that the names of any folders that you create do not contain spaces.
Configuration instructions for TP and other software required for implementing TP are detailed in
"Configure TP on Solaris" (on page 115).
Install application server

When you install TP on Solaris, use the WebLogic Server as your application server.
For more information on supported version of WebLogic Server, see JDA Transportation Planner
Release Notes.

When you install WebLogic Server, use the default settings. For more information, see the Oracle
Corporation website (http://www.oracle.com).
For more information on supported software, see JDA Transportation Planner Release Notes.
Install web server

Install the supported version of Oracle iPlanet as the web server. For more information on supported
version of Oracle iPlanet, see JDA Transportation Planner Release Notes.
Install database
Install the supported Oracle Client on each client machine. For more information on supported
software, see JDA Transportation Planner Release Notes.
Use the default settings during Oracle Client installation. See the Oracle Corporation website
(http://www.oracle.com) for more information.

If you use Oracle as your database (server and client), install supported Oracle Client on each client
machine. For more information on supported software, see JDA Transportation Planner Release Notes.
Use the default settings during Oracle Client installation. See the Oracle Corporation website
(http://www.oracle.com) for more information.
Install JDK/JRE
TP requires supported version of Oracle Hotspot Java. For more information on the supported version
of Oracle Hotspot Java, see JDA Transportation Planner Release Notes.
See the Oracle Corporation website (http://www.oracle.com) for more information.
Install Lightweight Directory Access Protocol (LDAP)

When you install TP on Solaris, use Apache Directory Server as your LDAP.

Pre-installation
After installing the Apache Directory Server and the TP interface, load the authorization directory
structure provided with TP. When you install the TP interface, the tpui.ldif file is installed into the
\tpui\ldif folder under your TP installation folder (c:\JDA\tp\8.1).
Install web browser

Install the supported Microsoft Internet Explorer as the Web browser on your Windows client machine.
Use the default settings during Microsoft Internet Explorer installation. See the Microsoft Corporation
website (http://www.microsoft.com) for more information.
Install Virtual Reality Modeling Language (VRML) player1

Install the supported version of Cortona VRML Client on the Windows client machine where you will be
using the Web browser. For more information on supported software, see JDA Transportation Planner
Release Notes. Use the default settings during Cortona VRML Client installation. See the Parallel
Graphics Limited website (http://www.parallelgraphics.com/products/cortona/order) for more
information.
Install common database/data repository

If using JDA Manufacturing ABPP, you must install JDA Manufacturing ABPP 8.1 before installing
Transportation Planner 8.1. For complete installation instructions, see the JDA Manufacturing ABPP
documentation.
If using JDA Fulfillment, you must install JDA Fulfillment before installing Transportation Planner 8.1.
For complete installation instructions, see the JDA Fulfillment documentation.
Install integration infrastructure

You must install JDA Infrastructure Services 8.1 before installing Transportation Planner 8.1. For
complete installation instructions, see the JDA Infrastructure Services Installation Guide 8.1.
Upgrade from an earlier version of TP on Solaris

The default path for Transportation Planner 8.1 is /opt/jda/tp/8.1. If you have an older version of TP,
you can install the new version without uninstalling the older version since it will be located in a
different path. If the older version is TP 8.1, uninstall the existing version as described in "Uninstall TP
programs on Solaris" (on page 81).
• scenario files
• strategy files
• rating files
Install third-party and other JDA components on AIX

Install third-party components before you install TP. For the full list of required JDA and third-party
components, see JDA Transportation Planner Release Notes.
This guide offers only guidelines for installing third-party products; specific instructions are provided
only where these differ from the products’ default installation instructions. Refer to the third-party
product manufacturer’s documentation for complete installation and setup information.
Note: When installing third-party or JDA software, if you do not accept the default folder names in the
installation, ensure that the names of any folders that you create do not contain spaces.

Pre-installation
Configuration instructions for TP and other software required for implementing TP are detailed in
"Configure TP on AIX" (on page 117).
Install the application server

When you install TP on AIX, use the WebSphere application server or Weblogic application server as
your application server. For more information, see JDA Transportation Planner Release Notes.
Install WebSphere server

When you install WebSphere, use the default settings. For more information, see the IBM Corporation
Website (http://www.ibm.com).
For more information on the supported version of WebSphere, see JDA Transportation Planner Release
Notes.
Note: Ensure that you use the right version of Java configured for use with WebSphere.

When you install WebLogic, use the default settings. For more information, see the Oracle Corporation
Website (http://www.oracle.com).
For more information on the supported version of WebSphere, see JDA Transportation Planner Release
Notes.
Install the web server

When you install TP on AIX, use the IBM HTTP Server or Oracle HTTP server as your web server.
Install IBM HTTP server or Oracle HTTP server

When you install IBM HTTP Server or Oracle HTTP Server, use the default settings. For more
information, see the IBM Corporation Website (http://www.ibm.com) and the Oracle Corporation
Website (http://www.oracle.com).
For more information on the supported version of IBM HTTP Server and Oracle HTTP Server, see JDA
Install database
TP requires the supported Oracle Client to be installed on each client machine.
Notes.

If you use Oracle as your database (server and client), install the supported Oracle Client on each
client machine. When you install Oracle Client, use the default settings. For more information, see the
Oracle Corporation Website (http://www.oracle.com).
Notes.
Install JDK/JRE
When you install TP on AIX, use the supported version of Java for AIX. When you install the supported
Java version for AIX, use the default settings. For more information, see the Java Technology website
and the IBM Corporation website (http://www.ibm.com).
For more information on the supported version of Java, see JDA Transportation Planner Release Notes.

Pre-installation
Install Lightweight Directory Access Protocol (LDAP)

When you install TP on AIX, use the supported IBM Tivoli Directory Server as your LDAP. For more
information on supported software, see JDA Transportation Planner Release Notes.
Install IBM Tivoli Directory Server

Install the supported version of IBM Tivoli Directory Server. Use the default settings. For more
information on supported version of IBM Tivoli Directory Server, see JDA Transportation Planner
Release Notes.
For more information, see the IBM Corporation Website (http://www.oracle.com).
After installing IBM Tivoli Directory Server and the TP user interface, load the authorization directory
structure provided with TP. When you install the TP interface, the tpuiSecureWay.ldif file is installed
into the /tpui/ldif folder under your TP installation folder (/opt/jda/tp/8.1).
Install web browser

Install the supported Microsoft Internet Explorer as the Web browser on your Windows client machine.
Use the default settings during Microsoft Internet Explorer installation. See the Microsoft Corporation
website (http://www.microsoft.com) for more information.
Install Virtual Reality Modeling Language (VRML) player

Install the supported version of Cortona VRML Client on the Windows client machine where you will be
using the Web browser. For more information on supported software, see JDA Transportation Planner
Release Notes. Use the default settings during Cortona VRML Client installation. See the Parallel
Graphics Limited website (http://www.parallelgraphics.com/products/cortona/order) for more
information.
Install the common database/data repository

If using JDA Manufacturing ABPP, you must install JDA Manufacturing ABPP 8.1 before installing
Transportation Planner 8.1. For complete installation instructions, see the JDA Manufacturing ABPP
documentation.
If using JDA Fulfillment, you must install JDA Fulfillment before installing Transportation Planner 8.1.
For complete installation instructions, see the JDA Fulfillment documentation.
Install integration infrastructure

You must install JDA Infrastructure Services 8.1 before installing Transportation Planner 8.1. For
complete installation instructions, see the JDA Infrastructure Services Installation Guide 8.1.
Upgrade from an earlier version of TP on AIX

The default path for Transportation Planner 8.1 is /opt/jda/tp/8.1. If you have an older version of TP,
you can install the new version without uninstalling the older version since it will be located in a
different path. If the older version is TP 8.1, uninstall the existing version as described in "Uninstall TP
programs on AIX" (on page 87).
• scenario files
• strategy files
Pre-installation
• rating files

Installation
Chapter 4. Installation
Install Transportation Manager server
Note: For UNIX users, create a separate administrative user ID that is used to both install and run the
servers. The user ID used on UNIX for installation must be the user ID used to start and stop the
servers.
Prepare for the installation

1. Ensure that you have obtained a signed license file from JDA Support.
2. If using UNIX or a custom multi host environment, ensure that all hosts (Windows and UNIX) can
communicate properly as described in Topology (on page 2).
3. Ensure that the correct versions of the operating system and the database server and client have
been installed or upgraded in all applicable servers (including the Transportation Planner and Web
Application servers).
4. If using UNIX with Oracle, ensure that the ".so" files in your $ORACLE_HOME/lib64 directory have
read permissions for all (644 or 755). If not, you cannot connect to the database.
Note: In some cases, it is observed that these permissions are not set correctly when Oracle is
installed using updated standard procedures that worked for previous versions.
5. If using AIX, ensure that the AIX patch level and C Set Runtime meet the minimum requirements
referenced under the Supported server operating systems in the Software and Platforms. If not,
ensure to upgrade as required before continuing.
6. Ensure that your Input Locale (Regional Options) is set to U.S. English, regardless of the language
of your operating system. This requirement applies to both UNIX and Windows application servers.
7. Ensure that all the Transportation Manager clients, server processes, and the Process Monitor have
been terminated.
8. If not already done, install the compliant version of the Java JDK on your system, see JDA
Transportation Manager Release Notes. Ensure that the path to the bin\java program is defined
for your Windows or UNIX system PATH. This is required for the installer to run properly on either
platform. On Windows, ensure to reboot after installing so that the PATH variable is updated and
available to all programs (can wait for next step if also installing JDA Infrastructure Services).
9. If not already done, install the compliant version of JDA Infrastructure Services (CIS). This
software must be installed before installing Transportation Manager server components. Also,
ensure that CIS_HOME is part of your Windows or UNIX system PATH. This is required for the
installer to run, or it terminates with an error. On Windows, ensure to reboot after installing so that
the PATH variable is updated and available to all programs.
10. Verify that TCP/IP ports 3390 and 3391 are free and using the netstat command as in the
following examples. If the ports are free, the command must not return any result.
Windows
netstat -an | findstr 3390
UNIX
netstat -an | grep 3390
Note: If these ports are already in use, you can change the application ports after the installation.
See Configure the Distributed Service Coordinator (DSC) (on page 92).
11. Verify the domain name of your server. You must have a domain name defined (on both UNIX and
Windows systems) or the DSC cannot run. If you do not use DNS on your Windows network, any
string works, for example: mydomain.com.

Installation
UNIX
On UNIX, you can verify the domain name using the domainname command (and an administrator
can also set it using this command if it returns no value).
Windows
On Windows systems, select the System applet from the Control Panel, and click the Computer
Name tab. Click the Change button and then the More button. The Primary DNS Suffix field
must be set.
Note: On both UNIX and Windows, once the product software is installed you can see the
hostname and domain name that DSC requires, by running AdmTool from TM_HOME with no
parameters (on UNIX, load the tmsrvenv.sh environment first). The DSC works if this hostname
is the same as what you see when you ping your hostname without the domain, for example, ping
MyHostname.
12. If you have performed any customizations such as server allocation, save your hostconfig.rsp file
to another location.
13. Save custom files (for example, the i2Distance folders, or any OpenSSL .pem and .der files) to
another location.
14. Uninstall old versions of Transportation Manager. On older UNIX versions, there is no Uninstaller,
so you must manually delete the old directory.
For example, rm -rf /opt/jda/tmgr/6.1/*.
15. On Windows systems, uninstall old versions of the Crystal Runtime from the Add or Remove
Programs applet in the Control Panel.
16. If you are installing on a Windows system that runs a TM report server, install the required version
of .NET Framework if it does not exist. If running on a 64-bit system, you must install the 64-bit
version of this software. See Software ordering information (on page 163) for download
information.
Note: Any required .NET service packs are automatically downloaded and installed if you are
configured for automatic updates.
17. See JDA Transportation Manager Release Notes to ensure that you are aware of any server and
third party software combinations that can run only on Windows.
Note: On Windows, there are software incompatibilities between the DSC process and
performance monitors such as Oracle and pcANYWHERE. The DSC starts up, but clients cannot
connect to it. The Oracle performance monitor must be uninstalled to solve such a conflict, but the
pcANYWHERE conflict can be fixed by deleting the following key from the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\pcAnywhere\Performance.
Install Transportation Manager server

1. Run TMSetup from the TM directory in the product. On Windows systems, you can double click the
TMSetup icon. On UNIX systems, login as the chosen administrative user ID and run sh
TMSetup.bin from within an X windows client such as xterm.
Note: Silent installs do not have to be run from an X windows client.
2. Click Next to dismiss the Introduction screen.The License Agreement page is displayed.
3. Read the Software License Agreement Terms and select I accept if you agree and wish to
continue.
4. Click Next. The Choose JDA License File is displayed.
5. Enter the full path to the Signed License File issued by JDA Support.
6. Click Next. The Choose CIS Home Folder page is displayed.

Installation
7. Enter the location of the cis-sdk folder of the installed CIS for windows (For example,
C:\jda\CIS\8.1\cis-sdk).
8. Click Next. The Choose Install Folder page is displayed.
9. Select a path to install Transportation Manager applications, for example C:\jda\tmgr\8.1. Do
not include spaces in the pathname because the ORB middleware interprets this as a list of
parameters and can fail.
10. Click Next.The UNIX Application Server page is displayed.
11. Select No if there is no UNIX application server as part of this install.
12. Click Next. The System Information - Windows page is displayed.
13. Enter the Hostname for this system.
Note: The default of localhost is appropriate if you are not using UNIX, or communicating with
other DSCs. If you are not using localhost, include the domain name here (for example,
myserver.jda.com), or just specify the hostname and let the DSC resolve the domain at run time.
14. Windows Only - If you responded Yes to the UNIX question, enter the UNIX hostname and path
where Transportation Manager is installed (or can be installed). Click Next.
15. UNIX Only - Enter the Windows Hostname and Application Folder where Transportation
Manager is installed (or can be installed).
16. Click Next. The DataBase Information page is displayed.
17. Enter the database User, Password, Alias, and the path to the database Client Folder.
Note: Do not enter values with lengths greater than 29 characters, or values containing @ signs.
The configuration can fail at a later stage.
18. Click Next.The DataBase Information (JDBC connection) page is displayed.
19. Enter the Database Hostname, Database Port Number, and Database Name for your JDBC
connection. This is used by the inbound TM Adapter for connecting to the database.
Note: Do not use the alias here for the Database Name. This must be the Oracle SID.
20. Click Next.
21. Review the summary information and click Install.
22. The program now installs the required files. On Windows servers it also formats the
hostconfig.rsp, dsc.db, and dsc.ini files to connect to your database.
23. Click Done when prompted to complete the installation.
24. If you encounter an error , check the install log XML file in the target install folder.
25. If you saved a customized rsp file from a previous release, then you must now apply the same
customizations to the new hostconfig.rsp file created during installation.
26. Restore any other customized files such as the i2Distance folders or any OpenSSL .pem and .der
files.
27. If you are installing on a Windows system that runs a TM report server, install the Crystal Reports
Runtime in the TM_HOME directory. This takes about a minute on a fast system, and the
command window disappears when done. This software must be uninstalled separately if no longer
required.
28. If you are installing on a Windows system, then reboot the system. This is to ensure that the
applicable system variables are altered properly.
29. The Monitoring Server initializes the UI. Therefore, if you are using Proactive Monitoring you must
start the Monitoring Server after installation, and before you access Monitoring in the browser UI.
This server initializes tables used by the UI. See Configure the monitor server (on page 104) for
details on how to grant access to the UI after the tables have been initialized.
Installation
30. UNIX Only - On UNIX servers, run the DSC configuration manually as described in Configure the
Distributed Service Coordinator (DSC) (on page 92).
Note: For environments that include a UNIX application server, any additional environments (such
as QA or Development) on the same network must be configured with a unique TM domain name
and DSC Port number or they can interfere with each other across the network. See Configure the
Distributed Service Coordinator (DSC) (on page 92) for detailed instructions.
Install the TM-Web interface for WebLogic

This chapter describes how to install and configure the Transportation Manager Web interface using the
WebLogic application server. The Web interface allows you to access Transportation Manager data and
functions using only a Web browser.
Prepare to Install the Web interface

There is no language selection during the TM Web installation or configuration. Instead, optional
language packs are available at the JDAUser website (http://www.jdauser.com) and are installed
as an addition to the Web Interface.
1. Ensure to order and receive the correct version of WebLogic software and the multiuser license (for
example: isv.jar). See JDA Transportation Manager Release Notes.
2. Shut down all Transportation Manager processes and servers on this machine.
3. Shutdown any WebLogic service (TMWebService) from the Services applet in the Control Panel >
Administrative Tools. This service might be running if WebLogic was previously installed on this
machine and was configured to run as a service.
4. Uninstall the previous version of the Web Interface. For versions prior to 6.1.6, there is no
uninstaller, so delete the entire tmgr-domain folder from the WebLogic product directory.
5. Uninstall the previous version of JDK or Java Runtime Environment (JRE) if it is not required for
other applications using the Add/Remove Programs applet in the Control Panel.
6. Uninstall the previous version of WebLogic using the uninstaller utility of the program, or the
Add/Remove Programs applet in the Control Panel.
7. Delete the WebLogic directory to remove the remaining files, for example, C:\weblogic or
C:\bea.
8. Uninstall the older version of Oracle.
9. Install and configure the correct version of Oracle client if it is not already installed.
10. Ensure that you have installed Transportation Manager server on your network and have a working
DSC.
Note: If WebLogic is running on a separate server from the DSC, do not install anything other
than the database client, WebLogic, and TM-Web. The Web Interface does not directly access
components from the TM Server install.
11. Verify if TCP/IP ports 7001 and 7002 are free using the netstat command as in the following
examples. If the ports are free, the command must not return any result. If the ports are in use,
select different ports during the installation.
Windows
netstat -an | findstr 7001
UNIX
netstat -an | grep 7001

Installation
Install the Web Interface

Install the WebLogic Server
Note: Install the current version of WebLogic server, if not installed. Ensure to uninstall any previous
versions first.
1. Run the Setup program from the WebLogic product. The Welcome page is displayed.
2. Click Next.
3. To accept the Software License Agreement terms, select Yes and click Next when prompted.
4. Select a BEA Home directory when prompted, for example, /opt/bea on UNIX or C:\bea on
Windows. Click Next.
5. Select the Custom install type. Click Next.
6. On the Choose Components page, deselect the check box next to Server and then select the check
box again to select the minimum required components. Also, select Server Add-ons if you are
using a web server (Apache or Sun Java System) to proxy web application requests using the
WebLogic plug-ins supplied.
Note: The other options are not required, but can be selected if desired.
7. Click Next.
8. On the Choose Product Directory page, click Next to accept the default directory (for example,
/opt/bea/wlserver_12.1.2 on UNIX, or C:\bea\wlserver_12.1.2 on Windows), or enter your
preferred directory.
9. The Node Manager Service is not required at this time. Select No and click Next.
10. Click Next to create shortcuts for All Users. The program installs files to the selected location.
11. Once done, deselect the Run Quickstart check box displayed at the end of the install and click
Done to complete the WebLogic installation.
Start the Web interface installation

1. Run TMWebSetup (found under TMWeb in the product) by running the command sh
TMWebSetup.bin from an xterm window (or just a command window if running a silent
installation). On Windows systems, double-click the icon or run the TMWebSetup.exe program
from the Run command on the Start menu. The setup program displays the Introduction page.
2. Click Next. The License Agreement page is displayed.
3. If you accept the Software License Agreement terms, select I accept.
4. Click Next. The Choose JDA License File page is displayed.
5. Enter the full path to the License File issued by JDA Support.
6. Click Next.The Transportation Manager Web Components page is displayed.
7. Select the TM components that should be installed:
• Install TM Web: Installs the TM web component.
• Install Smart Bench: Installs TM Smartbench (TM RIA).
Note: Select both components to install TM Web and Smartbench.
8. Click Next. The Choose Install Folder page is displayed.
9. Select the path where you want to install TM web or Smartbench. The installer creates
subdirectories called tmgr_domain and tmria_domain at this path and the files are installed
here.
10. Click Next. The Weblogic Home Folder page is displayed.

Installation
11. Enter the path to the WebLogic BEA home directory, for example, C:\bea.
12. Click Next. The Choose a Folder dialog box is displayed
13. Enter the path to the 64-bit JDK home directory, for example, C:\jdk1.7_x .
14. Click Next. The WebLogic Product Folder page is displayed.
15. Enter the path to the WebLogic Product server directory, for example,
C:\bea\wlserver_12.1.2\server.
16. Click Next. The Oracle Folder page is displayed.
17. Enter the path for the Oracle root folder where the database client software is installed.
18. Click Next. The Database Connection page is displayed.
19. Enter the following database connection information:
• User: The schema username.
• Password: The schema password.
• DataBase Name: The actual Oracle SID (not the alias) for the database server.
• Database Host and Port Number: In the form MyHostName:nnnn where nnnn is the database
port number. This information can be found by running tnsping dbalias from the command
line, where dbalias is the alias used by TM Servers to connect to Oracle.
20. Click Next. The JDBC Connections page is displayed.
21. Modify the JDBC connection settings, if required. This setting represents the number of
simultaneous connections open to the database server.
Note: Leave the minimum at 10 and set the maximum to around 50% to 75% of your total
number of possible users. If the number is set too low, you have to wait for available connections.
If set too high, you require more database connection licenses and RAM.
22. Click Next after you set these values. The Memory Allocation page is displayed.
23. Click Next to accept the default RAM settings. The WebLogic Ports and Configuration page is
displayed.
Note:For production installations, set to a minimum of 700, and a maximum of 2048 for the
system to function. For demo systems where RAM is lower, you can use marginally lower settings
but performance can be slower.
24. Change the Listening Port and SSL Port settings, if required (defaults are 7001 and 7002).
25. Select the check box for Clustered Environment if you are using a WebLogic cluster.
26. Select the check box for Session Replication if you are using a WebLogic cluster and need to
maintain user sessions during server failover.
This setting increases the overall system load (specifically in a load-balancing configuration). Use
this setting only if it is not required for you to log into the Transportation Manager web application
immediately after a system failure in the cluster.
27. Click Next to accept the WebLogic Ports and Configuration settings. The Single Sign On and
Authentication page is displayed.
28. Enter a value for the SSO time out minutes and CIS SSO Domain fields. You can select the SSO
Enable, Login Screen Visible, and Authentication Enable check boxes.
29. Click Next. The Smart Bench Configuration Information page is displayed.
30. Enter the following:
• TM web hostname including the domain of the system.
• Weblogic ports for Smartbench
Installation
• TM web external URL

• Google Map key, if Google Map is enabled.
Note: Transportation Smartbench supports the Google map viewer. The map view is optional. No
additional software is required to use the map viewer. However, the license key needs to be
obtained from Google.
For more information on how to obtain the license key, see the website
(https://developers.google.com/maps/licensing).
Caution: The map viewer has its own specific terms of use and you must adhere to those terms.
JDA does not guarantee the terms of use for the viewers. The manufacturer retains the right to
change these terms.
31. Click Next. The System Information page is displayed.
32. At the DSC Host field, enter the name of one or more computers that run the DSC program. If the
DSC port number is not 3390, include it after the computer name (separated by a colon). If there
are two or more computer names, separate them with commas, for example:
DSCHost1:4010,DSCHost2,DSCHost3:4020
In the example above, TM-Web is connected to DSCHost1 on port 4010 if available. If not, it is
connected to DSCHost2 on the default port 3390. If the first two machines are not available, it is
connected to DSCHost3 on port 4020.
Note: In production deployments, use the same DSC port on all servers in the same workgroup to
reduce complexity or allow the software to default to port 3390 by specifying only hostnames in
this field.
33. Click Next.
Complete the Web interface installation

1. Review the summary information and click Install if it is all correct. The program creates
tmgr_domain and tmria_domain folders at the selected location and installs the TM Web and TM
Smart Bench files and classes to the folders .
Note: It takes the program a few minutes to configure your system as it updates the J2EE archive
files and merges customizations. The merge process takes several minutes the first time it is run
for each schema, but is faster on any subsequent reconfigurations.
2. Click Done to complete the installation.
3. Verify the install log XML file in the target install folder, if the installer reports errors.
4. Install the WebLogic license multiuser license if applicable (for example: an isv.jar file).
5. To install on UNIX, and use a UTF8 database, edit the MyComputer.sh file in the template
directory (tmgr_domain/TM_Web_Config/domain_files/MyComputer.sh), and uncomment
the line that sets NLS_LANG. Reset this variable to american_america.al32utf8 if using a UTF8
database. If not, the following error is displayed when you try to login to the Web Interface:
Please retry the operation again or at a later time. If the issue persists, please
call technical support hotline at 1-111-111-1111 or send us an email at
support@company.com
6. To install on UNIX, manually run the config_parm.sh configuration utility from the
tmgr_domain/TM_Web_Config directory. See Change the WebLogic configuration using
TM_Web_Config (on page 52). For example:
config_parm.sh jdatm_crp jdatm_crp jdatmdb
Note: The same operation is required for TM Smartbench (tmria_domain) under
tmria_domain/TM_Web_Config

Installation
7. On Windows and UNIX, verify if the tmgr_domain\logs\merge***Customization.log files

have no errors (where *** can be Chart, List, NavPad, ScreenElement, Search, or Workflow).
These files are empty if the operation was successful.
Errors can occur in the following scenarios:
• If your DB URL (Database Host and Port Number) is set incorrectly during installation.
• If the NLS_LANG is set incorrectly in a UTF8 environment.
• If the database field is not the Oracle SID.
• If the program is unable to MERGE your customizations. In this scenario RESET the Web UI to
the default mode by changing the setting for SQL_MERGE_MODE to RESET in the config_env file,
and re-running config_parm. Ensure to change it to MERGE when done so that you retain your
customizations if you need to re-run config_parm later.
Note: Use of the RESET command mode is NOT recommended unless this is your only option. This
mode resets ALL web UI customizations to the JDA default settings. All system and user/user
group level overrides for page customization (column presentation on lists), saved searches,
module and module content configuration (links on navigation pad) and page element
configuration (buttons and sub-menu operations on lists) are removed.
8. If you want to run WebLogic as a Windows service, open an Explorer window in the tmgr_domain
folder (for example: C:\jda\tmgr\8.1\tmgr_domain) and double-click the
installWinService.cmd program. A service is created called TMWebService, which is set to a
Startup Type of Automatic by default.
Note: If the service has previously been installed on this system, run uninstallWinService.cmd
to remove it before trying to install. Also, on Windows systems you must leave the
TMWebService configured to use the local system account and not a real user account.
Start the WebLogic server

1. Ensure that the DSC is running on the specified system.
2. On Windows systems, if you did not select WebLogic to run as a service during the TM Web
installation, it creates a shortcut to the starttmgr_domain.cmd file found in your tmgr_domain
directory.
3. For TM Stmartbench, create a shortcut to the starttmria_domain.cmd file found in your
tmria_domain directory.
4. On Windows systems, start the server using the shortcut or the Windows services applet,
depending on your configuration. The service name is TMWebService. It takes several minutes to
start up as it compiles and prepares the Java code.
Use the Task Manager program to specify that it is complete. While loading, the java.exe process
(or wlsvcx64.exe if running as a service), it uses a lot of CPU time and memory. The memory
usage stabilizes, after the server starts.
5. On Windows systems, if you did not select WebLogic to run as a service during the TM Web
installation,it creates a shortcut to the starttmria_domain.cmd file found in your tmria_domain
directory.
6. On UNIX systems, if Transportation Manager Server is installed on the same machine, use the
start_servers.sh script to start WebLogic. Edit the TM_HOME/tmsrvenv.sh file, and supply the
correct value for BEA_HOME. Also edit WebLogic_HOME and TMWEB_HOME if you did not
install to default directories.
Edit the start_servers.sh program in the same directory and uncomment the WebLogic section
so the server comes up with the rest of Transportation Manager.
7. Navigate to the tmgr_domain directory from a command window, and run
starttmgr_domain.sh to start the server on UNIX manually. The Web Interface initializes its own
Oracle environment settings.
Installation
8. Navigate to the tmria_domain directory from a command window, and run

starttmris_domain.sh to start the TM Smartbench server on UNIX.
Change the WebLogic configuration and ports

During installation, the parameters that you enter are stored in config_env.cmd file under the
tmgr_domain\TM_Web_Config\Config\Current folder. These parameters are then used to
configure your installation.
To change the configuration later, you can edit this file and run the program that applies the changes
to the application archive. It is not possible to edit the configuration files directly since they are stored
in a J2EE ".ear" file.
Some common examples of parameters that require reconfiguration are:
• WebLogic ports (TCP/IP)

• DSC hostname (or DSC hostname:port - see Start the Web Interface installation (on page 58) for
possible values.)
• Schema connection information
The default installation sets the WebLogic listener ports to 7001 and 7002. Change these port
numbers if you have a conflict with an application already in use. In the recommended deployment,
these ports are only used to forward requests by proxy from the Web server to the Web application
server. Therefore, they are not open to users outside the private network if the outside firewall is only
open for http and/or https requests.
The other parameters stored in the config_env.cmd file can be changed to meet specific
requirements.
Change the WebLogic configuration using TM_Web_Config

1. Stop the TMWebService service, the command window, or the WebLogic Java process, depending
on the selected configuration.
2. Open a command window in the tmgr_domain\TM_Web_Config\Config\Current folder.
3. Edit the config_env.cmd file as required. See the Transportation Manager System Administration
Guide for more information.
4. If you are using a different version of Oracle server than before, change the value for
DB_SERVER_URL.
5. Run the config_parm program (config_parm.sh on UNIX) present in
tmgr_domain\TM_Web_Config to configure WebLogic. The command format is:
config_parm <db username> <db password> <Oracle SID>
For example, config_parm jdatm_crp jdatm_crp jdatmdb
Note: It takes the program a few minutes to configure your system as it updates the J2EE archive
files.
6. Follow the preceding steps to make similar changes for the TM Smartbench under
tmria_domain\TM_Web_Config, editing the config_env3.cmd file as necessary.
7. Verify the tmgr_domain\logs\merge***Customization.log files for errors.
8. Run installWinService to refresh the configuration, if you are using TMWebService.
9. If you are using an iPlanet Web server to proxy requests, and you changed the WebLogic ports,
edit the WebLogicPort=7001 line manually in the obj.conf file on the Web server and restart it.
Perform this after the Web server is configured as described in the next section.
10. Verify the URL for any browser clients if requests are sent directly to the WebLogic server and not
through a Web server.
Installation
11. Change the date format on the web client to dd/mm/yyyy and add new language support as
mentioned in the next section.
Reconfiguration and JavaScript recompiles

Wherever possible, configuration changes must be made using steps described in the previous section.
However, certain reconfigurations and data changes require you to edit files contained in the tm.ear
archive, or recompile the dependent JavaScript files to recognize the change. These include:
• Changes in the date format or the presentation of days and hours (see Change the date format
and presentation of days/hours (on page 53)).
• Changes in the default error message (see Change default error message (on page 53)).
• Addition of one or more preferred (high priority) countries that are displayed first in pick lists (see
Configure preferred countries (on page 54)).
• Customization of the Web Interface banner at the top of each page for announcements. The
section is 40x400 pixels and the content is referenced by adding a line to the
Error_<locale>.properties file (see Customize the web interface banner for announcements (on
page 54)).
Note: This feature is not currently supported for WebSphere environments.
• Modifications or additions to state/province code data (not usually required since states are
supplied for most countries as of version 6.2.1). These changes are automatically reflected up in
the Web Interface when you run refreshJSfiles and restart the Web Application server. No
additional steps are necessary for this particular task.
• Addition of optional support for additional languages. These language packs are available
independently and have their own installation instructions.
The refreshJSFiles program performs the necessary recompiling. It also allows you to perform the
changes listed previously by making modifications of required files present at the following path:
<tmgr_domain>\ TM_Web_Config\Config\Current. After the changes are made, the program
updates the archive and compiles the JavaScript files.
Most of these changes are configured independently for each locale (combination of language +
country). The standard release includes a locale for Canadian English and U.S English, and both are
configured with a date format of mm/dd/yyyy for consistency with previous releases.
The following sections describe how to perform the various reconfigurations. To ensure that the
changes are reflected, run the refreshJSFiles process (on page 54).
Note: Do not modify other files unless instructed. This includes the date formatting fields in application
properties, which are only relevant to internal programming routines and do not control the user
interface. Many of the files extracted to this folder are managed separately by tm_web_config.
Change the date format and presentation of days/hours

The date format, or the display of days and hours for a user locale can be edited from the User Locale
Properties page, which can be accessed from the Transportation Manager Web UI. Navigate to the User
Locales page by selecting Environment > UI Customization > User Locales. On the User Locales
page, verify if the existing defaults for localization are appropriate for your environment. If not, select
the appropriate locale and click the Properties button.
For more information, see the List of User Locales topic in the Transportation Manager User Guide or
the OnLine Expert in Transportation Manager.
Change default error message

Edit the applicable Error_<locale>.properties files (for example, Error_en.properties) present in
the following location: <tmgr_domain>\ TM_Web_Config\Config\Current\tm_misc\config.
Installation
The default error message and tag are as follows:
ERROR_PAGE=Please retry the operation again or at a later time. If the issue persists,
please call technical support hotline at 1-111-111-1111 or send us an email at
<a href="mailto:support@company.com">support@company.com</a>.
Configure preferred countries

To add Preferred (High Priority) Countries, edit the Application.properties file present in the
following location: <tmgr_domain>\ TM_Web_Config\Config\Current\tm_misc\config. Search
for the section called #High Priority Countries and add a new entry for each intended priority
country. Use the 2-character ISO country code. Ensure to sequence them in your preferred order, and
make the number on each line unique, for example:
#High Priority Countries
CountrySelection.1=ES
CountrySelection.2=US
CountrySelection.3=CA
Customize the Web interface banner for announcements

1. Edit the applicable Error_<locale>.properties file (for example, Error_en.properties) present
in the following location: <tmgr_domain>\
TM_Web_Config\Config\Current\tm_misc\config
2. Add a new line to this file, as in the following example (should all be on one line):
TOP_SECTION_CUSTOMIZED_HEADER=<table bgcolor="white" border="2" width="400"><tr
height="100%"><td><img id="notice1" src="/tm/images/notice3.jpg" alt="First
Announcement" border=0></td></tr></table>
If you have multiple graphics, then the line is structured as in the following example (which has
three):
TOP_SECTION_CUSTOMIZED_HEADER=<table bgcolor="white" border="2" width="400"><tr
height="100%"><td><img id="notice1" src="/tm/images/notice3.jpg" alt="First
Announcement" border=0></td>
<td><img id="notice2" src="/tm/images/notice2.jpg" alt="Second Announcement "
border=0></td><td><img id="notice3" src="/tm/images/notice3.jpg" alt="Third
Announcement " border=0></td></tr></table>
3. Copy your announcement files (for example: notice1.jpg), to the
<tmgr_domain>\TM_Web_Config\Config\Current\images directory.
Begin the refreshJSFiles process

1. Stop the TMWebService service, or the command window, or the WebLogic Java process,
depending on the selected configuration.
2. Run the refreshJSFiles program (or refreshJSFiles.sh on UNIX) from the tmgr_domain
directory. No parameters are required.
3. Verify the tmgr_domain\logs\refreshJSFiles.log file for errors.
Configure web servers for proxy requests to TM

Implement the appropriate level of security using firewalls and Secure Socket Layer (SSL) if the
application is to be deployed outside the immediate LAN. This includes the Internet or a WAN where
other networks are not given complete access to the local network. You need to design and run the
Web application deployment, in order to address your specific security requirements.

Installation
The Web Interface is run using WebLogic and a browser (plus a DSC). However, the standard
configuration is to have an independent Web server in a DMZ (outside the internal firewall) that
redirects the appropriate Web traffic to the WebLogic Server within the private network. The following
are the instructions pertaining to Apache. Other Web servers support this functionality, but have not
been specifically tested.
Install Apache web server on Windows server.

1. Go to the Apache website (http://www.apachelounge.com/download/win64/).
2. Click VC10 Win64.
3. Click VC10 SP1 vcredist_x64.exe and install Visual C++ 2010 SP1.
4. Click httpd-2.2.x-win64.zip and wait for the download to complete.
5. Unzip the file to c:/Apache2 (that is, the ServerRoot in the config).
6. Comment the sentence, LoadModule authnz_ldap_module modules/mod_authnz_ldap.so, by
adding # before the sentence in the http.conf file in the C:/Apache2/conf directory.
7. To install the Apache Service on windows, navigate to C:\Apache2\bin and run the following
command:
httpd.exe –f C:\Apache2\conf\httpd.conf -k install
8. To start the web server., navigate to C:\Apache2\bin and run the following command:
httpd.exe –f C:\Apache2\conf\httpd.conf -k start
9. Launch the following URL that shows a html page and displays It Works.
http://localhost:80
10. To stop the Web Server, navigate to C:\Apache2\bin and run the following command.
httpd.exe –f C:\Apache2\conf\httpd.conf -k stop
For more information on downloading Oracle WebLogic web server Plugins, See Oracle website
(http://www.oracle.com/technetwork/middleware/ias/downloads/wls-plugins-
096117.html).
Configure Apache web server (Windows 64 bit) for platform cluster

1. Create a folder, C:\Plugins\Apache, on the server where Apache Web Server is installed.
2. Download Oracle WebLogic Web Server Plugins Version 12.1.2 from Oracle website
096117.html).
3. Extract the contents of wls1212-plugins.zip to C:\Plugins\Apache.
4. Navigate to C:\Apache2\conf and add the following content to the httpd.conf file:
LoadModule weblogic_module C:/Plugins/Apache/lib/mod_wl.so
<Location /tm >
SetHandler weblogic-handler
WebLogicHost <SERVER_NAME>
WebLogicPort <SERVER_PORT>
WLCookieName JSESSIONID
ConnectTimeoutSecs 5
</Location>

Installation
Notes:
• User can copy the above content from the httpd.conf file that is in the Apache folder at
tmgr_domain\Connectors.
• If using a weblogic cluster instead of WebLogicHost and WebLogicPort, use the following format
in the httpd.conf file.
WebLogicCluster <ManagedNode1>:<Port>,<ManagedNode2>:<Port>
5. Navigate to C:\Apache2\bin and run the following command to start the Web Serve:.
httpd.exe –f C:\Apache2\conf\httpd.conf -k start
6. Access http://localhost:80/tm.
For more information on configuring WLS Web Server Proxy Plug-In for Apache HTTP Server, see
Oracle documentation
(http://docs.oracle.com/middleware/1212/webtier/PLGWL/apache.htm).
Other Web servers

For more information on the configuration of proxy plug-ins for various Web servers, see the Oracle
WebLogic website
(http://docs.oracle.com/cd/E17904_01/web.1111/e14395/isapi.htm#autoId0).
Access the TM-Web interface on WebLogic

The Web Interface is accessed using a compatible browser version (of Internet Explorer). It is accessed
through a standard Web server such as Microsoft Internet Information Server, or iPlanet Web Server.
The web server configuration instructions and templates allow the Web server to proxy any URL
requests for tm/ documents to the WebLogic server.
It is also possible to access the WebLogic server directly, if intended, assuming that the WebLogic
socket (default port = 7001) is not filtered by a firewall.
Access the web interface through a Web server

1. Launch the browser program.
2. Enter the appropriate Web URL as http://<server name>/tm. For example,
http://mywebserver/tm.
Note:The <server name> can be preceded by "www." if the application is being deployed over the
Internet.
Access the web interface directly through the WebLogic server

2. Enter the appropriate Web address as http://<server name>:7001/tm. For example,
http://mywebserver:7001/tm. The number following the server name and preceded by the colon
is the default port number for the WebLogic server.
Install the TM-Web interface for WebSphere

This chapter describes how to install and configure the Transportation Manager Web interface for
installations using the WebSphere application server in a single-server or network deployment. This
interface allows you to access Transportation Manager data and functions using only a Web browser.
Prepare to install the Web interface

1. Install the correct version of the database client software.

Installation
2. Ensure to order and receive the correct version of WebSphere from IBM. For more information on
supported software, see JDA Transportation Manager Release Notes.
3. Determine whether you require a Network deployment (central administration of multiple
WebSphere Application servers), or a Single-Server deployment.
4. Install the WebSphere application server as instructed in the product documentation.
5. If using HTTP server, install the required version on your AIX Web server machine. For more
information on supported software, see JDA Transportation Manager Release Notes.
6. In the following steps, WAS_PROFILE_HOME represents the location of your WebSphere application
server profile, for example: /usr/IBM/WebSphere/AppServer/profiles/AppServer01. Set this as
an environment variable for reference.
7. Ensure that you have installed Transportation Manager server on your network and have a working
DSC.
Note: If WebSphere is running on a separate server from the DSC, install only the database client,
WebSphere, and TM-Web. The Web Interface does not directly access components from the TM
Server install.
8. You need root access to install the WebSphere Application Server on a UNIX system.
Determine the following port numbers for your WebSphere application server.
Default value for

Description single server My value
deployments
Administrative console port 9060
Bootstrap address port 2809

Application port --
Note: Ensure that the default java version is Java7 ( instead of Java6) for the WebSphere profile
where TM web is deployed.
Determine the Administrative console port

Note: The following steps are for Single-Server deployments only. For Network deployments, get the
Administrative console port from the administrator.
1. Ensure that the WebSphere application server is running (see the following instructions for how to
start it).
2. Log into the admin console from a browser (default URL is in the form
http://MyHostname:9060/admin). If you can access the console, and there are no other application
server running on this machine, you have obtained the correct admin console port.
3. If the console is not obtained, or you need to confirm you are connecting to the correct application
server, search in
WAS_PROFILE_HOME/config/cells/cellName/nodes/nodeName/servers/serverName/server.xml (for
example: WAS_PROFILE_HOME/config/cells/cell01/nodes/node01/serverindex.xml). Search
for adminhost - the admin console is on one of these ports.
Determine the bootstrap address port

1. For single-server deployments, the bootstrap address port can be confirmed from the admin
console by navigating to Servers > Server Types > WebSphere application servers >
server1 > Ports (found under Communications section). The Bootstrap Address port must be
at the top of the list.

Installation
2. For network deployments, log into the admin console and navigate to System Administration >
Node Agents, and click the applicable Node Agent. Then, click Ports and search for Bootstrap
Address.
Determine the application port

The HTTP port on which the application is run is determined the same way as you looked up the
Bootstrap address port. Instead of Bootstrap Address, search for the port name WC_defaulthost.
Note: By default, Transportation Manager is mapped to the default host. After TMWeb has been
installed, you can confirm this from the admin console by navigating to Applications > Application
Types > WebSphere enterprise applications > tm. Click Virtual Hosts in the Web Modules
Properties section to see the virtual host assignment.
If the application has previously been deployed on this server, perform the following steps to remove
it.
Remove a previous deployment

1. Ensure that the WebSphere application server is running.
2. Log into the admin console from a browser (default URL is in the form:
http://MyHostname:9060/admin).
3. In the navigation panel, select Applications > Application Types > WebSphere enterprise
applications.
4. Select tm (check box on the left) and click Stop if tm is running.
5. Select tm again, and click Uninstall.
6. Click OK to proceed with uninstall.
7. Click Save at the top of the page.
Note: If doing a Network deployment, first click Preferences and ensure that the check box is
selected for Synchronize changes with Nodes. If not, select it, and click Apply before you
save).
8. If you access a different database instance than the earlier remove the JDBC, see Remove the
JDBC provider information (on page 58).
Remove the JDBC provider information

1. In the navigation panel, click Resources > JDBC > JDBC Providers.
2. Click Delete.
3. Click the Save link to save the changes.
Install the Web interface for WebSphere

The following section describes the steps necessary to install and configure the Web Interface for use
with the WebSphere application server.
Start the Web interface Installation

Note: If the Web Interface (TMServer) application exists from a previous installation, remove it. See
Remove a previous deployment (on page 58).
1. Log in as the administrative user (usually root).
2. Run TMWebSetupWS (found under TMWeb directory in the product) using the command sh
TMWebSetupWS.bin. Run it within an X windows client such as xterm (X windows is not required if
running as a Silent install).
3. The setup program displays the Introduction screen. Click Next.

Installation
4. The program displays a notice about installation using root user ID. Click Next.
5. To accept the Software License Agreement terms, select I accept and click Next.
6. Enter the complete path to the Signed License File issued by JDA Support. Click Next.
7. Enter the path to the WAS_PROFILE_HOME directory. Click Next.
8. Enter the path where the database client software is installed. Click Next.
9. Enter the database connection information as described in the following:
• User: The database username.
• Password: The password for the database username.
• Database Name: The actual Oracle SID (not the alias) for the database server.
• Database Hostname: The name of the server hosting the database.
• Database Port Number: The TCP/IP port number used to access the database (for example:
default is 1521 for Oracle).
10. Click Next.
11. At the DSC Host field, enter the name of one or more computers that are running the DSC
program. If the DSC port number is not 3390, include it after the computer name (separated by a
colon). If there are two or more computer names, separate them with commas, for example:
DSCHost1:4010,DSCHost2,DSCHost3:4020
In this example, TM-Web connects to DSCHost1 on port 4010 if available. If not, it connects to
DSCHost2 on the default port of 3390. And finally, if the first two machines are not available, it
connects to DSCHost3 on port 4020.
In production deployments, JDA recommends you to use the same DSC port on all servers in the
same workgroup in order to reduce complexity. It is even simpler to allow the software to default
to port 3390 by specifying only hostnames in this field.
12. Enter the WebSphere Bootstrap Address Port (as determined in the preparation steps).
13. Click Next.
Complete the Web interface installation

1. Review the summary information and click Install if it is all correct. The program installs the
Transportation Manager files and classes into the WAS_PROFILE_HOME/InstallableApps
directory.
2. Click Done to complete the installation program.
3. If the installer reports errors, verify the install log XML file in the target install folder.
4. Start the WebSphere application server, if not already running (see the following instructions).
5. Open a command window in the tm/config directory under
WAS_PROFILE_HOME/installableApps.
6. The thread pool and DB connection settings in tmenv.sh allows up to 500 simultaneous users. If
you have more than 500 users, contact JDA Support to determine the required modifications to the
WebSphere configuration.
7. Check the WAS_PROFILE_HOME/properties/soap.client.props file and ensure that
com.ibm.SOAP.requestTimeout is set to at least 360 (the default value of 180 seconds may be
too low and may result in a timeout error during deployment). If it is too low, edit the file, increase
it to 360 or more, and save the file. You may need to remove the failed TM deployment from
WebSphere Admin Console before re-trying the deployment.
8. Run the deployTM script as follows to deploy the application without credentials on the command
line.
Installation
deployTM.sh 2>&1 | tee deploy.log

This process takes 5 - 10 minutes. If you have enabled Global Security and do not supply
credentials on the command line, the script prompts you for the username and password of the
administrator, five different times. You can avoid this by supplying credentials on the command
line as in the following example:
deployTM.sh -username myuser -password mypassword 2>&1 | tee deploy.log
Credentials supplied on the command line are visible to other UNIX users logged into the system
and can be retained in your command history file.
As a last step, the deployTM script automatically runs the mergeCustomization program to
update your web screens with the latest changes. The process takes several minutes the first time
it is run for each schema, but is faster on any subsequent reconfigurations.
Notes:
• In case you encounter the following exception at the end of the deployment, you can ignore it.
The xx01Cell.xxNode01.server1 part of the exception may vary according to the configuration
of your WebSphere environment. For example, tm01Cell.tmNode01.server1.
Exception:
An exception occurred while reading the deployed applications for the specified server.
xx01Cell.xxNode01.server1.
It may occur as a part of the following exceptions:
PLGC0008I: The Plug-in is generating a single-server plug-in configuration file for the cell.
xx01Cell, node xxNode01, server server1.
PLGC0028E: An exception occurred while reading the deployed applications for the specified
server. xx01Cell.xxNode01.server1.
PLGC0005I: Plug-in configuration file * /usr/local/IBM/WebSphere8.5.0.1-
64bit/AppServer/profiles/xx/config/cells/plugin-cfg.xml.
• The mergeCustomization.sh script must be run for every applicable database after you
perform the database upgrade to this TM version, and for any new databases created. The
database configuration information is stored in the tmenv file.
9. Verify that the merge***Customization.log files have no errors (where *** can be Chart, List,
NavPad, ScreenElement, Search, or Workflow). These files are empty if the operation is successful.
If not, correct any problems and try again - search the last few lines of the deployTM script for
the exact syntax. If your customizations cannot be merged, use RESET instead of MERGE, which
overwrites user customizations to the web interface.
You are now ready to stop and restart the WebSphere application server as in the following
instructions. This refreshes the environment, complete with the new Transportation Manager
application.
Note: To change the configuration at any time, you can edit the tm/config/tmenv file under the
WAS_PROFILE_HOME/installableApps directory and re-run the deployTM step (after
removing the previous deployment - see Remove a previous deployment (on page 58)).
Administer the WebSphere application server

This section describes the steps to start and stop the application server. These steps must be
performed using a root level user, unless the installation has been configured for non-root deployment
(not described in this manual).

Installation
For single-server deployments, the WebSphere Administration server process is active in the same
process as the applications. The default administration URL for single-server deployments is
http://MyHostname:9060/admin, and is accessible when the application server instance is started. For
network deployments, the administration process runs as a separate application server. For more
information, search under Network Deployment at the IBM website.
Startup
Start the WebSphere application server
The following instructions apply to Single-Server deployments only. For Network Deployments, you
must start and stop the application server from the admin console for the network (under Servers >
Application Servers).
1. Open a command window in the WAS_PROFILE_HOME/bin directory.

2. Run the following command to start the server (including the TM application):
startServer.sh server1
Note: Do not stop and start the TM application from the admin console If the application server is
running in a single-server mode, it has to be stopped and restarted. Use tail -f
../logs/server1/SystemOut.log to monitor the log file. After initialization, the following message
is displayed:
Server server1 open for e-business.
3. You can also monitor the TM application log, which is located in logs/server1/tm/tmweb.log
under your WebSphere AppServer profile directory.
Start the HTTP server and HTTP admin server

1. On your AIX web server, open a command window in the HTTP bin/ directory, for example,
/usr/HTTPServer/bin.
2. Run the following command to start the HTTP server:
apachectl start
3. You can verify the ../logs directory for any errors.
4. If intended, you can also start the HTTP admin server. Do this using the adminctl start command.
The admin server is accessed using a browser and a URL which specifies the hostname and admin
port, for example:
http://MyWebServer:8008
Note: If no admin users have been set up, the admin web page informs you the procedure for creating
such users.
Shutdown
Stop the HTTP Server
1. To stop the HTTP Admin Server (if running), run the following command from the HTTP bin
directory on your AIX web server:
adminctl stop
2. To stop the HTTP Server, run the following command from the HTTP bin directory on your AIX web
server:
apachectl stop
Stop the WebSphere application server

1. To stop the WebSphere application server for a Single-Server deployment, run the following
command from the WebSphere bin directory:
stopServer.sh server1
Installation
2. To stop the server in a network deployment, log into the network admin console, navigate to
Servers > Application Servers, select the server to stop and click Stop.
Change the WebSphere configuration

During installation, the parameters that you enter are stored in a file called tmenv.sh under the
WAS_PROFILE_HOME/installableApps/tm/config directory. These parameters are then used to
configure your installation.
To change the configuration later, you can edit this file and rerun the deployTM script (after using the
WebSphere admin console to stop the TM application and uninstall it).
To change the DB_PASSWORD, it is encrypted and cannot be edited in the tmenv.sh file. Instead,
change your other DB connect information if required, save the file, and from the command prompt
run encrypt.sh mypasswd (substitute your own value for mypasswd). This script updates the
encrypted password right in the tmenv.sh file.
Some common examples of other parameters that might require reconfiguration are:
• DSC_HOST *: None
• DB_USER,DB_PASSWORD,DB_NAME:None
• SESSION_TIMEOUT_MINUTES:30
• EJB_SESSION_TIMEOUT_SECONDS:2000
Note: * Can contain the Hostname or Hostname:Port. See Start the Web Interface Installation (on
page 58) for possible values.
Note: See comments in the tmenv file if you change any TIMEOUT values.
There are other parameters stored in the tmenv file that can be changed to meet specific
requirements.
Reconfiguration and JavaScript recompiles

Wherever possible, configuration changes must be made using steps described in the previous section.
However, certain reconfigurations and data changes require you to recompile the dependent JavaScript
files to recognize the change. These include:
• Changes in the date format or the presentation of days and hours (see Change the date format
and presentation of days/hours (on page 53)).
• Changes in the default error message. See Change default error message (on page 53).
• Addition of one or more preferred (high priority) countries that are displayed first in pick lists. See
Configure preferred countries (on page 54).
• Modification or addition of state/province code data (not usually required since states are supplied
for most countries as of version 6.2.1). These changes are automatically reflected in the Web
Interface when you run refreshJSfiles and restart the Web Application server. No additional steps
are necessary for this particular task.
• Addition of optional support for additional languages. These language packs are available
independently and have their own installation instructions.
The refreshJSFiles program performs the necessary recompiling. It also allows you to perform the
changes listed previously by making modifications to required files present in the following locations:
• <tm profile>/installableApps/tm/tmp/tm_misc/config
• <tm profile>/installableApps/tm/tmp/help
After the changes are made, the program updates the archive and compiles the JavaScript files.

Installation
Most of these changes are configured independently for each locale (combination of language +
country). The standard release includes a locale for Canadian English and U.S English, and both are
configured with a date format of mm/dd/yyyy for consistency with previous releases.
Start the refreshJSFiles process

2. Stop the TM Web Application from the WebSphere admin console.
3. Uninstall the TM Web Application from the admin console.
4. Open a command window and navigate to the tm/config directory under
WAS_PROFILE_HOME/installableApps.
5. Run the refreshJSFiles.sh command. No parameters are required.
6. If you are running this program to recognize changes to state codes or names, proceed to
Complete the refreshJSFiles process (on page 64). No other changes are necessary.
7. When the program pauses with a prompt, open a new window and navigate to the
installableApps/tm/tmp/tm_misc/config folder.
The following sections describe how to perform the various reconfigurations. For the changes to take
effect, run the refreshJSFiles process.
Note: Do not change other files unless specifically instructed. This includes the date format fields in
application.properties, which are only relevant to internal programming routines and do not control the
user interface. Many of the files extracted to this folder are managed independently by deployTM.
Change the date format and presentation of days/hours

The date format, or the display of days and hours for a user locale can be edited from the User Locale
Properties page, which can be accessed from the Transportation Manager Web UI. Navigate to the User
Locales page by selecting Environment > UI Customization > User Locales. On the User Locales
page, verify if the existing defaults for localization are appropriate for your environment. If not, select
the appropriate locale and click the Properties button.
For more information, see the List of User Locales topic in the Transportation Manager User Guide or
the OnLine Expert in Transportation Manager.
Change default error message

Edit the Error_<locale>.properties files as required, for example, Error_en.properties. The
default error message and tag are as follows:
ERROR_PAGE=Please retry the operation again or at a later time. If the issue persists,
please call technical support hotline at 1-111-111-1111 or send us an email at
<a href="mailto:support@company.com">support@company.com</a>.
Configure preferred countries

To add Preferred (High Priority) Countries, edit the Application.properties file. Search for the section
called #High Priority Countries and add a new entry for each intended priority country. Use the 2-
character ISO country code. Ensure to sequence them in your preferred order, and use a unique
number on each line, for example:
#High Priority Countries
CountrySelection.1=ES
CountrySelection.2=US
CountrySelection.3=CA

Installation
Complete the refreshJSFiles process

1. Close any open windows and files in the directory, except the refreshJSFiles command window,
for the program to clean up its temporary files and folders.
2. Click Enter in the refreshJSFiles command window when done to allow the program to complete
the process.
3. Verify the refreshJSFiles.log file for any errors. It is empty if successful.
4. Deploy your changes by running the following command:
(or see Complete the Web interface installation (on page 59) for instructions on deploying in an
environment that is configured with Global Security)
5. Verify the merge***Customization.log files for errors as inthe initial installation.
6. Stop and restart the WebSphere application server as described earlier in this chapter.
Configure Web servers to proxy requests

It is important to implement the appropriate level of security using firewalls and SSL (Secure Socket
Layer) if the application is to be deployed outside the immediate LAN. This can include the Internet, or
a WAN where other networks are not provided full access to the local network. The technical people or
consultants must design and execute the Web application deployment, in order to address your specific
security requirements.
It is possible to run the Web Interface using only the Web application server and a browser (plus a
DSC). However, the normal configuration is to have an independent Web server in a DMZ (outside the
internal firewall) that redirects the appropriate Web traffic to the Web application server within the
private network.
HTTP Web server configuration for WebSphere

You can run the WebSphere application server and the HTTP server on the same machine or on
separate machines to achieve the DMZ configuration described earlier. In either case, see the IBM
documentation website (http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp)
for the WebSphere Application Server.
For information on communicating with the Web Server, navigate to WebSphere Application Server
(Distributed Platforms and Windows), Version 8.5.5 > Setting up intermediary services >
Communicating with web servers.
Access the TM-Web interface on WebSphere

The Web interface is accessed using a compatible browser version (of Internet Explorer). Access is
usually through a standard Web server such as IBM HTTP server. The configuration instructions found
at the link mentioned earlier allow the Web server to proxy any URL requests for tm/ documents to
the WebSphere application server.
It is also possible to access WebSphere directly, if intended, assuming that the application port (for
example, 9080) is not filtered out by a firewall.
Access the Web interface through a Web server

2. Enter the appropriate Web URL as http://<server name>/tm, for example:
http://mywebserver/tm.
Note: The <server name> can be preceded by "www." if the application is being deployed over the
Internet.

Installation
Access the Web interface directly through the WebSphere server

2. Enter the appropriate Web address as http://<server name>:<port #>/tm, for example,
http://mywebserver:9080/tm. The number following the server name and preceded by the colon
must be the same as the application port configured for the WebSphere application server.
Install the TM RIA-Web interface for WebSphere

Note: Ensure that TM Web has been configured for SSO prior to deploying the TMRIA application and
please verify that the <WAS_PROFILE_TM>/app/lib hierarchy has been created.
1. Locate the WebSphere deployment package (tmria_deploy_AIX_8.1.0.0.tar.gz) for the
Transportation Manager Smartbench UI and extract the contents to the
<WAS_PROFILE_TMRIA>/installableApps folder. This creates the tmria folder and its
dependent folders under <TMRIA_Inst_Root>.
2. Copy the <TMRIA_Inst_Root>/lib folder to <WAS_PROFILE_TMRIA>.
3. Configure the TMRIA Deployment:
a. Copy the common values from the <TM_Web_Inst_Root>/config/tmenv.sh file to
<TMRIA_Inst_Root>/config/tmenv.sh with the following exceptions:
Note: The process to configure TMRIA is very similar to that of the Transportation Manager
Web UI (TM Web). Many values from the TM Web configuration values are used by the TMRIA
configuration.
b. Edit the <TMRIA_Inst_Root>/config/tmenv.sh file.
Provide values for the following variables.
Configuration Configuration
Comments
Parameter Value
WAS_HOME Path to WebSphere Application Server
installation directory
TM_WEB_PROFILE Name of TM Web profile
TMRIA_PROFILE Name of TMRIA profile
TMRIA_APP_SERVER Name of TMRIA AppServer
WS_PORT WebSphere Port for TMRIA

TM_APP_SERVER_HOST Full domain qualified path to TM Web
host
For example: tmwebhost.jda.com
TMWEB_EXTERNAL_URL External URL for TM Web (optional)
TM_APP_SERVER_SSL_PO SSL Port for TM Web
RT
GOOGLE_MAP_ENABLE true/false If True, and a valid map key is
provided, the TMRIA application will
display a map view of the load’s stops.
GOOGLE_MAP_KEY Google Map API key to enable mapping
view

Installation
Configuration Configuration
Comments
Parameter Value
CIS_INSTALL_DIR Location where CIS 8.1 has been
installed. Provide the path to the cis-
sdk directory.
4. Run the TMRIA Deployer.

Change folders to <TMRIA_Inst_Root>/config and run deployTmria.sh 2>&1 | tee
deploy.log
5. Inspect the deploy.log file. If there are no errors, the tmria application is now installed and
configured. You can start the tmria application from the WebSphere Administrative console.
Note: See Prepare to install the Web interface (on page 56) for details on using the WebSphere
Administrative console.
TM installation directories for RIA

• TM_Distribution: Root folder of the Transportation Manager production distribution.
• TM_Root: Folder where Transportation Manager is installed.
• WAS_PROFILE_TMRIA: Location of the TMRIA WebSphere application server profile. For
example, WS: /usr/IBM/WebSphere/AppServer/profiles/AppServer01
• WAS_PROFILE_TM: Location of the TMRIA WebSphere application server profile. For example,
/usr/IBM/WebSphere/AppServer/profiles/AppServer02
• TMRIA_Root: Folder where TMRIA Web application is installed. For example:
• <WAS_PROFILE_TMRIA>/installedApps/<cell>/tmria.ear
• TMWeb_Root: Folder where TM Web UI is installed. For example:
• <WAS_PROFILE_TM>/installedApps/<cell>/tm.ear
• TMRIA_Inst_Root: Folder where TMRIA Web application deployer is unpackaged. For example,
<WAS_PROFILE_TMRIA>/installableApps/tmria
• TM_Web_Inst_Root: Folder where TM Web deployer is unpackaged. For example,
<WAS_PROFILE_TM>/installableApps/tm
• CIS_HOME: Folder where CIS is installed.
Install Transportation Manager Mobile

See the "Deploy JDA Transportation Manager ABPP" (on page 89) section for information on how to
use the ABPP Deployer to install the TM Mobile solution.
CIS configuration
1. Verify that the CIS security configuration is set up.
2. Open %CISDIR%\8.1\cis-sdk\conf\repository\cis\security\config.xml
3. Verify that there is an entry for TransportationManager.
<jaas:entry name="TransportationManager" type="basic">
<jaas:instance />
</jaas:entry>

Installation
Service Parameters
Service Parameters are located in tmmobile.xml inside the deployment jar in \cfg\properties.
These properties can be edited if required by the project; see the individual descriptions for details.
• GLOBAL_MAX_QUERY_ROWS: The maximum number of rows to return for any entity.

• Default=100
• MAX_LOAD_QUERY_ROWS: The maximum number of loads to return on a query.
• Default=50
• PURGE_AGE_IN_DAYS: The number of days since a load was a viewed to be purged.
• Default=15
• PURGE_WAIT_PERIOD_IN_DAYS: The number of days between each purge cycle.
• Default=15
• EMPLOYEE_STOP_CONTACT_ROLE: The type of contact that is displayed for contact
information.
• Default=APPOINTMENTS
Documents and Tables

• TRACKING_HISTORY: The recently tracked table. Logs the date and time when you view a
particular load. This is so that this load is readily available on your next load search.
Client Provisioning Service (CPS) Configuration

Request for a CPS entry to be added between your customer's and your ABPP Server. Contact JDA
Support. The mobile application looks up a particular customer, which maps your ABPP server. Your
ABPP server is mapped to TMGR, so as long as the mobile application through CPS can reach the ABPP
server, this will be setup correctly.
For the mobile application to work over 3G, 4G and different wifi networks (other than the one the
ABPP server is on), the ABPP server must be externally available. Contact Cloud Support for setting up
an external ABPP server.
The entry should look like the following:
"name":"JDAPlatform", "url":"http://server:abppport/base/rest/TRACKANDTRACE/"
Update TMGR Permissions

There are entities that need to have permission updates applied for data to be viewable. Navigate to
%TMDIR%\MetaData\UI\FunctionalSecurity.xml and update the following:
• <tmsecurity:functional2 entity="APChargeType" operation="findEntities"

employee="true" carrier="true"/>
• <tmsecurity:functional2 entity="APChargeType" operation="getEntity" employee="true"
carrier="true"/>
• <tmsecurity:functional2 entity="EventControlStatusReasonCodeType"
operation="findEntities" employee="true" carrier="true"/>
• <tmsecurity:functional2 entity="EventControlStatusReasonCodeType"
operation="getEntity" employee="true" carrier="true"/>
• <tmsecurity:functional2 entity="EventReasonType" operation="findEntities"

Installation
• <tmsecurity:functional2 entity="EventReasonType" operation="getEntity"

• <tmsecurity:functional2 entity="ReferenceNumberType" operation="findEntities"
• <tmsecurity:functional2 entity="ReferenceNumberType" operation="getEntity"
employee="true" customer="true" carrier="true"/>
• <tmsecurity:functional2 entity="AddressType" operation="getEntity" employee="true"
carrier="true" />
• <tmsecurity:functional2 entity="LoadScheduleEntryType" operation="findEntities"
• <tmsecurity:functional2 entity="LoadScheduleEntryType" operation="getEntity"
employee="true" customer="true" carrier="true"/>
Single Sign On (SSO) Configuration

Single Sign On needs to be enabled for security purposes.
1. Set ssoEnabled=true in %ABPP_INSTALL_DIR%\web\base\WEB-

INF\classes\x2.properties.
2. Set SSOLoginModule=tdm in %ABPP_INSTALL_DIR%\web\base\WEB-
INF\classes\x2.properties.
3. Set the following in
%ORACLE_DIR%\Middleware\user_projects\domains\base_domain\startWebLogic.cm
d:
set JAVA_OPTIONS=%JAVA_OPTIONS% -
Djava.security.auth.login.config=%ABPP_INSTALL_DIR%\web\base\WEB-INF\classes\cis-
auth.config
4. Set the following in %ABPP_INSTALL_DIR%\web\base\WEB-INF\classes\cis-jaas.config:
tdm
{ com.i2.tm.core.security.TDMLoginModule required
LanguageFileNamePrefix="MyResource"
UserKey="tdm.user"
PasswordKey="tdm.password"
TMHostFileName="tmhost"
TMHostKey="tm.host"
TMPortKey="tm.port"
HtmlUserName="USER_NAME"
HtmlPassword="PASSWORD";
};
5. Place TDMLogin.jar in %ABPP_INSTALL_DIR%\web\base\WEB-INF\lib.
6. Add the tmhost.properties file in %ABPP_INSTALL_DIR%\web\base\WEB-INF\lib.
• tm.host=server
• tm.port=tmport
7. The following highlighted element must be added to the
%ORACLE_DIR%\Middleware\user_projects\domains\base_domain\config\config.xml
element:
<security-configuration
xmlns:xacml="http://xmlns.oracle.com/weblogic/security/xacml"
xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator">
<name>abpp</name>

Installation
…
<node-manager-username>admin</node-manager-username>
<node-manager-password-
encrypted>{AES}5bQamvxqXfjB7NNDDOEBX1wgdkcYtlkQrmUrb2EfmAY=</node-manager-password-
encrypted>
<enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials
>
</security-configuration>
Uninstall Transportation Manager

Note: x.x is the TM version. For example, 8.1.
Uninstall the TM-Web interface

Note: TM web uninstallation does not delete everything from <TM_HOME>\tmria_domain. Delete
the folder after uninstallation.
WebLogic
1. Run Uninstall Transportation Manager Web x.x.exe at <TM_HOME>.\tmgr_domain\
UninstallerData. The Uninstall Transportation Manager Web x.x page is displayed.
2. Click Uninstall. Both TM web and Smartbench are uninstalled and the Uninstall Complete page is
displayed.
3. Click Done.
WebSphere
1. Log in to the WebSphere admin console where TM web is installed. For example, log in to
http://<SomeServer>.<company>.com:4900/ibm/console.
2. Select tm from the list in the Enterprise Applications section and click Uninstall. The Uninstall
Application section is displayed.
3. Click OK. tm is not displayed in the list of enterprise applications.
4. Click Save.
5. Delete the tm folder from <WS_HOME_PROFILE>/installableApps.
Uninstall Transportation Manager server

1. Run Uninstall Transportation Manager x.x.exe at <TM_HOME>.\tmgr_domain\
UninstallerData. The Uninstall Transportation Manager x.x page is displayed.
2. Click Uninstall. All components in the <TM_HOME>. folder are deleted and the Uninstall Complete
page is displayed.
3. Click Done.
Note: TM uninstallation does not delete everything from the <TM_HOME> folder. Delete the folder
after uninstallation.
Uninstall Transportation Manager Mobile

1. Delete the imported ABPP TrackAndTrace project jar.
2. On an iOS device, delete the application.

Installation
3. Contact Client Provisioning Service (CPS) to delete your Customer ID.
Install Transportation Planner on Windows

This section provides information about installing Transportation Planner (TP) on the Windows
platform, and performing required configuration tasks.
Install TP programs on Windows

User rights requirement
To install TP programs, you must have administrator rights for the computer on which the programs
are being installed. You must have rights to create, modify, and delete files and directories in the
install directory. See Windows documentation for details about user rights.
Install-time license
You must have a license from JDA Support to install TP.
JDA Support Services provides customer support for all JDA solutions.
1. Contact JDA Support Services at the JDAUser website (http://www.jdauser.com) to request the
license key file.
2. Place the license key file on the client machine where you are installing TP. The default license file
location used in the TP installer is C:\JDA, but you can specify a different location. During the
installation process, you are prompted to provide the license file name and location.
Installing on Windows x64

The TP Optimization server (Shipment Consolidation Engine) and the Shipment Scheduling Engine
components are supported on the Windows x64 platform. 32-bit Windows is not supported. For more
information on supported software and platform, see JDA Transportation Planner Release Notes.
When installing:
• Use RateWare Server or RateWareXL. RateWare DLL is not supported in Transportation Planner
8.1.
• The DllName setting for the Transportation Manager Distance Engine in setup.xml is defaulted to
JavaDistanceInterface.
• Copy RMIServer.properties from the <tp_home>/properties folder to the
<cis_home>/properties folder, to use the JavaDistanceInterface to connect to the TM Distance
Engine and you want to use the CIS Manager to control the SCE adapters. You do not need to edit
this properties file. Restart the CIS Agent after copying this file so that the file is found.
Run the TP installation program on Windows

The TP installation program includes several installation sets that you can use to install selected TP
components.
Note: Before TP installation, you should obtain an install-time license key from JDA Support. For
information, see "Install-time licensing" (on page 77).
Caution: The TP installation program may not run if other software is running on your computer.
Specifically, PCAnywhere, Dell OpenManager, and antivirus software can prevent the installer from
running successfully. JDA recommends that you close these and other applications before running the
TP installation.

Installation
Note: If you do not accept the default folder names in the installation, ensure that the names of any
folders that you create do not contain spaces.
1. Run SetupTP.exe from the TP Installation media. A progress dialog box is displayed as
InstallAnywhere extracts the installation files. When the file extraction is complete, the
Introduction dialog box is displayed. Click Next.
2. Select the "I accept the terms of the License Agreement" option in the License Agreement dialog
box and click Next. The Choose JDA License File dialog box is displayed.
3. Indicate the location of your license file. For information on obtaining an install-time license, see
"Install-time licensing" (on page 77). Click Next to select the default location, or click Choose and
navigate to the directory where you have placed the license file. After choosing the license file
location, click Next. If your license file is valid, the Product License confirmation message box is
displayed. Click OK.
4. The Choose Install Sets dialog box is displayed with the Typical option selected by default. Select
the type of installation:
• RRO: Installs the server that performs Routing and Rating and Optimization. This selection
also installs the Parameter File Editor and Strategy Editor, and the Distance Engine Creation
Tool.
• TPUI: Installs the TP web user interface.
• SS: Installs the Shipment Scheduler engine and web user interface components only.
• Typical: Installs all the folders and files required for the Routing and Rating and Optimization
server. This is the default installation option.
• Custom: The Choose Product Features page is displayed and you can select any combination
of the TP components.
The installation sets defined above are available in a drop-down list. You can select a specific
installation set, such as RRO, as a starting point, and then select or deselect individual
components. The rest of the installation process is determined by the components you select.
The components and their configuration requirements are displayed in the following table:
Component Description Configuration Requirements

Shipment Scheduling Installs the Shipment Installation folder
Engine Scheduling Engine. Infrastructure Services
Java SDK
SS Data Input Sources
Route Rate and Installs the Route Rate and Installation folder
Optimization server Optimization server. You can Infrastructure Services
set up multiple instances of
Java SDK
this server.
RRO Data Input Sources
RRO Instances
Transportation Planner Installs the TP client (the web Installation folder
web interface interface) for the Route Rate Infrastructure Services
and Optimization server and
WebLogic
for the Shipment Scheduler
server. Java SDK
RRO/TPUI Data Input Sources

Installation

Optimization Server Optimization Server Monitor. Infrastructure Services
Monitor
Java SDK
RRO Instances
Documentation Installs all TP product Installation folder
documentation (PDF files and Infrastructure Services
OnLine Expert).
Java SDK
5. The Choose Install Folder dialog box is displayed, select the location for installing TP. Click Next to
select the default destination, or click Choose and navigate to the drive and directory in which you
want to install TP. After choosing the installation destination, click Next.
6. The Infrastructure Services Configuration page is displayed:
• Enter the folder in which the JDA Infrastructure Services program is installed in the
Infrastructure Services Directory, or click Choose to navigate to the folder where JDA
Infrastructure Services is installed.
• Enter the name of the machine that hosts the Infrastructure Services (CIS) server in the
Infrastructure Services Host field.
• Enter the port number for the Infrastructure Services host in the Infrastructure Services Port
field and click Next.
7. If you select the TP UI, the WebLogic Directory Configuration page is displayed.
• In the WebLogic Domain directory folder field, indicate the location of your WebLogic domain
directory. If your WebLogic domain directory is not the default, click Choose to navigate to the
location of your WebLogic domain directory.
• In the WebLogic Server directory folder field, indicate the location of your WebLogic server
home directory. If your WebLogic server directory is not the default, click Choose to navigate
to the location of your WebLogic server directory.
Click Next.
8. If you select the TP UI, the TPUI LDAP Information page is displayed.
• In the LDAP Host field, enter the name of the machine that is hosting your LDAP server.
• In the LDAP Port field, enter the port number for the LDAP host.
Note: If you are not using LDAP as your authentication mechanism, you can clear the default
values from these fields.
Click Next. The Java SDK Directory page is displayed.
9. Enter the path to the folder where you installed Java SDK.
Click Next to accept the default path, or click Choose to navigate to the location for Java SDK.
Click Next. If your ORACLE_HOME variable is empty, the Choose Oracle ojdbc.jar file page is
displayed.
10. Navigate to the folder where your Oracle ojdbc.jar file is located, and then click Next. If you
select the TP UI, the Default TP Web Client Mode is displayed.
11. Select which user interface, TP (TPUI), or Shipment Scheduler (SSUI) should be the default and
then click Next.
12. Click Next. The Transportation Manager Database Information page is displayed.

Installation
13. Enter the User, Password, Database Alias (the Service Name), Hostname, and Port for your
Transportation Manager database, and then click Next. The Transportation Manager DSC Server
page is displayed.
Note: The TP installer verifies the database connection. If it cannot make the database connection,
a message box is displayed indicating that it "Could not connect to <Database Alias> as
<User>/<Password>." Click Ignore to continue or click Previous to return to the Database
Information page.
14. Enter the machine name to be used as a DSC Host and click Next. If you are installing the Routing
and Rating and Optimization server, the Configure Routing and Rating/Optimizer Engine Instance
names page is displayed.
15. Enter the list of instances you want to create, separating the values with commas. The default is
RR,OPT to configure an instance of the RouteRate Server as RR and the Optimization Server as
OPT. The installation program creates required python scripts, properties files, and setup.xml files
to run each individual instance you list. If you clear out the instance value (that is, you are creating
no named instances), the installation program installs only the default files for the engine and sets
the <TP_INSTALLED_SCE_NOINSTANCE> value in tpConfig.xml to true. For additional information,
see "Install Routing and Rating/Optimizer engine instances on Windows" (on page 75). For
complete information about creating instances, see Transportation Planner Implementation Guide.
Click Next. If you select the Shipment Scheduling Engine, the Shipment Scheduler Data Input
Sources page is displayed.
16. Select the data input sources that you use on the Shipment Scheduler Data Input Sources page:
• Manufacturing ABPP Basic: One of your data input sources is a JDA Manufacturing ABPP Basic
(Operational Data Store) database.
• Supply Chain Planning and Optimization: One of your data input sources is a JDA SCPO
database.
Click Next. The Data Source DB Info page is displayed.
Shipment Scheduler data source.
18. If you are installing the Shipment Scheduler server, the Configure Shipment Scheduler Engine
Instance names page is displayed. Enter the list of instances you want to create, separating the
values with commas. The default is SSE. The installation program creates required python scripts,
properties files, and setup.xml files to run each individual instance you list. For additional
information, see "Install shipment scheduler engine instances on Windows" (on page 76). For
complete information about creating instances, see Shipment Scheduler Implementation Guide.
Click Next. The Choose Shortcut Folder page is displayed.
19. Select an option on the Choose Shortcut Folder page for the location where TP product icons will be
created. Click Next. The Pre-Installation Summary page is displayed.
20. Review the details of the installation and click Install. A progress indicator is displayed while the
Setup program installs the TP programs.
21. If necessary for configuration reasons, the Setup program prompts you to restart your computer.
When programs are installed, the Install Complete dialog box is displayed. Click Done. The dialog
box closes and installation is complete. Restart your computer after TP installation.
Note: Details of any errors during installation are provided in the installation log (by default,
Transportation_Planner_InstallLog.log) located in the \tp\8.1\logs directory.
Installation results on Windows

After successful installation, the TP program group that you access from the Start menu contains some
or all of the following items. The set of available items is determined by the components you selected
for installation:

Installation
• Parameter File Editor: Starts the Parameter File Editor that enables you to create and edit the
OptParameters file. For information, see Transportation Planner Strategies and Parameters.
• Strategy Editor: Starts the Strategy File Editor that enables you to create and edit strategy files.
For information, see Transportation Planner Strategies and Parameters.
• Transportation Planner Launcher: Starts the Transportation Planner Launcher, from which you
can run TP scripts. For more information, see Transportation Planner Implementation Guide.
• Uninstall: Starts the Uninstall program.
Setup installs a series of folders and files when all components are installed. By default, the main TP
installation directory (C:\JDA\tp\8.1) contains all the TP subfolders. If you have installed a subset of
TP components, not all folders listed below are installed.
• bin: Contains the command files and scripts for executing and configuring all TP components.
• config: Contains the configuration settings file (tpConfig.xml). It also contains subfolders for
specific components.
• cis: Contains TransportPlan, TransportPlanMetadata, and TransportationPlannerBindings files.
It also contains subfolders for the Shipment Consolidation Engine (SCE) and Shipment
Scheduling Engine (SSE).
• jetty: Contains the server used for the stand-alone server configuration tool.
• ldif: LDAP server configuration files
• properties: Contains properties files for TP components.
• system_config: Contains system-level configuration files.
• template: Contains templates for several files used to run TP (runSCEServer64.py,
Setup.xml, tp_log.xml, and tp_log_cxx.xml).
• lib: Contains the .jar files required by TP.
• logs: Contains the TP installation log (Transportation_Planner_InstallLog.log) and a ReadMe
file that lists the locations and descriptions of logs that TP produces.
• PDFs: Contains the PDF format files of the TP user documentation.
• properties: Contains properties files that are modified from the configuration process and read
at runtime so that the TP client and engines can run properly.
• resourcebundles: Contains resource files for the TP interfaces.
• sce: Contains files and subfolders required for the Routing and Rating and Optimization server
(also called the Shipment Consolidation Engine or SCE). The top level of this folder contains the
executable to start the Shipment Consolidation Server (SCE.exe).
• 64: Contains the dlls and executables for running the server.
• archive: Used as the repository for saving archived files when using the TP web interface.
• checkpoints: Used as the repository for saving checkpoint files when using the TP web
interface.
• CrashReport: In the event of application crashes, files in this directory can help JDA Support
identify the issue.
• exports: If export definitions are configured, export files will be created here.

Installation
• i2distanceengine: The default location for distance data files, if applicable. A sample set of
data is provided with the installation; note that this data is not necessarily realistic, and is not
intended for business use. Within the i2distanceengine\creationtool folder is the Distance
Engine Creation Tool. This tool enables you to convert your distance and location data to a
distance engine.
• messages: If you enable message generation, this is the folder where TP messages are
written.
• reports: You can write reports to this folder. It is empty when the TP installation completes.
• strategies: Contains the sample strategy files, including ContinuousMoveStrat.strat,
Hub-ContinuousMoveStrat.strat, HubStrat.strat, and Strat.strat.
• sse: Contains settings files for the Shipment Scheduling Engine.
• logs: Contains Shipment Scheduler specific log files.
• xmldata: The default folder for XML format Shipment Scheduler files.
• ssui: Contains subfolders required for the Shipment Scheduler interface.
• defaults: Contains the default user interface configuration for the Shipment Scheduler
interface.
• tpui: Contains subfolders required for the TP interface.
• config: Contains configuration folders for each TP interface user. These folders contain
customization information.
• defaults: Contains the default user interface configuration for the TP interface.
• ldif: Contains ldif files you can use to set up your LDAP server to work with the TP interface.
• UninstallerData: Contains files and subfolders used to uninstall TP.
• xmldata: Contains folders with sample data in XML format (SamplePlan.xml).
• CIS: Contains \sce and \tmrh folders, each with a set of sample xml message files.
• tp: Contains a sample plan in XML format (SamplePlan.xml). This is the default location in
which the TP web interface checks for XML files for input.
Setup also installs folders and files to the following directories:
• lib\i2DocLibrary: Contains the files and subfolders required to view the TP documentation.
Install Routing and Rating/Optimizer engine instances on Windows

When you install the Routing and Rating Server and Optimizer Engine, configure multiple instances by
providing a comma-separated list of instance IDs. The installation program creates a unique set of
supporting files for each instance. The file name includes the instance ID and uses it to configure and
run the specific instance. For example, if you create one instance called RR, the TP installation program
creates:
• runTPShipmentConsolidationEngine64-RR.py
• ShipmentConsolidationBindings-RR.xml
• tp_log_cxx-RR.xml
• tp_log-RR.xml
• Setup-RR.xml
The installation program also installs the instance-specific adapters for use with the CIS Manager. For
complete information, see Transportation Planner Implementation Guide.

Installation
Install shipment scheduler engine instances on Windows

When you install the Shipment Scheduler Engine, configure multiple instances by providing a comma
separated list of instance IDs. The installation program creates a unique set of supporting files for each
instance. The file name includes the instance ID and uses it to configure and run the specific instance.
For example, if you create one instance called SSE, the TP installation program creates:
• runTPShipmentSchedulingEngine-SSE.py
• ShipmentSchedulerBindings-SSE.xml
• ss_log-SSE.xml
• Setup-SSE.xml
The installation program also installs the instance-specific adapters for use with the CIS Manager. For
complete information, see Shipment Scheduler Implementation Guide.
Uninstall TP programs on Windows

Uninstall TP to permanently delete TP and its components from your computer.
1. Select Start > Programs > Transportation Planner 8.1> Uninstall. The Uninstall
Transportation Planner dialog box is displayed.
Alternatively, you can navigate to the \UninstallerData directory (by default,
C:\JDA\tp\8.1\UninstallerData\). Double-click Uninstall TransportationPlanner81.exe. The
InstallAnywhere Uninstaller dialog box is displayed.
2. Click Uninstall. A progress indicator is displayed. When the software is completely removed, the
Uninstall Complete message is displayed.
3. Click Quit to complete the process.
Alternately:
1. Select Start > Settings > Control Panel from the Windows taskbar. The Windows Control Panel
is displayed.
2. Click Add/Remove Programs. The Add/Remove Programs Properties dialog box is displayed.
3. Select Transportation Planner 8.1 from the list box.
4. Click Add/Remove.
5. Click Yes when you are prompted to completely remove TP and its components. TP is removed
from your computer.
6. Click OK when the process is complete.
Note: The Uninstall process does not remove all files. To re-install TP in the same path, do not
delete the TP directory or any files left in it. You can delete these files and directories if you are not
re-installing a new version of TP in the same directory. You might need to remove shared files that
TP no longer uses. Use caution when removing shared files.
Install Transportation Planner on Solaris

This section provides information about installing Transportation Planner (TP) on the Solaris platform,
and performing required configuration tasks.

Installation
Install TP programs on Solaris

You must have the appropriate administrator rights for the computer on which you are installing TP in
order to successfully install the application, including read, write, and execute permissions for the files
and folders in the installation directory. See your system documentation for details about user rights.
Install-time licensing
You require a license from JDA Support to install Transportation Planner.
1. Contact JDA Support Services at the JDAUser website (http://www.jdauser.com) to request for
the license key file.
2. Place the license key file on the client machine where you are installing Transportation Planner.
The default license file location used in the Transportation Planner installer is C:\JDA (on Windows
platforms) and /opt/jda (on UNIX platforms), but you can specify a different location. During the
installation process, you are prompted to provide the license file name and location.
Run the TP installation program on Solaris

components.
Caution: Ensure that the CIS_HOME system variable is defined before you install TP. If the variable
is not set, the installation program cannot run several scripts used to configure the TP components. It
is recommended that you close all other programs before running the installation program.
If you do not accept the default folder names in the installation, ensure that the names of any folders
that you create do not contain spaces.
1. Copy the installation programs from the TP Installation media to your Solaris file system.
2. Run SetupTPSun.bin using the sh shell command. A progress dialog box is displayed as
Introduction dialog box is displayed.
3. Click Next. The License Agreement dialog box is displayed.
4. Select the "I accept the terms of the License Agreement" option to agree to the license terms, and
click Next. The Choose License File dialog box is displayed, in which you indicate the location of
your license file. For information, see "Install-time licensing" (on page 77).
5. Click Next to select the default location, or click Choose and navigate to the directory where you
have placed the license file. After choosing the license file location, click Next. If your license file is
valid, the Product License confirmation message box is displayed. Click OK. The Choose Install
Sets dialog box is displayed with the Typical option selected by default.
6. Select the type of installation that you want to perform:
also installs the Parameter File Editor and Strategy Editor, the Distance Engine Creation Tool,
and the Transportation Manager Request Handler.
• TPUI: Installs the TP web interface.
• SS: Installs the Shipment Scheduler engine and web interface components only.
• Typical (default option): Installs all of the folders and files required for the Routing and Rating
and Optimization server.
• Custom: The Choose Product Features page is displayed where you can select any
combination of the TP components.
Installation
components. The rest of the installation process will be determined by which components you
select.

Java SDK
Optimization Server Optimization server. You can Infrastructure Services
Java SDK
this server.
RRO/TOM Data Input Sources
RRO Instances
Monitor
Java SDK
RRO Instances
Transportation Planner Installs the TP client (the Web Installation folder
Web UI user interface) for the Route Infrastructure Services
Rate and Optimization server
WebLogic
and the Shipment Scheduling
Engine. Java SDK
RRO/TOM/TPUI Data Input
Sources
online help).
Java SDK
The Choose Install Folder dialog box is displayed where you select the location for installing TP (by
default, /opt/jda/tp/8.1).
7. Click Next to select the default destination, or click Choose and navigate to the drive and
directory to install TP. After choosing the installation destination, click Next.
8. The Infrastructure Services Configuration page is displayed:
• In the Infrastructure Services Directory field, enter the folder in which the JDA
Infrastructure Services program is installed or click Choose to navigate to the folder where
you installed JDA Infrastructure Services,
• In the Infrastructure Services Host field, enter the name of the machine that is hosting
your Infrastructure Services (CIS) server,
• In the Infrastructure Services Port field, enter the port number for the Infrastructure
Services host, and then click Next.
9. If you selected the Shipment Scheduler Web UI or the TP UI, the WebLogic Directory Configuration
page is displayed.
• In the WebLogic Domain directory folder field, indicate the location of your WebLogic
domain directory (by default, C:\bea\user_projects\domains\base_domain). If your
WebLogic domain directory is not the default, click Choose to navigate to the location of your
WebLogic domain directory.

Installation
• In the WebLogic Server directory folder field, indicate the location of your WebLogic server
home directory (by default, c:\bea\wlserver_12.1.2\server). If your WebLogic server
directory is not the default, click Choose to navigate to the location of your WebLogic server
directory.
Once you have selected your WebLogic settings, click Next.
10. If you selected the TP UI, the TPUI LDAP Information page is displayed.
Once you have selected your LDAP settings, click Next. The Java SDK Directory page is displayed.
11. On the Java SDK Directory page, enter the path to the folder where you installed Java SDK. Click
Next to accept the default path, or click Choose to navigate to the location for Java SDK. Click
Next. The Choose Oracle ojdbc5.jar file page is displayed.
12. Enter the full path to the ojdbc5.jar file. You can also click Choose and navigate to the file. Click
Next. If you selected the TP UI, the Default Transportation Planner Web Client Mode is displayed.
13. Select which interface, TP (TPUI) or Shipment Scheduler (SSUI) should be the default then click
Next. If you select RRO, the RRO Client Data Input Sources page is displayed.
page is displayed.
15. Note: The TP installer verifies the database connection. If it cannot make the database connection,
a message box is displayed indicating that it "Could not connect to <Database Alias> as
<User>/<Password>." Click Ignore to continue or click Previous to return to the Database
Information page.
see Install Routing and Rating/Optimizer engine instances on windows (on page 75). For complete
information about creating instances, see Transportation Planner Implementation Guide
Click Next. If you selected the Shipment Scheduling Engine in the previous step, the Shipment
Scheduler Data Input Sources page is displayed.
18. Select the data input sources that you will use on the Shipment Scheduler Data Input Sources
page:
• Manufacturing ABPP: One of your data input sources is a JDA Manufacturing ABPP Basic
database.
database.
19. Enter the User, Password, Database Alias (the Service Name), Hostname and Port for your
Shipment Scheduler data source.. If you selected Transportation Manager as a TP Data Input
Source, the Transportation Manager Database Information page is displayed.

Installation
Transportation Manager database. The Transportation Manager DSC Server page is displayed.
Enter the name of the machine you will be using as a DSC Host and click Next. If you are installing
the Routing and Rating and Optimization server, the Configure Routing and Rating/Optimizer
Engine Instance names page is displayed.
to run each individual instance you list. For additional information, see "Install Routing and
Rating/Optimizer engine instances on Solaris". For complete information about creating instances,
see the Transportation Planner Implementation Guide 8.1.
Click Next. The Choose Link Location dialog box is displayed.
22. On the Choose Link Location dialog box, choose an option for the location where Transportation
Planner product shortcut links will be created. Click Next. The Pre-Installation Summary dialog box
is displayed.
23. Review the details of the installation. If the details are correct, click Install. A progress indicator is
displayed while the Setup program installs the TP programs.
Note: When you click Install, Setup checks for enough disk space to complete the installation.
Due to an InstallAnywhere issue on UNIX platforms, you may receive an incorrect error message.
If you receive a message indicating that there is not enough disk space, but you are sure that
enough disk space exists, you must close the installer, set the environmental variable that disables
the check for disk space, and re-run the installer.
To set the CHECK_DISK_SPACE variable at the UNIX prompt, run:
export CHECK_DISK_SPACE=OFF.
24. When the progress indicates that the installation is complete, click Done. The UNIX prompt is
displayed.
Note: Details of any errors occurring during installation are provided in the installation log (by
default, /opt/jda/tp/8.1/logs/Transportation_Planner_InstallLog.log).
After completing the installation of TP programs and required software, see "Configure TP on
Solaris" (on page 115).
Installation results on Solaris

Setup installs a series of folders and files to your system when all components are installed. The
default main TP installation directory is
/opt/jda/tp/8.1. This root installation folder contains all the TP 8.1 subfolders.
• config: Contains configuration settings files including the main TP settings file (tpConfig.xml). It
also contains subfolders for specific components.
• cis: Contains TransportPlan, TransportPlanMetadata, and TransportationPlannerBindings files.
It also contains subfolders for the Shipment Consolidation Engine (SCE) and Shipment
Scheduling Engine (SSE).
• ldif: LDAP server configuration files.

Installation
• EventNotif: Contains a file used to define event notification.

• properties: Contains properties files that are modified from the configuration process and read at
runtime so that the TP client and engines can run properly.
• resourcebundles: Contains resource files for the TP interface.
• sce: Contains files and subfolders required for the Shipment Consolidation Engine.
interface.
identify the issue.
data is provided with the installation; this data is not necessarily realistic, and is not intended
for business use. Within the i2distanceengine\creationtool folder is the Distance Engine
Creation Tool. This tool enables you to convert your distance and location data to a distance
engine.
• reports: You can write reports to this folder. It is empty when the TP installation completes.
• strategies: Contains the sample strategy files, including ContinuousMoveStrat.strat, Hub-
ContinuousMoveStrat.strat, HubStrat.strat, and Strat.strat.
• sse: Contains settings files for the Shipment Scheduling Engine.
• ssui: Contains subfolders required for the Shipment Scheduler user interface.
• defaults: Contains the default user interface configuration for the Shipment Scheduler
interface.
• tpui: Contains subfolders required for the TP user interface.
• defaults: Contains the default user interface configuration for the TP interface.
• xmldata: Contains folders with sample data in XML format (SamplePlan.xml).
• CIS: Contains /sce and /tmrh folders, each with a set of sample xml message files.
which TP checks for XML files for input.
Uninstall TP programs on Solaris

Installation
Note: You must uninstall TP from the TP parent directory or from a directory outside the TP path. If
you uninstall TP from a TP subdirectory, you cannot return to the parent directory.
1. Run Uninstall_TransportationPlanner81 using the sh shell command. By default,
Uninstall_TransportationPlanner is located in the /opt/jda/tp/8.1/UninstallerData folder. The
About to Uninstall dialog box is displayed.
2. Click Uninstall. A progress indicator is displayed while Transportation Planner uninstalls. When
uninstallation is complete, the Uninstall Complete dialog box is displayed.
3. Click Quit. A UNIX prompt is displayed and TP is uninstalled.
Install Transportation Planner on AIX

This section provides details about installing TP on the IBM AIX platform, and performing required
configuration tasks. For more information on supported software, see JDA Transportation Planner
Release Notes.
Note: Install the IBM patch: 4019054 April 2008 IBM C++ Runtime Environment Components for AIX
for computers that do not have the XL C++ 8.0.0.18 compiler (Feb 2008) installed, Installation of this
patch requires root or superUser privileges.
Install TP programs on AIX

You must have the appropriate administrator rights for the computer on which you are installing TP in
order to successfully install the application, including read, write, and execute permissions for the files
and folders in the installation directory. For more information, see your AIX documentation for details
about user rights.
X-Windows environment requirement

You must have an X-Windows environment to successfully install TP on AIX.
Install-time licensing
You require a license from JDA Support to install TP.
1. Contact JDA Support Services at the JDAUser website (http://www.jdauser.com ) to request for
the license key file.
2. Place the license key file on the client machine where you are installing Transportation Planner.
The default license file location used in the Transportation Planner installer is C:\JDA (on Windows
platforms) and /opt/jda (on UNIX platforms), but you can also specify a different location. During
the installation process, you are prompted to provide the license file name and location.
Run the TP installation program on AIX

components.
Caution: Ensure that the CIS_HOME system variable is defined before you install TP. If not set, the
installation program cannot run several scripts used to configure the TP components. Close all other
programs before you run the installation program.
Note: If you do not accept the default folder names in the installation, ensure that the names of any
folders that you create do not contain spaces.
1. Copy the installation programs from the TP Installation media to your AIX file system.

Installation
2. Execute SetupTPAIX.bin using the sh shell command. A progress dialog box is displayed as
Introduction dialog box is displayed.
3. Click Next. The License Agreement dialog box is displayed.
4. Select the "I accept the terms of the License Agreement" option to agree to the license terms, and
click Next. The Choose License File dialog box is displayed, in which you indicate the location of
your license file. See "Install-time licensing" (on page 82).
5. Click Next to proceed with the default location, or click Choose and navigate to the directory
where you have placed the license file. After choosing the license file location, click Next. If your
license file is valid, the Product License confirmation message box is displayed. Click OK. The
Choose Install Sets dialog box is displayed with the Typical option selected by default.
6. Select the type of installation that you want to perform:
also installs the Parameter File Editor and Strategy Editor, the Distance Engine Creation Tool,
and the Transportation Manager Request Handler.
• TPUI: Installs the TP web interface.
• SS: The program installs the Shipment Scheduler engine and web user interface components
only.
• Typical (default option): Installs all of the folders and files required for the Routing and Rating
and Optimization server.
• Custom: The Choose Product Features page is displayed where you can select any
combination of the TP components.
components. The rest of the installation process is determined by which components you select.
The following table lists the installation components and their requirements:

Java SDK
Optimization Server Optimization server. You can Infrastructure Services
Java SDK
this server.
RRO/TOM Data Input Sources
RRO Instances
Monitor
Java SDK
RRO Instances
Transportation Planner Installs the TP client (the Web Installation folder
Web UI user interface) for the Route Infrastructure Services
Rate and Optimization server
WebLogic
and the Shipment Scheduling
Engine. Java SDK
RRO/TOM/TPUI Data Input

Installation

Sources
online help).
Java SDK
The Choose Install Folder dialog box is displayed where you select the location for installing TP (by
default, /opt/jda/tp/8.1).
7. Click Next to select the default destination, or click Choose and navigate to the drive and
directory to install TP. After choosing the installation destination, click Next. The Infrastructure
Services Configuration page is displayed:
• In the Infrastructure Services Directory field, enter the folder in which the JDA
Infrastructure Services program is installed or click Choose to navigate to the folder where
you installed JDA Infrastructure Services,
• In the Infrastructure Services Host field, enter the name of the machine that is hosting
your Infrastructure Services (CIS) server,
• In the Infrastructure Services Port field, enter the port number for the Infrastructure
Services host and then click Next.
8. If you selected the TP UI, the TPUI LDAP Information page is displayed.
Once you have selected your LDAP settings, click Next. The Java SDK Directory page is displayed.
9. On the Java SDK Directory page, enter the path to the folder where you installed Java SDK. Click
Next to accept the default path, or click Choose to navigate to the location for Java SDK. Click
Next. If you are installing on a WebSphere/Oracle stack, the Choose Oracle ojdbc5.jar file page is
displayed.
10. Enter the full path to the ojdbc5.jar file. You can also click Choose and navigate to the file. Click
Next. If you selected RRO, the RRO Client Data Input Sources page is displayed.
page is displayed.
Note: The TP installer verifies the database connection. If it cannot make the database connection,
a message box is displayed indicating that it could not connect to <Database Alias> as
<User>/<Password>. Click Ignore to continue or click Previous to return to the Database
Information page.
see Install Routing and Rating/Optimizer engine instances on windows (on page 75). For complete
information about creating instances, see Transportation Planner Implementation Guide.
Click Next. If you selected the Shipment Scheduling Engine in the previous step, the Shipment
Scheduler Data Input Sources page is displayed.
14. Select the data input sources to use on the Shipment Scheduler Data Input Sources page:
Installation
• Manufacturing ABPP: One of your data input sources is an JDA Manufacturing ABPP
database.
database.
Shipment Scheduler data source. If you selected Transportation Manager as a TP Data Input
Source, the Transportation Manager Database Information page is displayed.
Transportation Manager database. The Transportation Manager DSC Server page is displayed.
Enter the name of the machine you will be using as a DSC Host and click Next. If you are installing
the Routing and Rating and Optimization server, the Configure Routing and Rating/Optimizer
Engine Instance names page is displayed.
to run each individual instance you list. For additional information, see "Install Routing and
Rating/Optimizer engine instances on AIX". For complete information about creating instances, see
the Transportation Planner Implementation Guide.
Click Next. The Choose Link Location dialog box is displayed.
18. On the Choose Link Location dialog box, choose an option for the location where TP product
shortcut links will be created. Click Next. The Pre-Installation Summary dialog box is displayed.
19. Review the details of the installation. If the details are correct, click Install. A progress indicator is
displayed while the Setup program installs the TP programs.
Note: When you click Install, Setup checks for enough disk space to complete the installation.
Due to an InstallAnywhere issue on UNIX platforms, you may receive an incorrect error message.
If you receive a message indicating that there is not enough disk space, but you are sure that
enough disk space exists, you must close the installer, set the environmental variable that disables
the check for disk space, and re-run the installer.
To set the CHECK_DISK_SPACE variable at the UNIX prompt, run:
export CHECK_DISK_SPACE=OFF.
20. When the progress indicates that the installation is complete, click Done. The UNIX prompt is
displayed.
Note: Details of any errors occurring during installation are provided in the installation log (by
default, /opt/jda/tp/8.1/logs/Transportation_Planner_InstallLog.log).
After completing the installation of TP programs and required software, see "Configure TP on AIX" (on
page 117).
Installation results on AIX

Setup installs a series of folders and files to your system when all components are installed. The
default main TP installation directory is /opt/jda/tp/8.1. This root installation folder contains all the
TP 8.1 subfolders.
• config: Contains configuration settings files including the main Transportation Planner settings file
(tpConfig.xml). It also contains subfolders for specific components.
• cis: Contains TransportPlan, TransportPlanMetadata, and
TransportationPlannerBindings files. It also contains subfolders for the Shipment
Consolidation Engine (SCE) and Shipment Scheduling Engine (SSE).
Installation
• ldif: LDAP server configuration files.
• EventNotif: Contains a file used to define event notification.
• properties: Contains properties files that are modified from the configuration process and read at
runtime so that the TP client and engines can run properly.
• resourcebundles: Contains resource files for the TP interface.
• sce: Contains files and subfolders required for the Shipment Consolidation Engine.
interface.
identify the issue.
data is provided with the installation; note that this data is not necessarily realistic, and is not
intended for business use. Within the i2distanceengine\creationtool folder is the Distance
Engine Creation Tool. This tool enables you to convert your distance and location data to a
distance engine.
• messages: If you enable message generation, TP messages are written to this is the folder.
• reports: You can write reports to this folder. Note that it is empty when the TP installation
completes.
• strategies: Contains the sample strategy files, including ContinuousMoveStrat.strat, Hub-
ContinuousMoveStrat.strat, HubStrat.strat, and Strat.strat.
• sse: The top level of this folder contains settings files for the Shipment Scheduling Engine.
• ssui: Contains subfolders required for the Shipment Scheduler user interface.
• defaults: Contains the default user interface configuration for the Shipment Scheduler user
interface.
• tpui: Contains subfolders required for the TP user interface.
• defaults: The default user interface configuration for the TP interface.

Installation
• xmldata: Contains folders with sample data in XML format. (SamplePlan.xml).
• CIS: Contains /sce and /tmrh folders, each with a set of sample xml message files.
which TP checks for XML files for input.
Uninstall TP programs on AIX

Note: You must uninstall TP from the TP parent directory or from a directory outside the TP path. If
you uninstall TP from a TP subdirectory, you cannot return to the parent directory.
1. Run Uninstall TransportationPlanner81 using the sh shell command. By default,
Uninstall_TransportationPlanner is located in the /opt/jda/tp/8.1/UninstallerData folder. The
About to Uninstall dialog box is displayed.
2. Click Uninstall. A progress indicator is displayed while TP uninstalls. When the uninstallation is
complete, the Uninstall Complete dialog box is displayed.
3. Click Quit. A UNIX prompt is displayed and TP is uninstalled.
Configure web servers for proxy requests to TP

Implement the appropriate level of security using firewalls and Secure Socket Layer (SSL) if the
application is to be deployed outside the immediate LAN. This includes the Internet or a WAN where
other networks are not given complete access to the local network. You need to design and run the
Web application deployment, in order to address your specific security requirements.
The Web Interface is run using a WebLogic server and a browser. However, the standard configuration
is to have an independent Web server in a DMZ (outside the internal firewall) that redirects the
appropriate Web traffic to the WebLogic Server within the private network. The following are the
instructions pertaining to configuration of Apache. Other web servers also support this functionality,
but they have not been specifically tested.
Configure Apache to forward requests to the WebLogic server for TP

1. Go to the Apache website (http://www.apachelounge.com/download/win64/).
2. Click VC10 Win64.
3. Click VC10 SP1 vcredist_x64.exe and install Visual C++ 2010 SP1.
4. Click httpd-2.2.x-win64.zip and wait for the download to complete.
5. Unzip the file to c:/Apache2 .
6. Create a folder, C:\Plugins\Apache, on the server where Apache Web Server is installed.
7. Download Oracle WebLogic Web Server Plugins Version 12.1.2 from Oracle website
096117.html).
8. Extract the contents of the downloaded zip file(WLSPlugins12c-12.1.2-17082596.zip) to
C:\Plugins\Apache.
Note: The file name ( WLSPlugins12c-12.1.2-17082596.zip )may change based on the patch.
Ensure that the plugin is for Version 12.1.2.
9. Navigate to C:\Apache2\conf and add the following content to the httpd.conf file:
LoadModule weblogic_module C:/Plugins/Apache/lib/mod_wl.so
Installation
<IfModule mod_weblogic.c>
ConnectRetrySecs 5
ConnectTimeoutSecs 600
KeepAliveEnabled true
SecureProxy OFF
KeepAliveSecs 180
WLCookieName JSESSIONID
</IfModule>
<Location />
</Location>
<Location /tpui >
</Location>
10. Start the Apache web server.
For more information on configuring WLS Web Server Proxy Plug-In for Apache HTTP Server, see
Oracle documentation
(http://docs.oracle.com/middleware/1212/webtier/PLGWL/apache.htm).
Other web servers

For more information on the configuration of proxy plug-ins for various Web servers, see the WebLogic
website (http://docs.oracle.com/cd/E17904_01/web.1111/e14395/isapi.htm#autoId0).
ABPP application package contents

The JDA Transportation Manager Agile Business Process Platform package contains the following:
• setup.exe (setup.bin for UNIX): Used to install the application, ABPP runtime components, and
ABPP web application. Applications deployed in this manner do not require any additional ABPP
development components. The deployer also performs a co-located deployment of JDA
Transportation Manager ABPP and the JDA ABPP web application, where the two applications run
under the same JVM of the WebLogic or WebSphere application server. Both applications are run
when the WebLogic or WebSphere server starts.
The setup.exe (setup.bin for UNIX) is placed in the Deployer folder. To begin the installation, run
setup.exe (setup.bin for UNIX) and follow the instructions.
• deploy.jar: Contains the ABPP application. The file may also be named after the ABPP component
(that is, deployCEA.jar). The contents of the file include all ABPP services and models to
implement the functionality of the ABPP application. This list of ABPP services includes the JDA
Transportation Manager Foundation Components, which are a set of ABPP services that support the
API and UI based integration with JDA Transportation Manager. It is deployed with the ABPP
runtime by the deployer application.

Installation
• Documentation: All documentation, including this guide is contained in the Docs folder. Typical
documentation includes the JDA Transportation Manager ABPP component User Guide, JDA
Transportation Manager ABPP application Installation Guide, JDA Transportation Manager ABPP
Single Sign On Guide, and a Configuration Guide for the JDA Transportation Manager ABPP
application being deployed.
Deploy JDA Transportation Manager ABPP

The ABPP deployer application provides a graphical user interface to configure and install the project
archive of the ABPP application. It accepts various inputs about the target environment, such as the
database, the servlet engine to install the ABPP runtime on the target machine, and information on
how to deploy the archived ABPP Application in the target environment.
The following instructions describe the steps necessary to deploy the application in an environment
that consists of an Oracle WebLogic Application Server, Oracle Database, and Microsoft Windows
operating system.
Notes:
• Ensure that Java is available in the PATH.
• Ensure the WebSphere Profile server is in running mode.
1. Run the deployer application. An installation wizard is launched.

2. Click Next. Installation options are displayed.
3. Select the appropriate option and click Next.
4. Select the JDA Transportation Manager ABPP application jar file from the installation package when
prompted for the ABPP Project Archive and click Next. The License Agreement is displayed.
Note: The name of the jar file (for example, deployCEA.jar) is provided in the installation
document for the ABPP application.
5. Review and accept the license agreement and click Next.
6. Specify the location of the JDA ABPP license file provided by JDA and click Next.
7. Enter the folder location for the ABPP application. As part of deployment, the ABPP runtime is also
installed in this directory. Click Next.
8. Select the ABPP services from the Select service drop-down list and click Next.
Note: Each JDA Transportation Manager ABPP application may have unique configuration
requirements for one or more ABPP services.
See the installation guide of the application being installed so the necessary configuration can be
performed. If you do not configure the JDA Transportation Manager ABPP application, it may not
function properly.
9. Enter the port name for the ABPP server. Ensure that the port is not used by any other
application. Click Next.
10. Select the Servlet Engine (Oracle WebLogic or IBM WebSphere) and click Next.
• If you select Oracle WebLogic:
a. Select the domain directory of your WebLogic instance.
b. Enter the path of your WebLogic domain.
c. Click Next.
d. Specify the configuration details for the ABPP web application.
e. Specify a name for the ABPP web application.
Installation
Note: If you select the ABPP Web Application name as base, the URL to access the web
application in a browser is similar to
http://hostname.domain:weblogic_port/base/home
where the weblogic_port is defined in the config.xml file of the WebLogic domain.
• If you select WebSphere, you are prompted for the installableApps location:
a. Select a directory to copy the webclient archive (war file) that can be deployed in
WebSphere. For example (UNIX): /opt/WebSphere/AppServer01/installableApps.
b. Specify the name of the web application.
c. To automatically deploy the web client archive, select the Deploy WebClient Archive
check box. The deployer asks for more information about the application server. Deploy
the WebClient Archive to that server.
Note: The WebSphere AppServer must be running in order to use the webSphere deploy
functionality. If the WebSphere application server is not running and you select Deploy
WebClient Archive, the deployment fails. Any existing applications with the same Context
Root name as the application that you installed, are uninstalled and removed. If Deploy
WebClient Archive is not selected, skip to the step where you specify the path to the
JDK.
d. Specify the following information required for automatic deployment:
• WebSphere AppServer home directory: For example,
/opt/WebSphere/appServer01
• WebSphere Application Server Node/Cell: For example, cell01
• Context Root: Context root for your web application. The context root should be
exactly the same as the web application name you specified in the previous step
prefixed with "/". For example, if you specified "base" as the web application name,
specify "/base" for the context root. Otherwise, the deployment will fail.
11. Specify the path to the JDK to be used by the ABPP server.
12. Specify the path to the Oracle home directory. Click Next.
a. Specify the Oracle database host name, database port, and database driver and click Next.
b. Enter the database user name, password, SID, and TNS alias found in Oracle TNSNAMES.ora.
This information is for the Oracle schema to be used by the ABPP application, not
Transportation Manager. The installer pings to validate the database settings.
13. For a new installation, select the first option. The installer creates the database objects in the
schema. Click Next.
14. Specify the Windows Program Group where links to start the application are stored.
15. Select Install from the summary page to begin the installation process. After the installation and
configuration is complete, a status message is displayed before the schema generation step.
16. Click Next.
17. Click Next after the schema generation is completed. If there is no dataupload processing, ignore
any warning messages and click Next. The installer populates the base data and displays a
confirmation message.
18. Click Next. The installation log is displayed before completing the installer.
19. Click Done after the final screen indicates the completion of the installation of the ABPP
application.

Installation
Approval Chain
Installation steps
See "Deploy JDA Transportation Manager ABPP" (on page 89).
Freight Auction
Installation steps
See "Deploy JDA Transportation Manager ABPP" (on page 89).
Deviation from the standard ABBP application installation procedure

Freight Auction requires the following additional steps to be carried out during installation.
1. Follow Steps 1 through 12 described in "Deploy JDA Transportation Manager ABPP" (on page 89).
2. In Step 13 of that procedure, select Skip automatic schema creation and data population.
3. Follow the installation procedure from Step 14 until the end of the section.
Note: The installer does not display pages that pertain to schema creation and data population.
4. Run genSchema.bat (genSchema.sh for UNIX) from <%ABPP_WEB_INSTALL%>/bin to
create the schema.
5. Run uploadStaticData.bat (uploadStaticData.sh for UNIX) from
<%ABPP_WEB_INSTALL%>/bin to populate the static data.

Installation steps
See "Deploy JDA Transportation Manager ABPP" (on page 89) for details on the installation steps.

Post-installation
Chapter 5. Post-installation
Configure Transportation Manager
On Windows servers, the installation process creates shortcuts for all servers (processes) that start
manually.
On UNIX servers, template shell scripts are provided to set up the required paths and environment
variables, and to launch the DSC process. They can also launch servers that must be started manually.
For all platforms, there are pre-configured servers, and servers that require additional configuration
specific to your environment.
Configure the Distributed Service Coordinator (DSC)

The DSC monitors all non-Java Transportation Manager application servers. Configuration settings for
the DSC are stored in TM_HOME\dsc_config\dsc_config.properties and changed using the DSC
Configuration Editor. This program is launched using
TM_HOME\dsc_config\launch_dsc_editor.cmd (.sh in UNIX).
When the DSC is started, most monitored servers start automatically by default. The following servers
do not start automatically:
• CarrierSequentialTenderServer
• JDA Infrastructure Services Interface (Java process)
• Event Notification
• Proactive Monitoring (optional)
• Transportation Planner Adapters (Java processes)
• Report Distribution
These servers must be started manually, if required. The non-Java servers can be configured to be
started automatically. See Modify server autostart settings (on page 93).
The installation process prepares the DSC configuration based on your inputs. The configuration
program (dsc_config.cmd on Windows and dsc_config.sh on UNIX) is designed to perform the
following configuration steps:
1. Reads configuration settings from dsc_config.properties

2. Edits the hostconfig.rsp file (it contains the main server deployment information)
3. Runs xconfig to compile it and create the DSC.DB file (required to run the DSC)
4. Runs xdatasrc to modify DSC.INI to point to the correct schema
5. Verifies the target schema and re-initializes security tables if they are not current. This occurs
while upgrading from an older version, which used a different password encryption key.
The dsc_config program is automatically run during installation for Windows servers. For UNIX
servers, run it manually as described below. This program can also be used to point your configuration
to another schema.
Note: If using a UNIX application server and more than one environment on the network (for
example, Production and QA), ensure that the TM DSC Domain and the DSC Port are unique when you
install each environment. Otherwise, the environments can interfere with each other across the
network.
Modify the TM Domain and DSC ports, if required

Post-installation
1. Launch the DSC Configuration Editor using TM_HOME\dsc_config\launch_dsc_editor.cmd

(.sh in UNIX).
2. On the General tab, change the value for the DSC Domain Name to something other than
TMD1. The new value must be four characters long and contain only numbers or capital letters.
3. Save your changes and exit the DSC Configuration Editor.
4. Ensure that each UNIX and Windows application server is using the same TM Domain for a
particular environment (for example, QA) so that they can communicate.
5. Edit the TM_HOME/tmsrvenv.sh shell script on the UNIX server, and search for the line starting
with EXTREME_DSCPORT. Modify the default value 3390 to a free TCP/IP port.
6. If running more than one TM environments on an AIX server, search for LDR_CNTRL in the
tmsrvenv.sh file and change it to a value that is unique from the other environments, for
example:
LDR_CNTRL=USERREGS@NAMEDSHLIB=TM_NSLIB2; export LDR_CNTRL
This change must be made in AIX environments or the system throws memory errors, even when
there is sufficient memory.
Change the value in startCIS.sh to a unique value, for example:
LDR_CNTRL=USERREGS@NAMEDSHLIB=TM_CIS_NSLIB2; export LDR_CNTRL
Note: Do not run multiple TM environments on a single UNIX server for production environments.
There is a high risk of negative performance impact or accidental environment corruption through
human error.
7. On the Windows server, you must create a System environment variable called
EXTREME_DSCPORT and assign it the same value as the UNIX server. When you run "set |
findstr /ni extreme" from the command prompt, you must be able to see your new variable.
Note: You are now ready to configure the DSC manually.
Customize the DSC

Customization is required if specified by JDA, or for advanced users with unique requirements. For
UNIX environments and for some Windows installations using a customized server distribution, ensure
that dsc_config.properties is identical for all servers in the TM server group (as defined by the TM
DSC Domain parameter, which is stored in this file under config.domain).
Modify server autostart settings

The TM_HOME\dsc_config\dsc_config.properties file (as edited by the DSC Configuration Editor)
also controls the servers that autostart. If they are configured to autostart, they also restart
automatically if the DSC detects that they are no longer running. To change these settings, run
TM_HOME\dsc_config\launch_dsc_editor.cmd (.sh on UNIX). On the Deployment tab, select
the check box under the Always Up column for the servers you want to autostart.
If the intended server is not in the list on the left, select the Servers tab and ensure the Active box is
selected. You then see the server in your list of deployments.
After you have made the required edits, save your changes and run the dsc_config program as
described in Configure the Distributed Service Coordinator (DSC) (on page 92).
Modify machine settings to run specific servers

In most cases, Windows-only environments with multiple servers run in singlehost mode. Each
installation lists the current hostname or localhost in the dsc_config.properties file, and the DSCs do
not communicate as only one host is listed. It provides complete failover capabilities when all required
servers are running on more than one machine, and the CIS adapter and TM-Web interface have been
configured with more than one DSC.

Post-installation
In UNIX environments, all servers are configured to run on the UNIX machine except for the Reporting
Server, which must run on Windows. In some cases, you must also run the Distance Server on the
Windows machine if your distance engine is not supported on UNIX. To change the Distance Server
from HOST1 to HOST2, launch the DSC Configuration Editor, select the Deployment tab, and
change the Host Id for DistanceCalculatorServer from HOST1 to HOST2.
You must perform the same change on the Windows server, or you can just copy the revised
TM_HOME\dsc_config\dsc_config.properties file to that machine.
After you have made the required edits, run the dsc_config program on each applicable machine, as
described in Configure the Distributed Service Coordinator (DSC) (on page 92).
If you need to run other servers on Windows, see Server platform information (on page 165) for
details on servers that run only on Windows or those that must be run on UNIX if using that platform.
Customize the Hostconfig.rsp file

Manual changes are not required to this file since the DSC Configuration Editor provides you complete
control to TM server deployments. However, if JDA Support determines that such a change is
necessary, the following are the steps required to perform the change.
Note: Parameters in <angle brackets> in the hostconfig.rsp file are substituted from
dsc_config.properties when the dsc_config command is run. Do not change them manually.
1. Edit the template hostconfig.rsp file (located in the dsc_config\template folder - ensure to
create a backup copy of the original) and make the necessary changes. See the Transportation
Manager System Administration Guide or contact the JDA Support. Also, see Server platform
information (on page 165) for details on which servers run only on Windows or must be run on
UNIX if using that platform.
2. Run the dsc_config program as described in Configure the Distributed Service Coordinator (DSC)
(on page 92).
Start the DSC

If you have installed on a UNIX server, ensure that you have manually run the dsc_config. See
Configure the Distributed Service Coordinator (DSC) (on page 92) before starting the DSC.
Start the DSC on Windows systems

1. Double-click the DSC shortcut located in either:
• the Transportation Manager 8.1 folder on the desktop or
• Windows Start Menu > Programs > JDA Transportation Manager 8.1
You can also run dsc.exe -m info from Windows Explorer or a command window in the
TM_HOME directory.
Note: The -m info parameter is used to set the message logging level. Use this setting to display
various server programs that are registered or removed from the server map. If intended, you can
skip this parameter and the program defaults to a setting of error, will only show messages if
there are any issues.
2. To start the DSC for troubleshooting and not to launch the auto start servers, use the -u
parameter as shown below:
dsc.exe -m info -u
Start the DSC on UNIX systems

The UNIX installation includes a template shell program called tmsrvenv.sh to set up the required
paths and environment variables. This program is called by another shell start_servers.sh, that
starts the DSC and any required servers. Before starting the DSC, edit start_servers.sh to
uncomment the command lines for those servers that start manually after the DSC.

Post-installation
To start the DSC, run the following command:
sh start_servers.sh
This also starts servers in background mode and log the output to the logs directory.
Instead, you can run the following commands to launch the DSC only and capture the output to the
logs directory (first command ‘sources’ the environment):
. ./tmsrvenv.sh
dsc –m info -u > logs/dsc-out.log 2>&1 &
The -u parameter causes the DSC to refrain from auto starting the other server processes that it
normally would. If you start the DSC this way, start some servers manually as described later in this
chapter.
Like the Windows environment, the -m info parameter sets the logging level to be informative
without being too verbose.
Stop the DSC

Use the stopdsc command
Before stopping the DSC, ensure to stop the TM Process Monitor, if it is being used. It will not
automatically terminate the DSC if configured as suggested.
Stop the DSC process from the command prompt by running the stopdsc process from the TM_HOME
directory. The syntax is:
stopdsc <hostname> [<TM User ID> <TM Password>], for example:
stopdsc localhost TMUser TMPassword
On UNIX, you must source the tmsrvenv.sh file using . ./tmsrvenv.sh to initialize your
environment before running this command.
The hostname is mandatory, and this command can be used to stop a DSC process remotely or locally.
If you do not provide the optional User ID and Password on the command line, you are prompted to
enter them. The User must be a valid administrator for the application, and the DSC uses the
Administrative and BusinessProcessModel servers to authenticate the user and password.
The program communicates using the port specified in the EXTREME_DSCPORT variable, or defaults
to 3390 if the variable is not set.
The DSC first shuts down all managed server processes and then exits. It can take a minute or two for
all processes to terminate.
The Web Application server must be shut down separately as described in the TM-Web chapters for
WebLogic and WebSphere.
Other ways to stop the DSC

On Windows systems, click the Shutdown on the DSC command window to stop the DSC. The DSC
primarily shuts all managed server processes before terminating.
On UNIX systems, you can use ps -ef | grep dsc to find the process ID for the DSC process and issue
a kill command. The default kill settings (SIGTERM –15) provide sufficient time to the DSC to shut all
managed server processes before terminating.

Post-installation
Use parameter sets

In addition to the basic database access parameters, the server configuration is stored in a database
as a parameter set. Use these sets to configure each server function online. Some settings such as
cache configuration can be changed dynamically - you do not have to restart the server to recognize
the new values. Settings that are not dynamically recognized are static.
In addition to dynamic changes, parameter sets have parameter maintenance between upgrades. They
also allow you to visually manage the configuration for multiple servers and database schemas.
Each parameter set is derived from a predefined parameter set type. There is a set type for each
Transportation Manager server function. These set types define valid parameter names and the data
type for each parameter, indicate whether the parameter is dynamic, and provide the default value for
that parameter.
Bootstrap data includes all the necessary parameter set types, and a default parameter set for each
type. You cannot modify the parameter set types, but you can copy or modify the parameter sets.
The default parameter sets work for most installations, with few minor changes as specified in the
configuration instructions for the individual servers.
You can configure the parameter sets by accessing Server Configuration > TM Hosts > Parameter
Sets in the Transportation Manager web user interface. This is accessible only to the Employee type
users. Viewing and updating the parameter sets require the web user interface, and the web user
interface requires that at least the Admin Server and BusinessProcessModelServer are running. For
more information, see the List of Configuration Parameter Sets topic in the JDA Transportation
Manager User Guide and the Configuration Parameter Sets topic in the JDA Transportation Manager
System Administration Guide.
Server logging levels

Introduction to Transportation Manager logging
Transportation Manager uses the log4cxx framework for logging its non-Java processes. By default,
logging levels for most servers and utilities are set to INFO level (and higher), and logging to the
console is disabled except for warnings and error messages. Change the log settings to diagnose a
system problem.
Since many TM utilities such as DistPing also use log4cxx, INFO level information in the command
window is not displayed. To view the desired output, you need to either temporarily turn on console
logging as described below, or verify the appropriate log, in the TM_HOME\logs directory.
Configuration
XML configuration files in the TM_HOME\properties directory control the log settings. There are
specific *Log.xml files for various servers, and there is also a DefaultLog.xml file that controls the
configuration for the remaining servers and utilities.
The default settings for these files are suitable for production systems, but there is a utility named
logConfig (run using logConfig.cmd on Windows or logConfig.sh on UNIX), that allows you to alter
the logging levels for one or more processes and functions. These changes do not require a restart to
Transportation Manager, but can take a couple of minutes to activate as the server cache settings are
refreshed. An exception occurs when you create a new log configuration file. In this case, the server
must be restarted to recognize the settings.
A set of scripts in TM_HOME\tools\LogScripts make the bulk changes to the log settings easier.
The logConfig utility calls these scripts.
See the Transportation Manager System Administration guide.
logConfig examples
Post-installation
The following are a few examples of useful logConfig commands and scripts. The commands are run
from the TM_HOME directory (use logConfig.sh instead of logConfig on UNIX system).
Example 1: Turn on console INFO logging for all processes using the DefaultLog.xml configuration
file:
tools\logConfig appender Default Console root Threshold=INFO
Example 2: Set logging level to INFO for all reporting processes:
tools\logConfig set Default Tm.RptSrv=INFO
tools\logConfig set Default Tm.Crystal=INFO
tools\logConfig set Default Tm.Lib.Report=INFO
Example 3: Run the script to return all log settings to the default production system values:
tools\logConfig execute allProduction.logscript
Rolling Logs
The TM log4cxx logs are configured by default such that each log segment does not exceed 20MB. For
most logs, the system keeps five concurrent log segments for each process. Instead of creating a sixth
log segment file, it begins overwriting the oldest one.
The TM_Home\tools\LogScripts\examples.logscript file specifies how to change the maxIndex

and MaxFileSize parameters to modify the number of log segments or the size of each segment.
Note: If you set your production logging levels too high (that is, too inclusive), or if you specify too
small MaxFileSize value for individual log segments, it adversely impacts the performance.
Preconfigured servers
The servers listed in the following table are ready to use immediately after installation and do not
normally require further configuration.
The default parameter sets work for most installations, with a few possible changes required as
described in Alternative configurations (on page 98).
Default Shortcut or Single

Executable
Server function shell script active
1 parameter
name instance 2
set required
Administration AdmSrv.exe ADM -- --
3
CarrierSequentialTe AutoTdrSrv.exe AUTOTDR Y --
nderingServer
Batch API APIBatchSrv.exe APIBATCH -- --
BusinessProcessMo BObjSrv.exe BOBJ -- --
delServer
FinancialAndBatchS FinSrv.exe FIN -- Y
erver
3
Notification Agent NotifAgent.exe EVNT Y Y
Reporting (windows RptSrv.exe RPT -- --
only)
3
Report Distribution DistribRptSrv.ex DISTRIBRP Y Y
e T

Post-installation

Executable
1 parameter
name instance 2
set required
TM Optimizer TMOptRequestS TMRS -- Y
Request Server erver.exe
1
There is no .exe extension on UNIX systems. For example, FinSrv.exe (Windows naming
convention) is called FinSrv on UNIX.
2
Single Active Instance servers can only have one active instance running against a schema at any
given time. See Single active instance servers (on page 101) for instructions on how to set up a
standby instance.
3
Alternatively, you can configure the DSC to autostart these servers as described in Modify server
autostart settings (on page 93).
The install program creates shortcuts on Windows systems for those servers that need them, and the
FinancialAndBatch and TM Optimizer Request Servers (which autostart by default). You can use these
shortcuts to manually start specific servers as required if you choose not to autostart them. The
Process Monitor also provides a way to autostart and monitor processes, but must not be used to
manage servers that are designed to be managed by the DSC. See Configure the Process Monitor (on
page 105).
On UNIX, you can run the start_servers.sh shell script to start the servers that apply to your
environment. Ensure to edit this file and tmsrvenv.sh as described in Start the DSC (on page 94).
For diagnostic purposes, any of these functions can be started manually from the command line with a
command shown below. (On UNIX, you must source the environment using the command .
./tmsrvenv.sh before starting a server manually.)
<Path\Executable Name> -PS <Parameter Set>
For example, the shortcut for the CarrierSequentialTenderingServer on a Windows system is similar to:
C:\jda\tmgr\8.1\AutoTdrSrv.exe -PS AUTOTDR
Alternative configurations
Notification agent
If using Event Notification, to send notifications through fax or email, see Send reports and
notifications through fax and email (on page 33).
Report server
This server uses a Crystal Reports runtime engine to process reports from Transportation Manager,
and must be run on a Windows server. You can print the reports or display them locally using the
viewer.
You can test this server from the TM-Web interface or the command prompt.
TM optimizer request server

This server monitors the TM Optimizer request queue and forwards requests to the Transportation
Planner Shipment Consolidation adapter through the CIS agent. For interactive requests through the
TP user interface, you must use the TM Request Handler adapter. To run both the request handler and
the request server against the same schema at the same time, you must use Instance Groups to direct
requests appropriately.

Post-installation
Before testing, Transportation Planner must be installed, and the Shipment Consolidation adapter must
be started.
The adapter can be started from the command line, the TP launcher using
runTPShipmentConsolidationEngine64-OPT.py, or from the CIS console. If you start from the launcher,
you can monitor requests in the startup window as they occur.
Configuration
The optimizer request server calls the TP Shipment Consolidation Engine (SCE) adapter. It is OPT by
default, as specified in the TM_HOME\dsc_config\dsc_config.properties file with the
config.sce_opt.inst1=OPT parameter.
Configuration parameters for this server are located in both the TMRS parameter set, and in
configuration files starting with RequestServer in the TM_HOME\properties\ folder. If you want to
reduce the wait time before the server reconnects to another available SCE OPT adapter, change the
ConnectionRetryIntervalSecs parameter in the RequestServerConnector.properties file. The default
value is 60 (seconds). Do not set this value below 30 or performance can be adversely affected. See
TM optimizer request server (on page 98).
Change/Add shipment consolidation adapters for optimization (OPT)

1. Configure the new adapters within Transportation Planner if you want to change the adapter name,
or add additional failover adapters to be accessed on an active/passive or round-robin basis.
(.sh in UNIX), select the Optimizer Insts tab, and make the required edits. Ensure to save your
changes when done.
3. Rerun the dsc_config program as described in Configure the Distributed Service Coordinator
(DSC) (on page 92).
Note: Any TP adapters running on remote machines must be imported into the CIS agent on the
local machine. If using multiple TP machines, ensure that all adapter instances have unique names
to avoid import errors. Therefore, you cannot use RR and OPT on more than one machine in this
case.
When dsc_config is run, the setting is automatically configured in TM_HOME\hostconfig.rsp
and in the resulting dsc.db file that is used during DSC startup.
You can override the SCE OPT Adapter Instance from the command line, and on Windows servers it
is available in the following places other than dsc_config.properties:
• Start menu shortcut for TM Optimizer Request Server in the form:
C:\jda\tmgr\8.1\TMOptRequestServer.exe -PS TMRS -TPINSTANCES OPT
• Desktop folder shortcut for TM Optimizer Request Server (same format as above).
Modify these OPT parameter settings to synchronize them with any changes you make to the TP
OPT instances in the dsc_config.properties file.
On UNIX servers, the start_servers.sh script picks up its settings directly from the
hostconfig.rsp file, so no other changes are required.
Run SCE(OPT) adapters in Round-Robin mode

By default, requests are always sent to the first adapter in the list as long as it is active. The next
adapter in the list processes the request only if the first one terminates. Configure the system to
process requests on a round-robin basis for load balancing, use parameter sets (on page 96) by
accessing Server Configuration > TM Hosts > Parameter Sets in the Transportation Manager web user
interface to edit the TMRS parameter set. Change the TPInstances parameter to include a comma-
separated list of SCE adapters (for example, OPT,OPT_2), and change NumPoolWorkers to equal the
number of SCE adapters to be accessed.

Post-installation
Then, restart the TM Optimizer Request Server to recognize the change.
Servers for Routing and Rating calls

Configuration
The following servers make calls to the Transportation Planner SCE adapter for Routing and Rating:
• AutoTdrSrvr
• BObjSrv
• CISSrv
• FinSrv
The SCE adapter for Routing and Rating is RR by default, as specified in the
TM_HOME\dsc_config\dsc_config.properties file with the config.sce_rr.inst1=RR parameter.
Change/Add shipment consolidation adapters for Routing and Rating (RR)

1. Configure the new adapters within Transportation Planner to change the adapter name, or add
additional load balancing adapters to be accessed on a round-robin basis.
(.sh in UNIX), select the Route Rate Insts tab, and make the required edits. Ensure to save your
changes when done.
3. Rerun the dsc_config program as described in Configure the Distributed Service Coordinator
(DSC) (on page 92).
Note: Any TP adapters running on remote machines must be imported into the CIS agent on the
local machine. If using multiple TP machines, ensure that all adapter instances have unique names
to avoid import errors (therefore, you cannot use RR and OPT on more than one machine in this
case).
When dsc_config is run, the setting is automatically configured in TM_HOME\hostconfig.rsp
and in the resulting dsc.db file that is used during DSC startup.
The TM inbound adapter (CISSrv) picks up its configuration from the
TM_HOME\dsc_config\cisSCEInstance.cmd file, which is created when dsc_config is run. So,
if you make any changes to the TP RR Instances, you must also re-run cis_config_parm as
described in Configure SSL transport (on page 107).This deploys the new instance setting to the
<TM>\properties\cisapi\TransportationManager-<instance ID>.properties. file
You can override the RR Instance setting from the command line, and on Windows servers it is
available in the following places other than dsc_config.properties:
• Start menu shortcuts for AutoTdrSrv and FinSrv in the form:
C:\jda\tmgr\8.1\AutoTdrSrv.exe -PS AUTOTDR -TPINSTANCES RR
C:\jda\tmgr\8.1\finsrv.exe -PS FIN -TPINSTANCES RR
• Desktop folder shortcuts for AutoTdrSrv and FinSrv (same format as above)
Modify these RR parameter settings to synchronize them with any changes you make to the TP RR
Instances in the dsc_config.properties file.
On UNIX servers, the start_servers.sh script picks up its settings directly from the
hostconfig.rsp file, so no other changes are required.

Post-installation
Single active instance servers

Single Active Instance servers such as the FinancialAndBatchServer are configured to allow only one
active instance by default. If a second server is started on another machine, it becomes a standby
instance. The server processes compete for the active status, and temporarily shut the other server to
avoid process conflicts and possible data corruption.
After a shutdown and restart, it takes about 3 minutes for these servers to recognize that they are the
only active instance. This time depends on the ServerDownTime setting (in seconds) in the parameter
set for the server, and the CacheReloadFrequency. It is possible to avoid this wait time if you are
certain that no instances of the server are started on another machine (for example, if running the
whole application on one machine).
To avoid this verification for the TM Optimizer Request server, use multiple Optimizer adapters and
balance the request processing load by running multiple request servers concurrently. Each TM
Optimizer Request server should be configured with a unique set of Optimizer adapters to prevent
collisions.
Configure Single Active Instance servers to avoid the active check

Note: Except in the case of the TM Optimizer Request server, this setting can lead to system instability
or data corruption if more than one instance of a single instance server is started against a single
schema, and one or more have the active option disabled.
Change the shortcut or start_servers.sh on UNIX to include:
-EnforceSingleInst F
For example:
C:\jda\tmgr\8.1\finsrv.exe -PS FIN -EnforceSingleInst F
Servers configuration
After you install the servers, perform the following configuration before using them. Some need
shortcuts or shell scripts and others do not because the DSC starts them automatically as required. For
diagnostic purposes, any of these functions can be started manually from the command line like the
preconfigured servers. On UNIX, you must first source the environment using the command.
./tmsrvenv.sh

Executable
1 parameter
name instance 2
set required
Distance Calculator DistSrv.exe DIST -- --
JDA Infrastructure CISServer.exe CIS Y --

Services Interface (or launch from
CIS)
3
Monitoring Server MntrIntprtAgent. MNTR Y Y
(optional) exe
Notes:
1
• There is no .exe extension on UNIX systems. For example, DistSrv.exe (Windows naming
convention) is called DistSrv on UNIX.
2
• Single Active Instance servers can only have one active instance running against a schema at
any given time. See Single active instance servers (on page 101) for instructions on how to
set up a standby instance.
3
• Alternatively, you can configure the DSC to autostart this server as described in Modify
servers autostart settings (on page 93).

Post-installation
Configure the Distance Calculator server

1. Windows Only: Ensure that you have altered the system PATH environment variable as instructed
in Install PC*Miler on Windows systems (on page 29).
2. Ensure that the default Distance Engines for Geo Code and for Distance/Transit Time are set
correctly for every country you use. This setting is available in the property sheet for each country
under System Settings > Miscellaneous > Countries using the TM web interface. Set the value
for Geo Code to Select... if not using this feature.
Note: The default value for Distance Engine for Distance/Transit is PC*Miler Practical for
the U.S and Canada in the bootstrap and training data. For Distance Engine for Geo-Code the
default value is null (appears as Select...).
3. Use parameter sets (on page 96) by accessing Server Configuration > TM Hosts > Parameter
Sets in the Transportation Manager web user interface to edit the following parameters in the DIST
parameter set as required. Separate the values with commas if there is more than one distance
engine for each field. Set the cache to On (the default value) if Routing and Rating performance is
a problem.
• Cache: The distance cache for each distance engine, for example: PC*Miler:On
• OvrPoll: The frequency in milliseconds to poll for new distance/time overrides entered through
Transportation Manager, for example: PC*Miler:30000
Note: In the DIST parameter set, permissible distance engines for the parameters shown above
are: PC*Miler, MileMaker, and I2Distance. MileMaker is used to represent both the MileMaker
and IntelliRoute products by Rand McNally.
4. To change other Distance Engine settings, log into the Web interface as an administrator and
navigate to Environment > External Engines. Select your engine type, and click Properties to
set User Name / Password for IntelliRoute (if using the Express Server), and to activate the
correct Version(s). You can also edit the Data fields with optional settings for the applicable
versions.
This step is required if setting up a new schema and are not using the default distance engine, or if
you need to modify the Route or other optional settings such as Border Restriction, 53 Foot Truck
Length, Custom Route, or the path to the I2Distance engine.
See the Transportation Manager User Guide or the OnLine Expert in Transportation Manager and
search for Distance Engines and Configuring External Engines, for more information.
Configure the JDA infrastructure services interface

Install JDA Infrastructure Services before you install Transportation Manager because there are
dependencies on the libraries in that product.
The following steps describe the configuration of the Infrastructure Services (CIS) Adapters and the
related XML configuration files. After configuration, these interfaces can be started as CIS adapters.
Instead, start the inbound interface using the CISServer executable.
The Transportation Manager adapters are available for inbound requests, and outbound requests via
Event Notification. The adapters support the following transport modes:
• RMI,
• WebSphere MQ Series
• JMS
The default transport for inbound is RMI.
Configure the JDA infrastructure services interface

1. Install the required client and server software for supported transports.
Post-installation
2. Run the inbound TM adapter using the CISServer binary provided, or using the CIS launch
command from the command prompt.
Note: Do not start this adapter from the Services Manager on a production system. In this mode,
adapter activity is logged to memory and the process eventually runs out and fails.
3. The CISServer process uses a JVM library from the Java SDK referenced during the Infrastructure
Services installation. Verify that the library is part of your path as follows:
Windows
Check that the installer added the path to the jvm.dll file to your system PATH, for example,
c:\jdk1.7.0\jre\bin\server
UNIX
Verify that the CIS_HOME and JAVA_HOME variables in TM_HOME/tmsrvenv.sh are correct. The shell
program creates a variable called JVM_PATH which is based on JAVA_HOME.
4. UNIX Only - Initialize your environment by sourcing the tmsrvenv.sh program as shown below.
. ./tmsrvenv.sh
5. Navigate to the %CIS_HOME%\bin directory (or $CIS_HOME/bin on UNIX) in your command
window.
Note: Set the variable CIS_HOME if not set earlier before using it. Make sure it is pointing to the
cis-sdk folder of CIS 8.1.
6. Enable logins in Infrastructure Services by running the following launch command (or launch.sh on
UNIX):
launch configureLoginModules.py anyuser anypassword TransportationManager insert -
loginModuleType basic
7. Open a command window in the TM_HOME\cis_config folder, for example,
C:\jda\tmgr\8.1\cis_config
8. If using MQ Series for any adapter, edit the cis_config_env.cmd script (.sh on UNIX), and add
values for the MQ_PATH, JNDI_CONTEXT_FACTORY, JNDI_PROVIDER_URL, MQ_QUE_MGR, MQ_HOST,
MQ_PORT, MQ_OUT_DIR, and optionally the JMS_LOGIN and JMS_PASSWORD variables.
9. If using JMS transport for any adapter, edit the cis_config_env.cmd script (.sh on UNIX), and
add values for the JMS_JNDI_CONTEXT_FACTORY, JMS_JNDI_PROVIDER_URL and
JMS_GUARANTEED_DELIVERY variables in the JMS Settings section.
10. Run the cis_config_parm script (cis_config_parm.sh on UNIX) to create the inbound CIS Adapter
(CIS Port Type is TransportationManager). There are two optional parameters. The first one is
the instance ID and the second one is transport. When omitted, the default is TMAPI and RMI.
Running cis_config_parm [TMAPI] [RMI] is the same as running cis_config_parm without any
parameters.
The script completes the parameter substitution for the configuration files of the adapter, and
registers it with the CIS agent to make it available in the CIS Register Adapters Manager UI (at
http://localhost:8088).
If using WebSphere MQ Series, the script loads the event definitions of the adapter to the specified
broker. For MQ Series, it configures the JNDI bindings as well.
11. If using an LDAP provider as your JNDI repository, complete the configuration by editing the
%TM_INSTALL%\properties\cisapi\TransportationManagerBindings-
<CISInstanceID>.xml file manually. Search for "MQ type=" and add the following attributes to
the config section (substitute appropriate values for your installation):
jndiNamePrefix="cn="
jndiUserName="myLDAPuser"
Post-installation
jndiPassword="myLDAPpassword"
- or -
jndiPasswordEncrypted="xxx"
(where "xxx" is an excryption of your password, as created by the JDA CIS encryptText.py script)
If any other parameters are necessary for your LDAP provider configuration, see the table of supported
attributes in the JDA Infrastructure Services 8.1 Reference Guide. Search in the MQ Series Bindings
chapter, under the heading, Setting MQ Binding Parameters.
Configure the CIS adapter for TM event notification (Outbound)

If using Infrastructure Services for outbound notifications, you must perform the following tasks in
addition to the previous section.
1. Open a command window in the TM_HOME\cis_config subdirectory, and run the
en_config_parm script (en_config_parm.sh on UNIX) in the following format to create the
outbound CIS Adapter (CIS Port Type is NotifyEventNotification). The program defaults to
webMethods transport if no parameter is provided.
en_config_parm [ RMI | MQ | JMS ]
For example: if using MQ Series, the command is:
en_config_parm MQ
The script completes the parameter substitution for the configuration files of the adapter, and
registers it with the CIS agent to make it available in the CIS Register Adapters Manager UI (at
http://localhost:8088).
If using WebSphere MQ Series, the script also loads the event definitions of the adapter to the
specified broker. For MQ Series, it configures the JNDI bindings as well.
2. If using an LDAP provider as your JNDI repository, complete the configuration by editing the
EventNotif\ENEnterpriseBinding.xml file manually. Search for "MQ type=" and add the
following attributes to the config section (substitute appropriate values for your installation):
jndiNamePrefix="cn="
jndiUserName="myLDAPuser"
jndiPassword="myLDAPpassword"
- or -
jndiPasswordEncrypted="xxx"
(where "xxx" is an excryption of your password, as created by the JDA CIS encryptText.py script)
If any other parameters are necessary for your LDAP provider configuration, please see the table of
supported attributes in the JDA Infrastructure Services 8.1 Reference Guide. Search in the MQ Series
Bindings chapter, under the heading, Setting MQ Binding Parameters.
Configure the monitoring server

When this optional server is run for the first time, it initializes access in the user interface tables for
the schema. After they have been initialized, you must grant access to one or more user groups from
the browser interface (after the Web Interface has been installed).
Allow monitoring access to a user group

1. Ensure that the DSC and the web application server are started.
2. Log into the browser interface as an administrator.
3. Select Environment > User Groups from the Navigation Pad.

Post-installation
4. Select the intended group, and click Navigation Pad.

5. Click the Search icon.
6. Select Enabled = No, and click Search.
7. Select the intended Monitoring items, and click Enable.
8. You can now view the selected items for the selected group in the User Interface.
Configure the Process Monitor

Overview
The Transportation Manager Process Monitor is a program that manages a configured list of processes.
It automatically starts them as defined, and optionally restarts these processes if they terminate while
the Process Monitor is still running. To run without a logged in session, configure Process Monitor as a
service on Windows systems, or run it using nohup on a UNIX system.
Usage
The DSC process automatically starts most required non-Java servers, and can be configured to start
additional servers that are not used in all installations (for example: Carrier Sequential Tendering,
Distributed Reporting, Proactive Monitoring). Therefore, use the Process Monitor only to start the DSC
and Java processes not managed by the DSC such as the TM CIS adapter (CISServer), and TP
Shipment Consolidation Adapters (RR and OPT).
The CISAgent must be configured and run as an independent service if using the Process Monitor and
running in a Windows environment. If using WebLogic on Windows to run your TM-Web interface, this
must also be configured to run as an independent service.
If running the Process Monitor on UNIX, use it in place of the start_servers.sh script. The difference is
that Process Monitor can restart any failed process, whereas start_servers.sh only restarts the
processes managed by the DSC. On UNIX, you must source the tmsrvenv.sh file using
. ./tmsrvenv.sh to initialize your environment before running the Process Monitor.
Configuration
The ProcessMonitor program (ProcessMonitor.exe on Windows) is located in the TM_HOME directory
and by default receives its runtime configuration from TM_HOME\properties\ProcMonConfig.xml
and the logging configuration from TM_HOME\properties\ProcMonLog.xml. To view valid
command line options, run ProcessMonitor /? from a command prompt.
By default, activity and error logging is sent to TM_HOME\logs. Log filenames are in the form:
ProcMon*.log
To install this program as a Windows service called Process Monitor (defaults to automatic start), run
the following from the command prompt (all on one line):
ProcessMonitor -installsvc -config ./properties/ProcMonConfig.xml -logger

./properties/ProcMonLog.xml
And, to uninstall it,
ProcessMonitor -uninstallsvc
Note: If using PC*Miler, the Process Monitor service must be configured to run as the same user that
installed PC*Miler. From the Control Panel Services applet, double-click Process Monitor, and select
the Log On tab to configure the log on user. JDA recommends that you install PC*Miler with the same
admin user that installs and runs Transportation Manager.
The Process Monitor service initializes environment variables at runtime. Therefore, do not re-install
the service if your environment variables change (for example: EXTREME_DSCPORT).

Post-installation
Note: Processes started by a Process Monitor running in service mode or on UNIX systems do not
have a command window. They must be monitored using their respective log files and the task
manager (or ps command on UNIX).
Default behavior
The Process Monitor configuration file defines a series of global defaults in the top section. In most
cases, these settings can be over-ridden in the section where individual processes are defined (if
indicated with a comment of "May be overridden by a Process -->").
Based on the default settings, processes which are managed by process manager autostart
immediately when the Process Monitor starts as a process or service. They are not started in any
particular sequence unless you specify dependencies in your process definition. If the process fails to
start or terminates unexpectedly, Process Monitor immediately attempts to restart the process. It only
attempts up to 5 times within 60 seconds to avoid tight looping in the case of a serious error that
prevents start up or continually causes a program failure. It then waits two minutes and begins the
retry cycle again.
When the Process Monitor is stopped, its child processes are terminated as well. However, this
behavior is not recommended in production, where you must use stopdsc to terminate the DSC and
its child processes, and either the CIS console or launch stopAdapter.py to terminate CIS adapters
such as the TM adapters. To stop the TP Shipment Consolidation adapters (RR and OPT), use the
launch shutdownServer.py script in the TP directory. To avoid stopping all processes when Process
Monitor is stopped, change the setting for <CloseAllProcessOnShutdown> to False.
Note: After the auto shutdown is turned off, you must stop the Process Monitor before terminating the
other processes or they keep starting up again.
Add a new managed process

See the configuration file for examples of process definitions at the end of the file. The minimum
required tags are <Process Name="MyProcess"> (where MyProcess is a unique process identifier), and
<Command>. <WorkingDir>if running the process from a location TM_HOME. All tags must be closed
with the corresponding XML tag. For example: <Command>dsc.exe
</Command> is a valid XML combination, whereas <Command>dsc.exe is not.
Note: The tag settings in the examples are not usable without being altered. The <Command> tag
parameters must include the program extension (.exe) if running on Windows. And, the <WorkingDir>
for the TP adapters must be changed to match your environment if starting these processes from the
Process Monitor. Finally, the CISServer process specifies a dependency on CISAgent, but that section
has been commented out so CISServer never starts if left this way.
Main options and features

• Specify any additional arguments to be passed to the managed process using the <Arguments>
tag. For example the DSC process can use the following to set the message logging level to info:
<Arguments>-m info</Arguments>.
• To configure a process, to start but not monitor or restart, use
<NoMonitoring>True</NoMonitoring>. This is useful if you run a batch file during startup which
terminates when completed.
• You can temporarily comment a process by changing the <Process> start and end tags to
<NoProcess>. It remains in the configuration file but is not started or monitored.
• To change the Maximum retries (default=5), the Restart (or Retry) Period (default=60 seconds),
or the wait time before restarting the cycle (default = 120 seconds), you must change the
following tags, respectively:
<MaxNumRestartAttempts>5</MaxNumRestartAttempts>
<MinRestartPeriodSec>60</MinRestartPeriodSec>

Post-installation
<RestartInactiveWaitSec>120</RestartInactiveWaitSec>
• Use the <DependsOn> tag if another managed process is required to run before the current process
starts. The Process Monitor cannot inform that the process specified by <DependsOn> has
completely initialized, but you can specify a process override tag called <WaitAfterStartSec> in
that initial process definition, which allows it to wait the intended number of seconds before
indicating it has started successfully.
• To use a different configuration file at startup, specify a different -CONFIG <filename> on your
Process Monitor command line. For example:
ProcessMonitor -CONFIG ./properties/MyProcMonConfig.xml
Similarly, use -LOGGER <filename> to specify an alternate log configuration file.
You must also do this when initializing the Windows service if you want to reference files other
than the defaults, for example:
ProcessMonitor -installsvc -config ./properties/MyProcMonConfig.xml -logger
./properties/MyProcMonLog.xml
Configure SSL transport

Transportation Manager can be configured to encrypt the network traffic that travels between server
processes (including CIS Adapters) and also traffic to the Web Application server and desktop client.
Configuration is required on the application servers, and on the clients which access them if SSL is set
to mandatory.
Usually such traffic is within a private network and does not require encryption, but this configuration
is provided where security standards mandate it.
The product is bundled with OpenSSL and the following procedure is based on that product. Use of
other products is supported, but JDA must first build a library file which statically links in the required
product files.
You can configure SSL with a self-signed certificate or with the one signed by a Certificate Authority
(CA). A self-signed certificate is usually sufficient for SSL behind the firewall between servers.
The following process assumes that you are using a self-signed certificate. Even if you order a CA-
signed certificate, if using WebLogic ensure that the Common Name field is the qualified DSC
Hostname as described later in this section.
Generate a Self-Signed certificate

1. Open a command window in the TM_HOME\SSL directory on the DSC machine for which you
want to generate the certificate.
Note: If you have multiple DSC hosts to which WebLogic, WebSphere, or Java processes need to
connect, you must repeat this process for each DSC host, and import multiple certificates into the
keystores when instructed to do so.
2. There is a command script in this directory called create-tm-cert.cmd (.sh on UNIX). If you
require a key length longer than the default (2048 bits), modify the following line with the
applicable value and save the file.
openssl genrsa -out %TMP_DIR%\tm-privkey.pem 2048
3. In this script, there is another openssl command line that sets the expiration time on the
certificate (default is -days 1095). If you want the certificate to expire in more or less than this
default three year period, change the number of days as required and save the file. Connections to
the server fail after this time period until the certificate is refreshed. It must be re-imported as
described later in this section.
4. Run the create-tm-cert script. It prompts you for multiple fields as follows:

Post-installation
Question prompt Description Default

Country Name (2 letter code) Home country of organization AU
[AU] (Australia)
State or Province Name (full Home state of organization The
name) [Some-State] text 'Some-
State'
Locality Name (for example:, City name of organization blank
city) []
Organization Name (for Company name, for example: JDA Internet
example:, company) [Internet Widgits Pty
Widgits Pty Ltd] Ltd
Organizational Unit Name ( for Description name, for example TM blank
example: section) []
Common Name ( for example: Additional information. If using blank
YOUR name) [] WebLogic, must be set to fully
qualified DSC hostname (for
example:MyDSCHost.jda.com).
Email Address [] Contact email address blank
5. Install the certificate by running the install-tm-cert.cmd script (.sh on UNIX) from the SSL
directory. No command line arguments are required. This process copies the .pem and .der files
from the temporary directory to the SSL directory.
6. Save a copy of the .pem and .der files in a secure location. In this way, you do not have to repeat
the certificate generation process if the TM server is re-installed for any reason.
Configure Transportation Manager servers for OpenSSL

1. To enable SSL on the DSC host, edit the TM_HOME\SSL\ssl-configuration.cnf file and change
enable=0 to enable=2. (JDA does not recommend setting it to 1, which allows both secure and
unsecure connections unless you need that flexibility in a test environment).
After you restart the DSC, it displays a status message indicating the SSL is enabled.
Transportation Manager does not verify certificates for communication between TM servers
processes, since they are specifically defined within the configuration, unlike WebLogic, WebSphere
and Java processes. If the enable flag is set to 2, all traffic between servers (including TM CIS
adapters) is SSL-encrypted.
Note: Any desktop clients that connect to an SSL-enabled server must also be set for SSL or the
connection is rejected. This is done using the SSL\ssl-configuration.cnf config file, the same
way you performed on the server, and setting enable=2. No certificate is required for the desktop
client.
2. To enable SSL between the TM servers and Transportation Planner, the process depends on
whether TP is configured to use a Java client (the default for 64-bit installs), or the
TMDistanceInterface DLL. This can be determined by searching the TP_HOME\sce\Setup-
RR.xml file. Search for the <DefaultDistanceEngine> tag, and search the <DllName> setting for
the default <DistanceEngineEntry>. If it is JavaDistanceInterface, it is using a Java client and
you must follow the steps described in SSL from Java clients to TM servers (on page 111).
Otherwise, it is using the TMDistanceInterface DLL, create a TP_HOME\sce\SSL directory,
copy the ssl-configuration.cnf file there, and change enable=0 to enable=2.
SSL from a WebLogic TM-Web interface to TM servers

Add the signed certificate to the trust store
1. Copy the tm-signer-cert.der file from the TM_HOME\SSL directory on the TM Server system to
a local directory, for example: C:\temp
Post-installation
2. Open a command window where the trust store file is located, for example:
C:\bea\wlserver_12.1\server\lib.
3. Run the Java keytool command to add the certificate. The following example assumes:
• java\bin for the JDK is on your PATH, and includes the keytool.exe program (keytool on
UNIX).
• The name of the key store is DemoTrust.jks.
• The key store is using the default WebLogic store password (DemoTrustKeyStorePassPhrase).
keytool -import -keystore DemoTrust.jks -file c:\temp\tm-signer-cert.der
-storepass DemoTrustKeyStorePassPhrase -alias tm
Note: If the DemoTrust.jks file does not exist, the keytool command creates one. Ensure that
you update the correct file.
4. If a certificate exists for tm, an error occurs. This certificate can be removed by running the
command above and substituting -delete for -import. You can then be able to run the import
command successfully.
Configure the WebLogic web interface for OpenSSL

1. On the WebLogic server, locate the tmgr_domain directory where you installed the
Transportation Manager web interface.
2. Edit the TM_Web_Config\config_env.cmd file (config_env.sh on UNIX), and change the setting
for DSC_SSL_MODE to ON. By default, it is set to OFF. Instead, in a non-production environment
you can set it to OPT (optional), to connect to a DSC host that is not configured for SSL.
3. Re-run the config_parm script. See Change the WebLogic configuration using TM_Web_Config
(on page 52).
Workaround for Java Strong encryption error

By default, the Sun JVM does not handle the default level of encryption that OpenSSL does and this
leads to an error, or hangs the WebLogic server when trying to connect to the DSC.
To resolve this problem, you must either change the OpenSSL encryption method, or download and
apply the Java Cryptography Extension (JCE) Unlimited Strength Policy.
Change the OpenSSL encryption method

Perform the following steps on each DSC server:
1. Stop the DSC process.

2. Edit the TM_HOME\ssl\ssl-configuration.cnf file and uncomment the last line:
ciphers=DES-CBC3-SHA
3. Save the file.
4. Restart the DSC Server
The WebLogic server now connects to the DSC.
Download Java Cryptography Extension (JCE) unlimited strength policy

To retain the OpenSSL encryption method, perform the following steps on each WebLogic server:
1. Stop the WebLogic server.

2. Open a browser and navigate to the following page:
http://java.sun.com/javase/downloads/index_jdk5.jsp

Post-installation
3. Scroll down to Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy
Files 5.0
4. Download that package and follow the instructions included.
5. Start the WebLogic server.
The WebLogic server must now connect to the SSL-enabled DSC.
Note: Ensure to apply the patch to the version of Java being used. Specifically, if using WebLogic and
the JRE supplied with WebLogic, ensure that this is the version patched.
SSL from a WebSphere TM-Web interface to TM servers

In order to use SSL on WebSphere, you must enable Global Security. Ensure this feature is active
before proceeding.
The SSL configuration contains details of the Key Stores used. These steps assume you to import the
TM certificate generated above into the default trust store. For additional information, see IBM website
(http://www.ibm.com/developerworks/websphere/techjournal/0612_birk/0612_birk.html
).
SSL configurations in WebSphere

Create or modify an SSL configuration
1. Log into WebSphere admin console as an admin user.
2. Select Security > SSL certificate and key management > Key stores and certificates >
NodeDefaultTrustStore > Signer certificates >Retrieve from port.
3. Enter the required values. Host and Port are the values for your DSC server (default DSC port is
3390).
4. Select NodeDefaultSSLSettings from the SSL Configuration for outbound connection drop-
down list. Alias is mandatory.
5. Click Retrieve signer information to request the certificate from the DSC.
6. Click OK and then Save to finish the configuration.
Configure the WebSphere TM-Web interface for OpenSSL

Modify and re-deploy the TM-Web settings for OpenSSL
1. Stop the TM-Web application and uninstall it from WebSphere as described in Remove a previous
deployment (on page 58).
2. Log off from the admin console.
3. Open a command window in the WAS_PROFILE_HOME directory where you installed the TM-Web
interface.
4. Edit the tmenv.sh file located in your WAS_PROFILE_HOME/installableApps/tm/config
directory and change DSC_SSL_MODE from OFF to ON.
5. Save the file.
6. Re-deploy the application as described in Complete the Web interface installation (on page 59).
7. Stop and restart the WebSphere Application server.
The TM-Web application must now be able connect to the SSL-enabled DSC.
Note: The default encryption selected by OpenSSL works fine on the AIX JVM. Do not apply the Java
Cryptography Extension or modify the encryption used by TM (unlike Solaris and Windows, which both
require this extra step).

Post-installation
SSL from Java clients to TM servers

A Java Client connects directly to the DSC in TM using TMOrbClient.jar. Currently, the only known
shipped tool that does this is Transportation Planner when it needs to use TM distance engine, and is
configured for the Java interface (the default configuration when using 64-bit TP).
The certificate must be placed in a trust store. You can use the default provided by every JRE, which is
located in JRE/lib/security/cacerts (default password = changeit), or create your own. The trust store
is manipulated by the Java keytool command.
Add the signed certificate to a trust store

1. Copy the tm-signer-cert.der file from the TM_HOME\SSL directory on the TM Server system to
a local directory, for example: C:\jda.
2. Open a command window in this directory.
3. Run the Java keytool command to add the certificate. The following example assumes:
• java\bin for the JDK is on your PATH, and includes the keytool.exe program (keytool on
UNIX).
• The name of the key store is tmtruststore.jks.
• The key store is using a password of tmtrustpassword.
keytool -import -keystore tmtruststore.jks -storepass tmtrustpassword
-file tm-signer-cert.der -alias tm
Note: If the tmtruststore.jks file does not exist, the keytool command creates one. Ensure to
update the correct file.
4. If a certificate exists for tm, an error occurs. This certificate can be removed by running the
command above and substituting -delete for -import. You can then run the import command
successfully.
Enable SSL for a Java client

1. Ensure that TMOrbClient.jar and TMOrbClient.properties are on your classpath (this is already
true in the default TP configuration, where they are located in TP_HOME\lib, and
TP_HOME\properties, respectively).
2. Edit TMOrbClient.properties and change tm.ssl.mode=OFF to tm.ssl.mode=ON
3. Search for the line that sets javax.net.ssl.trustStore, and change it to include the appropriate
path and key store file name, for example:
javax.net.ssl.trustStore=C:/jda/tmtruststore.jks
A password is not required as Java allows Trust Stores to be read without one (they only contain
public certificates). If you did not use keytool to create the trust store then you must specify
these other options:
javax.net.ssl.trustStore
javax.net.ssl.trustStorePassword
javax.net.ssl.trustStoreType
Note: If using the Sun JVM you must make changes in order to avoid a Java Strong Encryption error.
See Workaround for Java Strong Encryption error (on page 109).
Enable debugging
If exceptions occur in the SSL layer, you can turn on debugging to get more Java messages to help
you find the problem.
In TMOrbClient.properties, uncomment the following line:

Post-installation
javax.net.debug=ssl
You can also specify the debug parameter on the Java command line as follows:
-Djavax.net.debug=ssl
SSL and the TMgr infrastructure services adapters

When you configure the Transportation Manager servers for SSL, the Adapters launched from that
directory also communicate with the servers using SSL. You can also configure your Infrastructure
Services client to communicate using SSL. This configuration is described in detail in the JDA
Infrastructure Services 8.1 Reference Guide in a section called Configuring Transport Layer to use SSL.
The following is an example of this configuration for the APIEnterpriseBindings.xml adapter:
Note: Infrastructure Services SSL between the agent and the client is currently only supported for RMI
transports.
Configure a TM infrastructure services adapter for SSL

1. Ensure that your CIS Agent is running, and your Transportation Manager adapter is stopped.
2. Edit the TransportationManagerBindings.xml file located in the
TM_HOME\cis_config\template directory and search for the <bindings> section as follows:
<bindings>

<RMI type="TransportationManager" default="RMI_DEFAULT">
3. Insert the following code after the RMI type line. Substitute your correct CIS_HOME path if it is not
C:\JDA\CIS\8.1\cis-sdk
<SSL mode="true">
<debug>true</debug>
<protocol>SSL</protocol>
<keyStore>C:\JDA\CIS\8.1\cis-sdk\conf\ssl\server.private</keyStore>
<trustStore>C:\JDA\CIS\8.1\cis-sdk\conf\ssl\client.public</trustStore>
<keyStorePassword>serverpw</keyStorePassword>
<trustStorePassword>public</trustStorePassword>
<useSunJSSE>true</useSunJSSE>
</SSL>
4. Save the file.
5. Re-run your cis_config step from the Transportation Manager cis_config directory, for example:
cis_config_parm <instance ID> RMI
6. Ensure that your DSC is running, and start up the adapter, for example using the CISServer
program.
7. The standard testCIS script file provided in the Transportation Manager tools directory does not
work with CIS SSL turned on. You must use the cisSendEx.py function as in the following
example (run from the TM_HOME\tools directory):
%CIS_HOME%\bin\launch %CIS_HOME%\bin\cisSendEx.py TransportationManager
queryTMEntityID CISRetrieveEquipType.xml user=VENTURE password=VENTURE
useSunJSSE=true
The last parameter (useSunJSSE=true) is required on all platforms.

Post-installation
Configure TP on Windows
This section provides details about configuring the third-party and TP applications after installation.
WebLogic
The installation process performs most of the configuration of TP with WebLogic. Custom configuration
is required in the following cases:
• If you use a port for JDA Infrastructure Services (CIS) other than the default of 5015, add the CIS
/properties path to the CLASSPATH in the startWebLogic.cmd file. For detailed information, see
"Configure WebLogic CLASSPATH information for CIS port" (on page 113).
• If your WebLogic domain is in Production mode, deploy the applications from the WebLogic
console. For detailed information, see "Deploy JDA Applications in Production Mode" (on page
113).
Configure WebLogic CLASSPATH information for CIS port

To use a port for CIS other than the default of 5015, add the CIS \properties folder to the
CLASSPATH in the startWebLogic.cmd file.
Note: Create a copy of the startWebLogic.cmd file before editing this file.
1. Edit the startWebLogic.cmd file located in the \bin folder of your WebLogic domain.
2. Verify the following information is included in the definition of the CLASSPATH:
• <cis_path>\properties;
where:
• <cis_path> is the folder in which CIS (Infrastructure Services) is installed (typically
c:\JDA\cis\cis-sdk\8.1).
Note: The CLASSPATH may include other information in addition to that required for the CIS port
configuration. For example, if you are also deploying the TP web interface in the same domain, the
CLASSPATH includes information such as:
C:\JDA\tp\8.1\properties;C:\JDA\tp\8.1\lib\TmUtils.jar;C:\JDA\CIS\8.1\cis-
sdk\lib\xercesImpl.jar;C:\JDA\CIS\8.1\cis-sdk\lib\jdom.jar
Deploy JDA applications in Development mode

If your WebLogic domain is in Development mode, the applications will be automatically deployed if
the application file (tpui.war) is located in the \autodeploy folder in your WebLogic domain. Copy the
war files from their installed locations to the \autodeploy folder. The tpui.war files are installed in the
\lib folder (c:\JDA\tp\8.1\lib).
For the TP Help, use the following procedure:
1. Navigate to the \documentation folder under your TP installation folder (c:\JDA\tp\8.1).

2. Copy the contents (all folders and files) to the \lib\i2DocLibrary folder under your TP
installation folder (c:\JDA\tp\8.1).
3. Copy \i2DocLibrary and all its contents to the \autodeploy folder of your WebLogic domain.
Deploy JDA applications in Production mode

If your WebLogic domain is in Production mode, use the WebLogic administrative console to deploy
JDA applications.
Set up the TP help for deployment

The TP Help is set up as a library of documents and help systems.
Post-installation
1. Navigate to the \documentation folder under your TP installation folder (c:\JDA\tp\8.1).

installation folder (c:\JDA\tp\8.1)
3. Follow the instructions provided in "Deploy applications from the WebLogic console" (on page 114)
to deploy the help in the JDA Documentation Library.
Deploy applications from the WebLogic console

Note: Deploy each application separately. Perform this task for each application you want to deploy.
2. Open the WebLogic Console in a browser window and log in. The URL is
http://<server>:<port>/console
where
• <server> is the WebLogic server name and
• <port> is the WebLogic port.
3. Click Lock & Edit in the left pane.
4. Click Deployments for your domain in the Domain Structure section of the navigation tree.
5. Click Install. The Install Application Assistant page is displayed.
6. Browse to the location of the Web Application (tpui.war) typically c:\JDA\tp\8.1\lib.
Caution: When deploying in Production mode, the application files, such as tpui.war,
cannot be deployed from the \autodeploy folder in your WebLogic domain.
7. Select the application, or in the case of the Transportation Planner help, select the \i2DocLibrary
folder, and then click Next. The Choose targeting style page is displayed.
8. Accept the default (Install this deployment as an application) and click Next. The Optional settings
page is displayed.
9. Accept the defaults and click Finish. Messages regarding the deployment are displayed. If the
deployment was successful, the application will be listed in the Deployment table with a state of
"New".
10. When all the applications are installed, click Activate Changes in the left pane. The applications
will now have a state of "Prepared".
11. Select the application names in the Deployments table, click Start and select Servicing all
requests.
12. Click Yes to confirm the deployment start. The applications will be listed in the Deployment table
with a state of "Active"
For the TP and Shipment Scheduler interfaces, the WebLogic config.xml is updated with the
application entries as defined below.
Note: Text in bold is not included in the config.xml; this text is informational in this document
only. The Path value will reflect your WebLogic deployment.
<app-deployment>
<name>tpui</name>
<target>AdminServer</target>
<module-type>war</module-type>
<source-path>C:\JDA\tp\8.1\lib\tpui.war</source-path>

Post-installation
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
Configure TP on Solaris
This section provides details about configuring the third-party and Transportation Planner applications
after you have installed them. In addition, this section provides details about creating or updating
database schemas for use with Logistics Tariff Manager.
Configure TP with WebLogic on Solaris

The installation process performs most of the configuration of TP with WebLogic. Custom configuration
is required in the following cases:
• If you use a port for JDA Infrastructure Services (CIS) other than the default of 5015, add the CIS
/properties path to the CLASSPATH in the startWebLogic.sh file. For detailed information, see
"Configure WebLogic CLASSPATH information for CIS Port" (on page 115).
• If your WebLogic domain is in Production mode, deploy the applications from the WebLogic
console. For detailed information, see "Deploy JDA Applications in Production Mode" (on page
116).
Configure WebLogic CLASSPATH information for CIS port

To use a port for CIS other than the default of 5015, add the CIS /properties folder to the CLASSPATH
in the startWebLogic.sh file.
To configure the WebLogic CLASSPATH

Note: Create a copy of the startWebLogic.sh file before performing any edits on this file.
1. Edit the startWebLogic.sh file located in the \bin folder of your WebLogic domain.
2. Verify the following information is included in the definition of the CLASSPATH:
• <cis_path>/properties;
where:
• <cis_path> is the folder in which CIS (Infrastructure Services) is installed (typically
/opt/jda/8.1/cis/cis-sdk/).
Note: The CLASSPATH may include other information in addition to that required for the CIS port
configuration. For example, if you are also deploying the TP web interface in the same domain, the
CLASSPATH will include information such as:
/opt/jda/tp/8.1/properties;/opt/jda/tp/8.1/lib/TmUtils.jar;/opt/jda/CIS/8.1/cis-
sdk/lib/xercesImpl.jar;
/opt/jda/CIS/8.1/cis-sdk/lib/jdom.jar
Deploy JDA Applications in Development Mode

If your WebLogic domain is in Development mode, the applications will be automatically deployed if
the application files (tpui.war) are located in the
/autodeploy folder in your WebLogic domain. Copy the war files from their installed locations to the
\autodeploy folder. The tpui.war file is installed in the \lib folder (/opt/jda/tp/8.1/lib).
For the TP Help, use the following procedure:
1. Navigate to the /documentation folder under your TP installation folder (/opt/jda/tp/8.1).

installation folder (/opt/jda/tp/8.1).
Post-installation
3. Copy /i2DocLibrary and all its contents to the /autodeploy folder of your WebLogic domain.
Deploy JDA Applications in Production Mode

If your WebLogic domain is in Production mode, use the WebLogic administrative console to deploy
JDA applications.
Set up the TP help for deployment

The TP Help is set up as a library of documents and help systems.
1. Navigate to the /documentation folder under your TP installation folder (typically

/opt/jda/tp/8.1).
2. Copy the contents (all folders and files) to the /lib/i2DocLibrary folder under your TP
installation folder (/opt/jda/tp/8.1).
3. Follow the instructions provided in "Deploy applications from the WebLogic console" (on page 116)
to deploy the help in the JDA Documentation Library.
Deploy applications from the WebLogic console

2. Open the WebLogic Console in a browser window and log in. The URL is
http://<server>:<port>/console
where
• <server> is the WebLogic server name and
• <port> is the WebLogic port.
3. Click Lock & Edit in the left pane.
4. Click Deployments for your domain in the Domain Structure section of the navigation tree.
5. Click Install. The Install Application Assistant page is displayed.
6. Browse to the location of the Web Application (tpui.war).
Caution: When deploying in Production mode, the application files, such as tpui.war, cannot be
deployed from the \autodeploy folder in your WebLogic domain.
7. Select the application, or in the case of the TP help, select the \i2DocLibrary folder, and then click
Next. The "Choose targeting style" page is displayed.
8. Accept the default ("Install this deployment as an application) and click Next. The "Optional
settings" page is displayed.
9. Accept the defaults and click Finish. Messages regarding the deployment are displayed. If the
deployment was successful, the application will be listed in the Deployment table with a State of
"New".
10. When all the applications are installed, click Activate Changes in the left pane. The applications
will now have a State of "Prepared".
11. Select the application names in the Deployments table, click Start and select Servicing all
requests.
12. Click Yes to confirm the deployment start. The applications will be listed in the Deployment table
with a State of "Active"
The WebLogic config.xml is updated with the application entries as defined below.
Note: Text in bold is not included in the config.xml; this text is informational in this document
only. The Path value will reflect your WebLogic deployment.
Post-installation
<app-deployment>
<name>tpui</name>
<target>AdminServer</target>
<module-type>war</module-type>
<source-path>/opt/jda/tp/8.1/lib/tpui.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
Configure TP on AIX
This section provides details about configuring the third-party and Transportation Planner applications
after you have installed them. In addition, this section provides details about how to create or update
database schemas for use with Logistics Tariff Manager.
Configure WebSphere with TP components

You deploy TP or Shipment Scheduler once you have successfully completed TP installation as
described in "Run the TP installation program on AIX" (on page 82).
Note: Although these procedures can be used for both Web modules and Enterprise Java beans (EJB)
modules, they specifically apply to Web modules. Other details involving EJB modules are not included.
The WebSphere installation directory is referred to as $WAS_HOME. For example, $WAS_HOME may be
/opt/WebSphere/AdvancedEdition.
Web applications can be created or installed in WebSphere using different methods, like using the
WebSphere Administrative Console or using the WSCP and XMLconfig utilities. These utilities can be
found in the $WAS_HOME/bin folder. The procedure described here uses the WebSphere
Administrative Console.
Deploy TP components on WebSphere

You can install the TP interface and the Shipment Scheduler interface as WebSphere applications. In
each case, you must configure the Application Server, install the component as a new application, then
start the component as an enterprise application. You can also install the Documentation Library as an
application.
Configure the application server for use with TP

1. Ensure the WebSphere Administration Server has already been started.
2. Log in to the WebSphere Administrative Console.
3. Expand the Servers node and click Application Servers.
4. Click server1. The server1 application server page is displayed.
5. Select the Configuration tab.
6. Expand the Java and Process Management node and click Process Definition.
7. Click Java Virtual Machine.
8. Add the following information to the Generic JVM arguments. Ensure to prepend this to information
already in the field and separate it from other arguments with a space:
-Djava.security.auth.login.config=/<tp path>/properties/cis_jaas.conf
where:
Post-installation
• <tp path> is the folder in which TP is installed (/opt/tp/8.1)

If TM is installed on same WebSphere profile, then update the classpath. Add the following
information to the Classpath section on the same page:
/<CIS_HOME>/lib/jdom.jar
/<CIS_HOME>/lib/jsse.jar
where:
• <CIS_HOME> is the folder in which CIS is installed (typically /opt/cis/8.1/cis-sdk)
9. Click OK. The changes are saved to the Server configuration.
Install TP as a new application

1. Expand the Applications node and click Install New Applications. The path to the new
application page is displayed.
2. Select Remote file system and enter the path to the tpui.war file
(/opt/tp/8.1/lib/tpui.war).
3. Enter /tpui for the Context root and click Next. The default bindings and mappings page is
displayed.
4. Click Next. The Application Security Warnings page is displayed.
5. Click Continue. The Select installation options page is displayed.
6. Enter Transportation Planner as the application name and click Next. The Map modules to
servers page is displayed.
7. Select Transportation Planner and click Next. The Map virtual hosts for Web modules page is
displayed.
8. Select Transportation Planner as the web module and leave the Virtual Host value as
default_host and click Next. The Summary page is displayed.
9. Click Finish. When the deployment is successful, a status page is displayed. It contains the
message "Application Transportation Planner installed successfully".
10. Click Save to Master Configuration. The Save page is displayed, with a summary of changed
documents.
11. Click Save.
Note: There are additional application-specific configuration changes described in "Start TP as an
enterprise Application" (on page 119).
Install the documentation library as a new application

1. You must copy the i2DocLibrary.war file from the TP install media to your computer.
2. Expand the Applications node and click Install New Applications. The Path to the new
application page is displayed.
3. Select Remote file system and browse to the i2DocLibrary.war file you copied to your
computer.
4. Enter / for the Context root and click Next. The default bindings and mappings page.
5. Click Next. The Application Security Warnings page is displayed.
6. Click Continue. The Select installation options page is displayed.
7. Click Next. The Map modules to servers page is displayed.
8. Select the i2DocLibrary.war module and click Next. The Map virtual hosts for Web modules page
is displayed.
Post-installation
9. Select the .war files, leaving the Virtual Host value as default_host and click Next. The
Summary page is displayed.
10. Click Finish. When the deployment is successful, a status page is displayed. It contains the
message "Application i2DocLibrary installed successfully".
11. Click Save to Master Configuration. The Save page is displayed, with a summary of changed
documents.
12. Click Save.
Start TP as an enterprise application

1. Expand the Applications node and click Enterprise Applications. The Enterprise Applications page
is displayed. TP is listed as one of the applications.
2. Select Transportation Planner and click Start. Transportation Planner is started and a success
message is displayed at the top of the page.
3. Log out of the WebSphere Administrative Console.
4. Restart the WebSphere Server. The server will now include the TP deployment.
Configure Transportation Manager Mobile

This section describes the post-installation steps to be performed for the TM Mobile installation.
Additional post-installation steps

1. Copy %CIS_HOME%/properties/cisauth.xml to %ABPP_INSTALL_DIR
%/web/base/WEB-INF/classes.
2. Copy %CIS_HOME%/properties/cisjaas.xml to
%ABPP_INSTALL_DIR%/web/base/WEB-INF/classes.
3. Edit the ABPP WSDL to point to the correct location for web services. Open
%TM_MOBILE_ABPP_DIR%\wsdl\i2\TransportationManagerService.wsdl.
• Find <service name="TransportationManagerService">
• Edit the soap address location to match the CIS adapter location:
<soap:address
location="http://server:cisport/webservices/services/TransportationManager"/>
• Edit the CIS address binding to match the server instance name:
<cisWsdl:address instance="server" portType="TransportationManager" />
4. Edit %TM_MOBILE_ABPP_DIR%\cfg\xservice\tmgr_security\rules\uiSecurity.xml:
<PORTTYPE name="TransportationManager" instance="server"/>
TM Mobile server configuration

The following servers are required by the installation:
• ABPP
• TrackAndTrace service
• Oracle WebLogic
• TM
• DSC
• CIS Adapter

Post-installation
• TMGR domain WebLogic

• CIS
• CIS
• SSO
• TransportationManager
• webSessionCoordinator
Transportation Manager System configuration

Set CIS to ignore time zone information on dates
1. Select Server Configuration > TM Hosts -> Parameter Sets from the TM web UI.
2. Open the CIS Parmset.
3. Set ignoreTimeZonesOnDates value to Y.
4. Restart the CIS Adapter.
Run the JDA Transportation Manager ABPP application

Prerequisites
• The JDA Transportation Manager ABPP application package must be successfully deployed into the
Oracle WebLogic domain.
• The Oracle database schema must be created and initialized with the JDA ABPP system tables and
any required data uploaded for the application.
• JDA Transportation Manager is running and the JDA Transportation Manager CIS adapter is
registered with the CIS Agent using the CIS Instance ID specified in the deployment phase.
Run the application

Start the WebLogic application server
1. Go to the Oracle WebLogic Domain that was provided during the deployment, from the Windows
Start menu. For example,
Start > Programs > Oracle WebLogic > User Projects > %TM_ABPP domain% > Start
Admin Server for WebLogic Server Domain where %TM_ABPP domain% is the name of the
WebLogic domain provided to the Deployer application.
2. After the server has started, the console output displays the progress. As the ABPP application
comes online, the startup of each ABPP Service is logged to the console.
If the Oracle WebLogic domain is created using the default properties, the listen-port is assigned
the value of 7001, which is typically used by the JDA Transportation Manager Web UI.
This value can be updated in the config.xml file in the config directory of the Domain Home
directory (that is, D:\bea\user_projects\domains\cea_domain\config).
Modify the following block of text in config.xml to update the value for the listen-port:
<server>
<name>AdminServer</name>
<listen-port>7005</listen-port>
<listen-address/>
</server>

Post-installation
The Weblogic server console reports that it is running when the application is started. The ABPP
Application is ready to accept requests.
Start the WebSphere application server

Navigate to $WAS_PROFILE_HOME/bin and start the WebSphere application server using
./startServer.sh server1.
Note: $WAS_PROFILE_HOME refers to your WebSphere profile home; for example,

/data/softwares/WebSphere/AppServer79/profiles/AppSrv02
Connect to the ABPP web application

1. Open a Microsoft Internet Explorer session to connect to the JDA ABPP web application. The URL is
in the following form:
http://host.domain:tmabpp_port/base/home
where host.domain is the fully qualified hostname where the Weblogic application server is
running and tmabpp_port is the listen-port value described in the previous step. For example:
http://tmabpphost.JDA.com:7005/base/home
A login screen is displayed.
2. Enter valid JDA Transportation Manager user credentials and click Log In. A dialog box is
displayed with a navigation pane that indicates installation and deployment of the JDA
Transportation Manager ABPP application is successful.
3. Configure JDA Transportation Manager to complete the UI integration between the two
applications. See the installation guide for the JDA Transportation Manager ABPP application for
details on the configuration requirements.
4. Configure both applications as Single Sign On to complete the integration between JDA
Transportation Manager ABPP and JDA Transportation Manager. See the JDA Transportation
Manager Single Sign On Guide for details.
Logging from the ABPP applications

All of the logging configuration for each TM/ABPP application is located in the following file:
<%ABPP_WEB_INSTALL%>/web/base/WEB-INF/classes/log4j2.xml
All output is written by default to a single file, abpp.log, under the profile(for example, tm1,tm2)
located at the root of the domain for WebLogic.
1. To change logging levels for the Xserver, uncomment and modify the following section, changing
the level as necessary:
<logger name="com.jda.abpp.xserver" level="warn" additivity="false">
<appender-ref ref="Default"/>
</logger>
2. Specific services logging can be modified in the following manner:
<logger name="com.jda.abpp.service.TMGRX" level="debug" additivity="false">
<appender-ref ref="Default"/>
</logger>
Where TMGRX is a specific ABPP Service.

Post-installation
Approval Chain
Post-installation steps
This section describes the post-installation steps to be performed for Approval Chain.
Directory locations
The following table lists references to the application installations, and their locations that are used
during configuration.
Reference Name Location

%JAVA_HOME% The directory where the JDK is installed;
for example, C:\jdk1.7
%CIS_HOME% The cis-sdk directory of the JDA Infrastructure

Services Installation;
for example, C:\jda\CIS\8.1\cis-sdk
%TM _INSTALL% The directory in which Transportation Manager

has been installed.
for example, C:\jda\tmgr\8.1
%TM_ABPP_INSTALL% The directory where Transportation Manager
ABPP has been deployed
%ABPP_WEB_INSTALL The directory where the ABPP Web application

% has been deployed. This is the same as the
%TM_ABPP_INSTALL% location if the
defaults were selected during the deployment
phase.
Configure different tablespace

1. Edit SchemaConfig.xml in the <%ABPP_WEB_INSTALL%>/additional/ApprovalChain/db
folder.
Replace the default tablespace names with the appropriate entries.
<PHYSICAL_SCHEMA_DEFINITION>
<DEFAULT_TABLE_SPACE Name="jdatm_AC_data"/>
<DEFAULT_INDEX_SPACE Name="jdatm_AC_index"/>
</PHYSICAL_SCHEMA_DEFINITION>
2. Run genSchema.bat (genSchema.sh for UNIX) located in <%ABPP_WEB_INSTALL%>/bin to
generate schema.
3. Run uploadData.bat (uploadData.sh for UNIX) located in <%ABPP_WEB_INSTALL%>/bin to
upload the static data.
Configuration steps
The deployer assumes you have CIS installed. Ensure that the cistransport.properties file exists
and that cisregistry.properties points to the correct CIS instance (where the Transportation
Manager CIS agent is running).

Post-installation
Copy cisregistry.properties to <ABPP_DEPLOY>/web/base/WEB-INF/classes (For

WebSphere: $WAS_PROFILE_HOME/installedApps/<node cell>/base.ear/base.war/WEB-
INF/classes)
Additional post-installation steps

1. Update the Transportation Manager wsdl file to point to your Transportation Manager Services.
Note: Replace <hostname> and <port> with appropriate values.
<ABPP_DEPLOY>\wsdl\i2\TransportationManagerService.wsdl
<service name="TransportationManagerService">
<port name="TransportationManagerPort"
binding="cis:TransportationManagerSoapBinding">
<soap:address
location="http://<hostname>:<port>/webservices/services/TransportationManager" />
</port>
<port name="TransportationManagerCISPort"
binding="cis:TransportationManagerCISBinding">
<cisWsdl:address instance="<CISInstanceID>" portType="TransportationManager"
/>
</port>
</service>
2. Configure XServer for CIS.
Server initialized CIS calls need to have back end credentials, since the server does not have
access to the UI Session.
The following has to be edited with appropriate values of CISInstanceID, username, and password
to allow server-side CIS calls.
<cis-client-config>
<property Key="TransportationManager.CISInstanceID.USER"
Value="username"/>
<property Key="TransportationManager.CISInstanceID.PASSWORD"
Value="password"/>
</cis-client-config>
3. Update the uiUserSecurity rule to initialize the CIS connection using your CIS Server.
<ABPP_DEPLOY>\cfg\xservice\tmgr_security\rules
update uiUserSecurity.xml
<DEFINE_METHOD Name="onValidatedLogin">
<API_DOC>
<INPUT>
<REQUEST Name="onValidatedLogin">
<LOGIN_NAME Value="..." />
<PASSWORD Value="..." Optional="true" />
<SSO_TOKEN Value="..." Optional="true" />
</REQUEST>
</INPUT>
Post-installation
<OUTPUT>
<ON_SUCCESS>
<RESPONSE />
</ON_SUCCESS>
</OUTPUT>
</API_DOC>
<RULE>
<ACTION>
<INITIALIZE_CIS_CONNECTIONS>
<AUTHORIZATION_CONTEXT>
<USER_ID Value="{$thisParam/LOGIN_NAME/@Value}" />
<PASSWORD Value="{$thisParam/PASSWORD/@Value}" />
<AUTHORIZATION_ID Value="{$thisParam/SSO_TOKEN/@Value}" />
</AUTHORIZATION_CONTEXT>
<PORTTYPES>
<PORTTYPE name="TransportationManager" instance="CISInstanceID" />
</PORTTYPES>
</INITIALIZE_CIS_CONNECTIONS>
</ACTION>
</RULE>
</DEFINE_METHOD>
4. Update the x2.properties file as shown below. This file is located at
<%ABPP_WEB_INSTALL%>\additional\ApprovalChain\web\base\WEB-INF\classes
folder:
• com.i2.x2.util.configurability.uploadPath=/
• com.i2.x2.util.configurability.uploadPathType=relative
• com.i2.x2.util.configurability.maximumUploadSize=10
For WebSphere: The x2.properties file is located at
$WAS_PROFILE_HOME/installedApps/<node cell>/base.ear/base.war/WEB-
INF/classes
5. Copy the folder tmgrxui from
<%ABPP_WEB_INSTALL%>\additional\ApprovalChain\web\base to
<%ABPP_WEB_INSTALL%>\web\base.
For WebSphere: $WAS_PROFILE_HOME/installedApps/<node cell>/base.ear/base.war
6. Copy the contents of the i18n text messages from
<ABPP_DEPLOY>\additional\ApprovalChain\web\base\WEB-
INF\classes\ApprovalChain_i18n.txt
These messages in the source file will replace the contents of the following files:
• <ABPP_DEPLOY>\web\base\WEB-INF\classes\i18n-messages.properties (for
WebSphere: $WAS_PROFILE_HOME/installedApps/<node
cell>/base.ear/base.war/WEB-INF/classes/i18nmessages.properties)

Post-installation
• <ABPP_DEPLOY>\web\base\WEB-INF\classes\i18n-messages_en.properties (for
cell>/base.ear/base.war/WEB-INF/classes/i18nmessages_en.properties)
7. Create a folder by name “userhelp” under the <%ABPP_WEB_INSTALL%>\web\base\core
folder and copy the Employee (TMgr_Approval_Chain_Employee_User_Guide_8.1.pdf ) and Carrier
( TMgr_Approval_Chain_Carrier_User_Guide_8.1.pdf ) user guides from installation package to this
folder.
For WebSphere: $WAS_PROFILE_HOME/installedApps/<node
cell>/base.ear/base.war/core
8. Update UI Security to allow API access to Voucher Charges:
Edit <TMGR_INSTALL_DIR>/METADATA/UI/FunctionalSecurity.xml
Change: <tmsecurity:functional2 entity="VoucherChargeType" operation="findEntities"
/>
To: <tmsecurity:functional2 entity="VoucherChargeType" operation="findEntities"
employee="true" />
9. Configure the Messaging Service to support the email functionality
a. Update the following line in <ABPP_DEPLOY>\cfg\properties\custom-email.xml to point
to address of the SMTP Email server
<service-params>
<param Name="om.smtpHost" Value="mailout.jda.com" />
The default email address is supplied in the TM_ApprovalChain service configuration.
b. Make the Messaging i18n resource files available on the Classpath:
Copy the email i18n resource file from
<ABPP_DEPLOY>\additional\ApprovalChain\messaging
acMessageResources.properties
acMessageResources_en_US.properties
acMessageResources_en_CA.properties
to
<ABPP_DEPLOY>/web/base/WEB-INF/classes (for WebSphere:
INF/classes)
10. To support email distributions when a message event is raised by a Division or Logistics Group
Restricted User, modify the meta-data file User.xml:
a. Edit the <TMGR_INSTALL_DIR>/METADATA/BusinessEntities/User.xml file.
b. Remove the Division / Logistics Group Security (this can be commented out or physically
removed) based on the following:
<?xml version = "1.0" encoding = "UTF-8"?>
<definitions xmlns = "http://www.jda.com/cis"
xmlns:tm="http://www.jda.com/tm"
xmlns:tmsecurity="http://www.jda.com/tmsecurity"
xmlns:tmdoc="http://www.jda.com/tmdoc"
xmlns:tmhistory="http://www.jda.com/tmhistory">
<types>
Post-installation


<type javaPrefix = "Seg" name = "UserType" javaPackage = "com.i2.tmgr.beans">
<documentation>
A person who is using this system. Mandatory field.
</documentation>
<tm:entity.persistence>
<tm:table name="usr_t" alias="U">
<tm:key member="userCode"/>
</tm:table>
</tm:entity.persistence>



<member name = "id" type = "IDType" use = "optional">

<tmdoc:required r="F" c="X" u="X" />
<documentation>
Internal ID. Applicable only for UI-oriented APIs.
</documentation>
</member>
11. Create a "Stop Weblogic Server" entry in the Approval Chain Program Group
When deploying an ABPP application, a new Program Group is created with 'Start Weblogic Server'
and 'uninstall' entries, but no "Stop Weblogic Server" entry.
Create a 'Stop Weblogic Server' entry and link it to the stopWebLogic.cmd file found in the bin
folder of the WebLogic Domain specified during the Approval Chain Application deployment (that is,
D:\bea\user_projects\domains\ApprovalChain\bin\stopWebLogic.cmd).
12. Perform the following additional configuration steps that are required only for WebSphere on AIX:
a. Login to the WebSphere admin console.
b. Select Applications > Application Types > WebSphere enterprise applications . The
Enterprise Applications page is displayed.
c. Click <WebApp>. For example, Click base.
d. Click Manage Modules in the Modules section of the Configuration tab. The Manage
Modules page is displayed.
e. Click BPE Web UI. The Deployment-specific information for Web module page is displayed.
f. Select Classes loaded with parent class loader first from the Class loader order drop
down list in the General Properties section.
g. Click Apply.
h. Click Save.
i. Log out of the admin console and stop the WebSphere profile server.
j. Clean the contents for temp, wstemp, and log files folders and restart the WebSphere profile
server.
Post-installation
Approval Chain Service Configuration

Note: These params must be set in both the xserver_ac.xml and tm_approvalchain.xml property
files.
• <param Name="wildCardCharacter" Value="%" />
A constant - do not modify.
• <param Name="spUserGuideName" Value="TMgr_Approval_Chain_User_Guide_8.1.pdf" />
<param Name="spCarrierGuideName" Value="TMgr_Approval_Chain_User_Guide_8.1.pdf" />
• <param Name="spBillingProposalSearchFrequency" Value="1" />
<param Name="spCostAdjustmentSearchFrequency" Value="1" />
These values define how often the Batch Processes look for new Approval Documents to extract
from Transportation Manager.
It is measured in minutes.
• <param Name="spDefaultApprover" Value="VENTURE" />
When an Approval Document is submitted, if no approver groups, an Approval Alert is created for
the DefaultApprover. This must be a valid Transportation Manager user with Manager Authorization
for Freight Audit.
• <param Name="spSystemUser" Value="<system user name>" />
System User. Can be the same as the API user specified in the CIS-CLIENT-CONFIG.
This must be a valid Transportation Manager user with Manager Authorization for Freight Audit.
Note: Replace <system user name> with the appropriate value.
• <param Name="spEmailFromAddress" Value="fromaddress@yourcompany.com" />
Email address passed with Approval e-mails as the From Address.
• <param Name="spBatchProcessFetchSize" Value="30" />
<param Name="spMaxFetchSize" Value="2000" />
These parameters affect the behavior of the batch processes.
• spMaxFetchSize: Controls the number of Freight Bill or Charge Detail IDs matching the
Approval Chain criteria to read in at once.
• spBatchProcessFetchSize: Controls the number of entities to read from TM at one time.
These parameters should only be modified to address performance issues.
• <param Name="spBatchProcessShutdown" Value="false" />
Flag used to trigger the shutdown of the batch processes.
Must remain as false; otherwise, the batch process will not start.
Transportation Manager system configuration

1. Set the ignoreTimeZonesOnDates CIS Parameter to Y
a. Select Server Configuration > TM Hosts > Parameter Sets from the TM web UI.
b. Open the CIS Parmset.
c. Set ignoreTimeZonesOnDates value to Y.
d. Restart the CIS Adapter.

Post-installation
The following additional steps may be required depending on your implementation.
1. Activate the Cost Adjustment document type for the Approval Chain Document Types Domain
Table.
2. Create a ReferenceNumberType and Qualifier for the Billing Proposal Status.
This can be set up using the Web UI: System Settings > Miscellaneous > Reference Number
Types.
VAL_CD VAL_DESC
BPS Billing Proposal

Approval Status
a. Specify Reference Number Qualifiers and Categories:

i. Add a new row to the Reference Number Qualifiers table and add a corresponding row in
the Reference Number Categories table for the qualifier.
This can be set up using the Web UI: System Settings > Miscellaneous > Reference
Number Qualifier.
• Reference Number Type: BPS
• Qualifier Entity Type: Carrier
• Qualifier Entity ID: Null
• Supported Level: Freight Bill (This creates a row in the Reference Number Categories
table)
• Generation Source: Manual - Free Format
3. Configure Screen Element Version Operations:
List of Freight Bills (FN_FREIGHT_BILL_LIST_)
a. Deactivate the following operations at System level:
• HOLD_
• RELEASE_
• CANCEL_FREIGHT_BILL_
• DUPLICATE_
• NEW_
• RESUME_CREATE_
b. Set the View Mode Only flag on the Screen Element Version Operation Properties page to
True at the System level for the following operations:
• PROPERTIES_
• FREIGHT_BILL_DETAILS_
• REFERENCE_NUMBERS_
i. For the various Lists that support the Freight Bill Details operation:
Set the View Mode Only flag on the Screen Element Version Operation Properties page to
True at the System level for the FREIGHT_BILL_DETAILS_ operation that can be accessed
from the following lists.
Use Environment > UI Customization > Screen Element > Operations and filter with
Screen Element Version Operation ID = 'FREIGHT_BILL_DETAILS_' to access a list
containing all of the applicable rows:

Post-installation
• FN_AP_TRANSACTION_LIST_
• FN_ENTITY_FREIGHT_BILL_LIST_
• FN_FREIGHT_BILL_LIST_ (repeated from above)
• FN_LOAD_LIST_
• FN_NON_OP_FREIGHT_LIST_
• FN_TRIP_LIST_
• FN_TRIP_LOAD_LIST_
ii. List of A/P Voucher Charges (FN_AP_VOUCHER_CHARGE_LIST_)
Deactivate the following operations at the System level:
• DELETE_
Set up this operation to invoke ABPP Approval Chain pages:
• Approval Details: Point to the ABPP TMAC_ApprovalDetails workflow for a selected
Charge Detail ID.
4. Set up Module Contents in the Navigation Pad for Carrier Type and Employee Type users to access
ABPP Carrier Approvals module contents.
(See Integration With Transportation Manager in the Transportation Manager Approval Chain
Employee User Guide for detailed information.)
5. Set up Freight Bill Versions with the following parameters to use theBilling Proposal Approval
workflow:
• Logistics Group: As required
• Carriers / Exclude Carriers: As required
• Freight Bill Payment Mode: As required
• Include Vouchers (3 flags): As required
• Hold Freight Bill Upon Creation (for Freight Bill Versions used to generate Freight
Bills for carriers that will approve Billing Proposals): True
• Ignore Customer IDs for Operational Vouchers: True
• Freight Bill Confirmation Mode: Confirmation Optional
6. Set up users authorized to use Approval Chain with the following features:
• Align Country and Language with locale assignment in ABPP
• Authorized to Audit Freight (for any user authorized to approve an approval chain document)
Manager
Note: Default System user and API User must also have Manager level.
• Send Email for Alerts based on the user preference
7. Set up carriers with these feature for the Billing Proposal Approval workflow:
• Freight Bill Payment Mode: Auto-Pay
• Maximum Pay Variances: All four values should be zero
• Freight Bill Group Level: One for All Vouchers
8. If rows are created in this table (required for NOFs), the Unmatched Freight Bill Authorization
should never be set to "Always". Using the Transportation Manager Web UI, you can access the
data in this table by selecting System Entities > Customers > Carrier Freight Authorization
operation; or System Entities > Carriers > Customer Freight Authorization operation.

Post-installation
9. Set up Transaction Management with the following defaults for the Billing Proposal Approval
workflow:
• Apply Voucher Adjustments to Auto Pay Freight Bills: True
(Environment > Global Settings > Transaction Management > Financial 2 tab)
• Maximum Pay Variances: All four values should be zero
(Environment > Global Settings > Transaction Management > Financial 1 tab)
Freight Auction
This section describes the post-installation steps to be performed for Freight Auction 8.1.
Directory locations
The following section lists application installations used during configuration and their locations:
• %JAVA_HOME%: Directory where the jdk is installed.

For example: C:\jdk1.7
• %CIS_HOME%: Directory where JDA Infrastructure Services is installed.
For example: C:\jda\CIS\8.1\cis-sdk
• %TM _INSTALL%: Directory where JDA Transportation Manager is installed.
For example: C:\jda\tmgr\8.1
• %TM_ABPP_INSTALL%: Directory where TM ABPP is deployed.
• %ABPP_WEB_INSTALL%: Directory where the ABPP web application is deployed. This is the
same as the %TM_ABPP_INSTALL% location, if the defaults are selected in the deployment
phase.
Configuration steps
1. WSDL Configuration for CIS instance:
Edit <%ABPP_WEB_INSTALL%>/wsdl/i2/ TransportationManagerService.wsdl to point
to the appropriate CIS instance according to the deployment.
<soap:address location="http://<CIS_Agent_HostName>:<CIS Manager
Port>/webservices/services/TransportationManager" />
where CIS_Agent_HostName is the host where the CIS Agent is running.
</port>
<cisWsdl:address instance="<CIS_InstanceID>"portType="TransportationManager" />
</port>
</service>
Note: CIS_InstanceID is typically the hostname of the machine where the adapter is running. The
actual value can be seen from the CIS Adapter Console. This value is case sensitive.

Post-installation
2. To change the UI security, open

<%ABPP_WEB_INSTALL%>/cfg/xservice/tmgr_security/rules/uiUserSecurity.xml and
change the instance name as per your deployment in the following tags in the onValidatedLogin
method.
<PORTTYPES>
<PORTTYPE name="TransportationManager"
instance="<CISInstanceID>" />
</PORTTYPES>
3. Copy <%CIS_HOME%>\properties\cisregistry.properties to
<%ABPP_WEB_INSTALL%>\web\base\WEB-INF\classes.
cell>/base.ear/base.war/WEB-INF/classes.
<%ABPP_WEB_INSTALL%>\additional\FreightAuction\web\base\WEB-INF\classes
folder:
INF/classes
5. Copy the tmgrxui folder from
<%ABPP_WEB_INSTALL%>\additional\FreightAuction\web\base to
For WebSphere: $WAS_PROFILE_HOME/installedApps/<node cell>/base.ear/base.war
6. Make the following XServer configuration changes for CIS:
Server initialized CIS calls must have back end credentials, because the server does not have
access to the UI session.
Edit the following in xserver_fa.xml, located at <%ABPP_WEB_INSTALL%>/cfg/properties,
with appropriate values of CISInstanceID, username, and password to allow server-side CIS calls.
<cis-client-config>
<property Key="TransportationManager.CISInstanceID.USER" Value="username"/>
<property Key="TransportationManager.CISInstanceID.PASSWORD" Value="password"/>
7. Create a userhelp folder under the <%ABPP_WEB_INSTALL%>\web\base\core folder and
copy the TMgr_Freight_Auction_Employee_User_Guide_ 8.1.pdf,
TMgr_Freight_Auction_Carrier_User_Guide_8.1.pdf, and
TMgr_Freight_Auction_Admin_User_Guide_8.1.pdf from the installation package to this
folder.
If the user guide names are different, open
<%ABPP_WEB_INSTALL%>/cfg/properties/xserver_fa.xml and update the entries in the
following service parameters to the appropriate guidenames for all relevant services.
<param Name="spEmployeeGuideName"
Value="TMgr_Freight_Auction_Employee_User_Guide_8.1.pdf"/>
<param Name="spCarrierGuideName"
Value="TMgr_Freight_Auction_Carrier_User_Guide_8.1.pdf"/>
Post-installation
<param Name="spUserGuideName"
Value="TMgr_Freight_Auction_Admin_User_Guide_8.1.pdf"/>
cell>/base.ear/base.war/core
8. Update the translation files:
Copy i18n-messages_en_US.properties from
<%ABPP_WEB_INSTALL%>/additional/FreightAuction/web/base/WEB-INF/classes
into the <%ABPP_WEB_INSTALL%>/web/base/WEB-INF/classes folder.
cell>/base.ear/base.war/WEB-INF/classes
Note: If the i18n-messages_en_US.properties file already exists in the
<%ABPP_WEB_INSTALL%>/web/ui/WEB-INF/classes folder, append its content. For
g. Click Apply.
h. Click Save.
server.
Configure for different tablespace

1. Edit schemaConfig.xml in the <%ABPP_WEB_INSTALL%>/additional/FreightAuction/db folder.
Replace the default tablespace names with the appropriate entries.
<DEFAULT_TABLE_SPACE Name="jdatm_FA_data"/>
<DEFAULT_INDEX_SPACE Name="jdatm_FA_index"/>
2. Run genSchema.bat (genSchema.sh for UNIX) located in <%ABPP_WEB_INSTALL%>/bin
to generate the schema.
3. Run uploadData.bat (uploadData.sh for UNIX ) located in <%ABPP_WEB_INSTALL%>/bin
to upload the static data.
Configure Transportation Manager system

Set the ignoreTimeZonesOnDates CIS Parameter to Y

Post-installation
1. Select Server Configuration > TM Hosts > Parameter Sets from the TM web UI.
3. set ignoreTimeZonesOnDates value to Y.

This section describes the post-installation steps to be performed for Carrier Equipment Availability.
Directory locations
This section lists the application installations and their locations used in configuration.
• %JAVA_HOME%: Directory where the JDK is installed.

For example: C:\jdk1.7_SR2
phase.
• $WAS_PROFILE_HOME: WebSphere application profile home directory for UNIX.
For example: /data/WebSphere/AppServer80/profiles/AppSrv02
Configuration steps
1. WSDL Configuration for CIS instance:
Edit <%ABPP_WEB_INSTALL%>/wsdl/i2/ TransportationManagerService.wsdl to point
to the appropriate CIS instance according to the deployment.
<soap:address location="http://<CIS_Agent_HostName>:<CIS Manager
Port>/webservices/services/TransportationManager" />
where CIS_Agent_HostName is the host where the CIS Agent is running.
</port>
<cisWsdl:address instance="<CIS_InstanceID>"portType="TransportationManager" />
</port>
</service>
Note: CIS_InstanceID is typically the hostname of the machine where the adapter is running.The
actual value can be seen from the CIS Adapter Console.This value is case sensitive.

Post-installation
2. To change the UI security, open

<%ABPP_WEB_INSTALL%>/cfg/xservice/tmgr_security/rules/uiUserSecurity.xml and
change the instance name as per your deployment in the following tags in the onValidatedLogin
method.
<PORTTYPES>
<PORTTYPE name="TransportationManager"
instance="<CISInstanceID>" />
</PORTTYPES>
3. Copy <%CIS_HOME%>\properties\cisregistry.properties to
<%ABPP_WEB_INSTALL%>\web\base\WEB-INF\classes.
<%ABPP_WEB_INSTALL%>\additional\CarrierEquimentAvailability\web\base\WEB-
INF\classes folder:
INF/classes
5. Copy the tmgrxui folder from
<%ABPP_WEB_INSTALL%>\additional\CarrierEquimentAvailability\web\base to
(For WebSphere: $WAS_PROFILE_HOME/installedApps/<node cell>/base.ear/base.war)
6. Modify the XServer configuration for CIS:
Server initialized CIS calls must have back end credentials, because the server does not have
access to the UI session.
Edit the following with appropriate values of CISInstanceID, username, and password to allow
server-side CIS calls.
<cis-client-config>
<property Key="TransportationManager.CISInstanceID.USER" Value="username"/>
<property Key="TransportationManager.CISInstanceID.PASSWORD" Value="password"/>
7. Create a userhelp folder under the <%ABPP_WEB_INSTALL%>\web\base\core folder, and
copy TMgr_Carrier_Equipment_Availability_User_Guide_8.1.pdf from the installation
package to this folder.
(For WebSphere: $WAS_PROFILE_HOME/installedApps/<node
cell>/base.ear/base.war/core).
8. Update the translation files.
Copy i18n-messages_en_US.properties from
<%ABPP_WEB_INSTALL%>/additional/CarrierEquimentAvailability/web/base/WEB-
INF/classes to the <%ABPP_WEB_INSTALL%>/web/base/WEB-INF/classes folder.
Post-installation
Note: If the i18n-messages.properties and i18n-messages_en_US.properties files already

exist in the <%ABPP_WEB_INSTALL%>/base/WEB-INF/classes folder, append their
content. For WebSphere: $WAS_PROFILE_HOME/installedApps/<node
To configure different logging levels for services, open
<%ABPP_WEB_INSTALL%>/cfg/properties/xserver_cea.xml and modify the selected
services.
From
<logLevels>
<logLevel Value="Exception"/>
<logLevel Value="Error"/>
</logLevels>
to
<logLevels>
<logLevel Value="All"/>
</logLevels>
g. Click Apply.
h. Click Save.
server.
Configure for different tablespaces

1. Edit schemaConfig.xml file located in the
<%ABPP_WEB_INSTALL%>/additional/TMTBCBridge/db folder.
Replace the default tablespace names with appropriate entries.
<DEFAULT_TABLE_SPACE Name="jdatm_tmtbc_data"/>
<DEFAULT_INDEX_SPACE Name="jdatm_tmtbc_index"/>
2. Run genSchema.bat (genSchema.sh for UNIX) located in the
<%ABPP_WEB_INSTALL%>/bin folder to generate the schema.

Post-installation
3. Run uploadData.bat (uploadData.sh for UNIX ) located in the

<%ABPP_WEB_INSTALL%>/bin folder to upload the static data.
Configure Transportation Manager system

Set the ignoreTimeZonesOnDates CIS Parameter to Y
1. Select Server Configuration > TM Hosts > Parameter Sets from the TM web UI.
3. set ignoreTimeZonesOnDates value to Y.
SSO configuration for Windows/WebLogic

This chapter describes the process to configure the JDA Transportation Manager Agile Business Process
Platform applications and JDA Transportation Manager for Single Sign On (SSO).
Directory locations
The following section lists application installations used during configuration and their locations:
• %JAVA_HOME%: Directory where the jdk is installed.

For example: C:\jdk1.7
phase.
JDA Infrastructure Services configuration

1. Install the JDA Infrastructure SSO Adapter.
2. Change directories to %CIS_HOME%/bin.
Run the following command to install the SSO Adapter in the CIS Console with port type
webSessionCoordinator:
launch.bat installSSOAdapter.py
3. Edit the SessionCoordinator.xml file.
Change directories to %CIS_HOME%/xml and open the SessionCoordinator.xml file in an
editor.
In the port type definition, update the enableSessionCoordination property, setting the value to
True.
<portType name="webSessionCoordinator" serviceName="WebSessionCoordinator"
version="6.1">
<initializer class="com.i2.cis.session.service.WebSessionCoordinator">
<property name="enableSessionCoordination" value="true"/>

Post-installation
<property name="sessionTimeoutMins" value="30"/>

Note: Enabling SessionCoordination moves the lifecycle of the individual sessions in the workflow
to the JDA Infrastructure Service SSO Service. The virtual session spanning multiple applications
expires only when there has been no user activity in any of the applications for the duration of the
sessionTimeoutMins property value.
4. Start the webSessionCoordinator from the CIS Console by selecting the green arrow to the left of
the Status column.
Enable Java security

1. Add the cis-jaas.config file created during the Transportation Manager configuration to the JVM
arguments for Transportation Manager WebLogic domain.
2. Add the following as a JVM parameter to the tmenv.cmd file:
-Djava.security.auth.login.config=%TM
_INSTALL%\tmgr_domain\applications\cis\properties\cis-jaas.config.
3. Verify the path specified for cis-jaas.config in mycomputer.cmd file under
%TM_INSTALL%\tmgr_domain before altering tmenv.cmd.
Enable SSO for JDA Transportation Manager web user interface

Set the SSO flag for application deployment
If the TM Web UI was not deployed with the SSO option enabled, perform the following changes.
1. Stop the JDA Transportation Manager web user interface.

Shutdown the tmgr_domain Weblogic domain.
2. Update the JDA Transportation Manager web user interface configuration file.
Edit config_env.cmd, available in %TM_INSTALL%\tmgr_domain\TM_Web_Config. Set the
appropriate domain value for the network environment:
• Set the value of SSO_ENABLE to true
• Set the value of SSO_CIS_DOMAIN to .jda.com
Note: The preceding ‘.’ (dot) is required as part of the domain value. Replace jda.com with an
appropriate domain.
Configure the JDA Transportation Manager login module

JDA Transportation Manager provides a JAAS compliant login module, TDM_Login.jar. This section
describes the necessary configuration settings.
1. Edit the tmhost.properties file located in the

%TM_INSTALL%\tmgr_domain\applications\login\properties folder.
The file consists of:
• tm.host: Allows you to set to the full (domain qualified) name of the host running the
Transportation Manager web user interface.
• tm.port: Allows you to define the port number where the Transportation Manager web user
interface is listening for connections.
For example:
tm.host = tmappserver.jda.com
tm.port = 7001
2. Redeploy the JDA Transportation Manager web user interface.

Post-installation
Run config_parm.bat to redeploy the Transportation Manager web user interface with the
updated configuration. This file is located in
%TM_INSTALL%\tmgr_domain\TM_Web_Config.
This batch file considers Schema name, Oracle Password, and Oracle SID parameters.
For example:
config_parm.bat tmschema tmpasswd TMDB
3. Refresh the configuration by re-running installWinService, if you are using TMWebServices.
4. If the CIS agent is configured on a port other than the default port (5015), move the
<%CIS_HOME%>\properties\cisregistry.properties file to
%TM_INSTALL%\tmgr_domain\applications\cis\properties.
5. Verify the configuration:
• TDM_Login.jar is located in %TM_INSTALL%\tmgr_domain\applications\login\lib.
• tmhost.properties and MyResource_en_US.properties are located in
%TM_INSTALL%\tmgr_domain\applications\login\properties.
• tmhost.properties has tm.host property pointing to a server running Transportation
Manager Web UI.
• cis-jaas.config is the JAAS login configuration file referenced by the Java Security settings. It
is located in
%TM_INSTALL%\tmgr_domain\applications\cis\properties.
It must contain an entry for tdm, which specifies the use of the TDM_Login.jar login module for
user authentication, including the parameters set in the tmhost.properties file.
tdm
{com.i2.tm.core.security.TDMLoginModule required
UserKey="tdm.user"
TMHostKey="tm.host"
TMPortKey="tm.port"
HtmlUserName="loginUser"
HtmlPassword="loginPassword";
};
6. Restart the TM Web UI.
Enable SSO for JDA ABPP

CIS components
1. CIS jars must be available for the ABPP application.
2. Ensure that the following jars are available in the %ABPP_WEB_INSTALL%/web/ui/WEB-
INF/lib folder. These files may be copied from the JDA CIS installation. They are located in the
%CIS_HOME%/lib folder:
• cis.jar
• cis-util.jar
• cis-sso.jar
Post-installation
• cis-sso-spi.jar
• jdom.jar
• connector.jar
• jmxri.jar
• log4j-api-2.0-beta9.jar
• log4j-core-2.0-beta9.jar
• log4j-slf4j-impl-2.0-beta9.jar
• slf4j-api-1.7.5.jar
Note: The ABPP user interface application name, which you specify during the installation,
determines the location for the WEB-INF folder. For example, if you select base as the application
name, the path is %ABPP_WEB_INSTALL%/web/base/WEB-INF/lib.
3. Enable CIS Security.
Ensure that the following values in the
%TM_INSTALL%/properties/cisapi/TransportationManagerBindings-
<CISInstanceID>.xml file are set:
<security requireClientAuthentication="true" requireSenderIdentity="true"/ >
4. Restart the Transportation Manager CIS Adapter, if these values are updated.
Transportation Manager components

Install the Transportation Manager Login Module using the following steps:
1. Copy the file TDM_Login.jar from the TM server's

$WAS_PROFILE_HOME/lib/app/login/lib folder to the
$WAS_PROFILE_HOME/installedApps/<node cell>/base.ear/base.war/WEB-INF/lib
folder.
2. Copy the tmhost.properties and MyResource_en_US.properties files from the
$WAS_PROFILE_HOME/lib/app/login/properties folder to the
$WAS_PROFILE_HOME/installedApps/<node cell>l/base.ear/base.war/WEB-
INF/classes folder.
Note: If your locale is different from en_US, rename the MyResource_en_US.properties file to
match your locale. For example, rename MyResource_en_US.properties to
MyResource_en_AU.properties if your locale is en_AU.
Weblogic components
1. Java security
If not present, modify the Weblogic startup script to include a command line argument to specify
the login configuration file.
For example:
In %ABPP_DOMAIN%/bin/setDomain.cmd (Windows) or
%ABPP_DOMAIN%/bin/setDomain.sh (UNIX), where %ABPP_DOMAIN% is the WebLogic
domain under which the ABPP application is being deployed.
set JAVA_PROPERTIES=%JAVA_PROPERTIES% -Djava.security.auth.login.config=
%TM_WEB_DOMAIN%\applications\cis\properties\cis-jaas.config
Where %TM_WEB_DOMAIN% is the tmgr_domain folder of the Transportation Manager Web UI install.
2. Cookie path setup

Post-installation
Modify the weblogic.xml file in the %ABPP_WEB_INSTALL%\web\base\WEB-INF folder of

the ABPP application, to provide a cookie path.
Use a file editor to add a session parameter named CookiePath under the session-descriptor
element.
<session-param>
<param-name>CookiePath</param-name>
<param-value>/base</param-value>
</session-param>
This assumes that the application name is base. You can change the param-value for other
application accordingly.
3. Restart the ABPP application WebLogic domain.
ABPP components
1. Enable Single Sign On.
Use a file editor to open the file x2.properties located in the
%ABPP_WEB_INSTALL%\web\base\WEB-INF\classes folder.
Enable single sign on by setting the value of ssoEnabled property to True.
2. Specify the Login Module for ABPP application.
Update the x2.properties file located in the %ABPP_WEB_INSTALL%\web\ui\WEB-
INF\classes folder. Set the SSOLoginModule property to tdm, the entry in the JAAS configuration
file for the TM Login Module.
SSOLoginModule=tdm
3. Set the default ABPP Web Service bindings to CIS.
Verify in the ABPP application’s x-server property file that the default web service bindings are set
to CIS.
<wsdl-client-config>
<bindings>
<defaultBinding Name="CIS" />
</bindings>
</wsdl-client-config>
Note: If the value is currently set to SOAP, change it to CIS and restart the server.
4. Configure and activate the TMGR ABPP security service. The Transportation Manager
TMGR_SECURITY ABPP service is configured to be used in an SSO deployment.
5. Validate the settings in the uiUserSecurity.xml file located in the
%TM_ABPP_INSTALL%\cfg\xservice\tmgrx_security\rules folder.
6. Look for the onValidatedLogin method and verify that the instance attribute of PORTTYPE property
is set to the CISInstanceID value used by the Adapter of the Transportation Manager CIS.
CISInstanceID is typically the hostname where the CIS Agent is running.The actual value can be
seen from the CIS Adapter Console.
Note: This value is case sensitive.
<DEFINE_METHOD Name="onValidatedLogin"
.....
<RULE>
<ACTION>

Post-installation
<USER_ID Value="{$thisParam/LOGIN_NAME/@Value}"
<PASSWORD Value="{$thisParam/PASSWORD/@Value}"
<PORTTYPES>
</PORTTYPES>
</ACTION>
</RULE>
</DEFINE_METHOD>
7. Verify that the Transportation Manager TMGR_SECURITY ABPP service is the
activeUserAuthenticationService and activeUserAuthorizationService.
Use a file editor to open the xserver property file in the
%TM_ABPP_INSTALL%\cfg\properties folder. Look for the following section and verify the
value of the activeUserAuthenticationService and activeUserAuthorizationService parameters to
complete the SSO configuration for a Windows/WebLogic environment:
<service-params>
...
<param Name="activeUserAuthenticationService" Value="TMGR_SECURITY"/>
<param Name="activeUserAuthorizationService" Value="TMGR_SECURITY"/>
</service-params>
Validate SSO configuration

1. Verify that all servers are running:
• JDA CIS Agent
• JDA CIS webSessionCoordinator (SSOServer)
• JDA Transportation Manager
• JDA Transportation Manager CIS Adapter (CISServer)
• JDA Transportation Manager Web UI (Bea WebLogic Server for tmgr_domain)
• Bea WebLogic Server for the JDA Transportation Manager ABPP application domain.
2. Connect to the JDA Transportation Manager system from a web browser, using the URL. For
example, http://tmserver.jda.com:7001/tm.
Note: The JDA CIS webSessionCoordinator manages the virtual session for all applications in the
SSO domain.
3. Connect to the JDA Transportation Manager ABPP application user interface from the same web
browser screen, enter the URL for the JDA Transportation Manager ABPP web application, for
example, http://tmabppserver.jda.com:7005/base/home. The JDA Transportation Manager ABPP
application user interface is displayed without the option of the login screen.
This indicates that the SSO configuration is functioning correctly.

Post-installation
The URL for both the JDA Transportation Manager Web UI and JDA Transportation Manager ABPP
Web application must have the fully qualified domain path, as this value determines which
applications the webSessionCoordinator will place in the same SSO session.
This completes the steps required to configure the JDA Transportation Manager ABPP Application and
JDA Transportation Manager for Single Sign On.
SSO configuration for AIX/WebSphere

This chapter describes the process to configure the JDA Transportation Manager Agile Business Process
Platform applications and JDA Transportation Manager for Single Sign On (SSO).
Directory locations
The references to the following application installation locations are used during configuration:
• $JAVA_HOME: The directory where the jdk is installed.

For example: /usr/jdk1.7_SR2
• $CIS_HOME: cis-sdk directory of the JDA Infrastructure Services Installation.
For example: /data/jda/CIS/8.1/cis-sdk
• $TM _INSTALL: directory in which JDA Transportation Manager is installed.
For example: /data/jda/tmgr/8.1
• $WAS_PROFILE_HOME: The is the WebSphere profile home directory
For example: /usr/IBM/WebSphere/AppServer/profiles/AppServer01
JDA Infrastructure Services configuration

1. Install the JDA Infrastructure SSO Adapter. Change directories to $CIS_HOME$/bin.
2. Run the following command to install and display the SSO Adapter in the CIS Console with port
type as webSessionCoordinator:
launch.sh installSSOAdapter.py
3. Update the SessionCoordinator.xml file. Change directories to $CIS_HOME$/xml and open the
SessionCoordinator.xml file in an editor.
Note: In the port type definition, set the value of ‘enableSessionCoordination’ to True.
<portType name="webSessionCoordinator" serviceName="WebSessionCoordinator"
version="6.1">
<initializer class="com.i2.cis.session.service.WebSessionCoordinator">
<property name="enableSessionCoordination" value="true"/>
<property name="sessionTimeoutMins" value="30"/>
Note: Enable SessionCoordination to move the lifecycle of the individual sessions in the workflow
to the JDA Infrastructure Service SSO Service. The virtual session includes multiple applications
times out, if there is not activity performed for period defined in the sessionTimeoutMins.
4. Start the webSessionCoordinator from the CIS Console by clicking the green arrow on the left of
the Status column.

Post-installation
Enable SSO for JDA Transportation Manager web user interface

Set the SSO flag for application deployment
Note: In the following steps, $WAS_PROFILE_HOME represents the location of the WebSphere
application server profile. For example, /usr/IBM/WebSphere/AppServer/profiles/AppServer01.
1. Stop the JDA Transportation Manager web user interface.
a. Open the Command window in $WAS_PROFILE_HOME/bin.
b. Stop TM server using ./ stopserver.sh server1.
2. Copy jsse.jar from $CIS_HOME/lib to $WAS_PROFILE_HOME/lib/app/cis/lib.
3. Update the tmenv.sh file located in the $WAS_PROFILE_HOME/ installableApps/tm/config
folder.
4. Set the domain value for the network environment.
• Set the value of SSO_ENABLE to true
• Set the value of SSO_CIS_DOMAIN to TM Web’s application server host domain, that is,
.jda.com
Note: The preceding ‘.’ (dot) is required as part of the domain value.
Configure the JDA Transportation Manager Login Module

Note: JDA Transportation Manager provides a JAAS compatible login module, TDM_Login.jar. This
section describes the configuration settings.
1. Update the tmhost.properties file located in the $WAS_PROFILE_HOME
/lib/app/login/properties folder.
The file consists of:
• tm.host: Allows you to set to the full (domain qualified) name of the host running the
Transportation Manager web user interface.
• tm.port: Allows you to set the port number where the Transportation Manager web user
interface is listening for connections.
For example:
tm.host = tmappserver.jda.com
tm.port = 1352
2. If the CIS agent is configured on a port other than the default port, copy the file
$CIS_HOME/properties/cisregistry.properties to
$WAS_PROFILE_HOME/lib/app/cis/properties.
3. Redeploy the JDA Transportation manager web user interface.
4. Stop the application and uninstall.
Uninstall a previous deployment

2. Log in to the admin console, the default is http://MyHostname:9060/admin.
3. Select Applications > Application Types > WebSphere > Enterprise Applications in the
navigation panel.
4. Select the tm check box and click the Uninstall button.
Note: If tm is running, select the tm check box and click Stop.
5. Click OK to proceed.

Post-installation
6. Click Save. If you are working on a Network Deployment, click Preferences and ensure that
Synchronize changes with Nodes is selected. If Preferences is not selected, select it and click
Apply > Save).
Redeploy TM
1. Start the WebSphere application server, if the server is not running.
2. Open a command window in the tm/config directory located in the
$WAS_PROFILE_HOME/installableApps.
3. Run the deployTM script to deploy the application. For example,
The deployTM script automatically runs the mergeCustomization program to update the web
screens with the updated information.
Note: The mergeCustomization.sh script must be run for every applicable database after you
perform the database upgrade to this TM version. The database configuration information is stored
in the tmenv file.
4. Verify that the merge***Customization.log files are error free (where *** could be List,
NavPad, ScreenElement, or Search). These files are blank, if the operation is successful. Else,
fix the exact syntax in the deployTM script for the Oracle environment.
Note: If your customizations cannot be merged, you need to use RESET instead of MERGE, which
overwrites the customizations to the web interface.
5. You can now stop and restart the WebSphere application server. This refreshes the environment
for the new Transportation Manager application.
a. Start the JDA Transportation Manager web user interface.
b. Open Command window in $WAS_PROFILE_HOME/bin.
c. Start TM server using ./ startserver.sh server1.
Classpath definition and JVM arguments

1. Log in to the admin console. For example, http://MyHostname:9060/admin.
2. Add jdom.jar and TDM_Login.jar to CIS_JARS shared library defined in the TM deployment.
a. Go to Environment > Shared Libraries and select CIS_JARS.
The shared library consists of the following jars on the classpath:
• ${CIS_LIB_ROOT}/cis-sso-spi.jar
• ${CIS_LIB_ROOT}/cis-sso.jar
• ${CIS_LIB_ROOT}/cis-util.jar
• ${CIS_LIB_ROOT}/cis.jar
• ${CIS_LIB_ROOT}/log4j-api-2.0-beta9.jar
• ${CIS_LIB_ROOT}/log4j-core-2.0-beta9.jar
• ${CIS_LIB_ROOT}/log4j-slf4j-impl-2.0-beta9.jar
• ${CIS_LIB_ROOT}/slf4j-api-1.7.5.jar
b. Append the following to the shared library classpath:
• ${CIS_LIB_ROOT}/jdom.jar
• $WAS_PROFILE_HOME/ lib/app/login/lib/TDM_Login.jar
Note: Substitute the appropriate path for $WAS_PROFILE_HOME.

Post-installation
c. Save changes.
3. Add the reference for the CIS_JARS shared library from the TM application.
a. Select Applications > WebSphere enterprise applications.
b. Click the tm application and click Shared Library references in the References section.
c. Select an application and click Reference shared libraries.
d. Select the CIS_JARS shared library from the Available list and move it to the Selected list.
e. Click OK.
f. Click Save to save the changes.
4. Add jsse.jar, cis/properties, login/properties to the classpath in the App Server.
a. Select Application Server > server1> Java and Process Management > Process
Definition > Java Virtual Machine.
b. Append the following to the classpath:
${CIS_LIB_ROOT}/jsse.jar
$WAS_PROFILE_HOME/ lib/app/cis/properties
Note:Substitute the appropriate path for $WAS_PROFILE_HOME.
c. Click Save to save the changes.
5. Add the following line to Generic JVM arguments.
-Djava.security.auth.login.config=$WAS_PROFILE_HOME/lib/app/cis/properties/cis-
jaas.config
Replace $WAS_PROFILE_HOME with appropriate WebSphere profile home.
6. Click Apply.
7. Click Save.
8. Stop and start the server using the following commands from $WAS_PROFILE_HOME/bin.
• ./stopServer.sh server1.
• ./startServer.sh server1.
Enable SSO for JDA ABPP

Transportation Manager components
Install the Transportation Manager Login Module using the following steps:
1. Copy the file TDM_Login.jar from the TM server's

$WAS_PROFILE_HOME/lib/app/login/lib folder to the
$WAS_PROFILE_HOME/installedApps/<node cell>/base.ear/base.war/WEB-INF/lib
folder.
2. Copy the tmhost.properties and MyResource_en_US.properties files from the
$WAS_PROFILE_HOME/lib/app/login/properties folder to the
INF/classes folder.
Note: If your locale is different from en_US, rename the MyResource_en_US.properties file to
match your locale. For example, rename MyResource_en_US.properties to
MyResource_en_AU.properties if your locale is en_AU.
ABPP components
1. Enable Single Sign On.
Post-installation
Use a file editor to open the x2.properties file located in the

INF/classes folder. Enable Single Sign On by setting the value of ssoEnabled property to True.
ssoEnabled=true
2. Set the Single Sign On domain.
Update the cis-sso.properties file located in the $WAS_PROFILE_HOME/installedApps/<node
cell>l/base.ear/base.war/WEB-INF/classes folder. Leave the active SSO domain empty in
the SSO sessions
For example:
sso.domain=
3. Modify the x2.properties file.
Edit the x2.properties file located in the $WAS_PROFILE_HOME/installedApps/<node
cell>l/base.ear/base.war/WEB-INF/classes folder.
a. Specify the Login Module for ABPP application
Set the SSOLoginModule property to tdm. This entry is done in the JAAS configuration file for
the TM Login Module, SSOLoginModule=tdm.
b. Update the xcore.classpath.
Remove all Jar files from $TM_ABPP_INSTALL$/lib folder from this path.
4. Configure and activate the TMGR ABPP security service.
The Transportation Manager TMGR_SECURITY ABPP service is configured to be used in an SSO
deployment.
Similarly, validate the settings in the uiUserSecurity.xml file located in the
$TM_ABPP_INSTALL$\cfg\xservice\tmgrx_security\rules folder.
Search for the onValidatedLogin method and verify that the instance attribute of PORTTYPE
property is set to the InstanceID value used by CIS Adapter of the Transportation Manager.
CISInstanceID is typically the hostname where the CIS Agent is running.The actual value can be
seen from the CIS Adapter Console.
Note: This value is case sensitive.
<DEFINE_METHOD Name="onValidatedLogin"
.....
<RULE>
<ACTION>
<USER_ID Value="{$thisParam/LOGIN_NAME/@Value}"
<PASSWORD Value="{$thisParam/PASSWORD/@Value}"
<PORTTYPES>
</PORTTYPES>
</ACTION>
</RULE>

Post-installation
</DEFINE_METHOD>
5. Edit cis-auth.config file from the $WAS_PROFILE_HOME/installedApps/<node
cell>l/base.ear/base.war/WEB-INF/classes folder and add tdm module.
tdm
{
com.i2.tm.core.security.TDMLoginModule required
UserKey="tdm.user"
TMHostKey="tm.host"
TMPortKey="tm.port"
HtmlUserName="loginUser"
HtmlPassword="loginPassword";
};
6. Generic JVM arguments
a. Log in to the admin console (For example (http://MyHostname:9060/admin)).
b. Select Servers > Server Types > WebSphere ApplicationServers > Server1 on the
navigation panel.
c. Click Java and Process management > Process Definition.
d. Click Java Virtual Machine.
e. Add the following line to Generic JVM arguments.
-Djava.security.auth.login.config=$WAS_PROFILE_HOME/installedApps/<your
cell>/base.ear/base.war/WEB-INF/classes/cis-auth.config
Note: Replace $WAS_PROFILE_HOME with appropriate WebSphere profile home.
f. Click Apply.
g. Click Save.
h. Stop and start the server using the following commands from $WAS_PROFILE_HOME/bin.
./stopServer.sh server1.
./startServer.sh server1.
Enable cookies for TM and ABPP

The WebSphere configuration must be improved to include the application level session management
configuration.
For TM
1. Log in to the admin console. For example, http://MyHostname:9060/admin.
2. Select Application > Application Types > WebSphere > Enterprise Applications > TM >
Session Management from the navigation panel.
3. Select the Enable Cookies check box and click Enable Cookies.
4. Change the cookie path to /tm and click Apply.
5. Click Save to save the file.
Post-installation
For ABPP
1. Log in to the admin console from a browser. The default URL is http://MyHostname:9060/admin.
2. Select Enterprise Applications > base in the navigation panel.
3. Click Session Management.
4. Select the Enable Cookies check box and click Enable Cookies.
5. Change the cookie path to /base and click Apply.
6. Click Save to save the file.
Validate Single Sign On configuration

1. Verify that the following servers are running:
• JDA CIS Agent
• JDA CIS webSessionCoordinator (SSOServer)
• JDA Transportation Manager
• JDA Transportation Manager CIS Adapter (CISServer)
• JDA Transportation Manager Web UI (IBM WebSphere Server for tm)
• IBM WebSphere Server for the JDA Transportation Manager ABPP application
2. Log in to the JDA Transportation Manager system, using the URL. For example,
http://tmserver.jda.com:1352/tm.
Note: The JDA CIS webSessionCoordinator manages the virtual session for all applications in the
SSO domain.
3. Log in to the JDA Transportation Manager ABPP application and enter the URL for the JDA
Transportation Manager ABPP web. For example, http://tmabppserver.jda.com:1456/base/home.
The SSO configuration now functions as required.
Notes:
• This ensures that you can access the JDA Transportation Manager ABPP application without
logging in.
• The URL for both the JDA Transportation Manager Web UI and JDA Transportation Manager
ABPP Web application must have the fully qualified domain path, as this value determines
which applications the webSessionCoordinator will place in the same SSO session.
For example:
http://tmserver.jda.com:1352/tm
http://tmabppserver.jda.com:1456/base/home

Utilities and common tasks
Chapter 6. Utilities and common tasks

User interface extension
Starting with the 6.3.5 release, certain user interface functions are developed utilizing Rich Internet
Application (RIA) technology. These functions offer more advanced configuration and usability
features.
For the Transportation Manager, these features include:
• Location Throughput Group - Capacity Maintenance

• Transportation Smartbench
All of these functions are deployed within a single web application.
The following sections describe how to install and configure these new features.
Transportation Smartbench
1. Access to the Transportation Smartbench is through the Transportation Manager Web UI’s Solution
Pad. This comes pre-configured with the TM Web UI installer.
2. To enable access to the Tranportation Smartbench for specific UserGroups, use Environment >
UI Customization > Navigation Pad > Modules.
The Transportation Smartbench is active for the Security User Group by default. To enable access
for additional User Groups, proceed with the following steps:
a. Search for the Solutions Pad module (Module Type = Solution).
b. View Contents of the Solutions module.
c. Select Transportation Smartbench. Activate if necessary.
d. Click User Group.
e. Select the rows for each of the required User Groups.
f. Click Authorization and set the appropriate Function Authorization level.
g. Click Submit to save the new settings, or alternatively, click Cancel.
See Allow monitoring access to a user group (on page 104) for additional details on configuring the
Navigation Pad security for User Group access.
Add Location Throughput Group Capacity Maintenance operations to the

1. Create Screen Element Version Operations (SEVO):
• List of Dates For Location Throughput Group Capacity for Shipping Location using System
Entities > Principal > Shipping Locations > Capacity > Day of Week or Capacity -
Date Specific.
Note: Screen Element Version Operations are the same for both Capacity Screens.
Screen Element ID ES_LOCATION_THROUGHPUT_GROUP_CAPACITY_DA

TES_LIST_
User Group Type Employee

SEVO ID PROPERTIES
Description Capacity Properties

Select Required Exactly One Row
Access Method Button
URL http://<@SmartbenchServerHostPort@>/tmria/lcm.js
p
URL Parameters locationID=<@EntityLocationCode@>&locationType=
<@EntityLocationTypeID@>&date=<@EntityAttribute
StartDate@>&startDate=<@EntityAttributeStartDate
@>&endDate=<@EntityAttributeEndDate@>&specific
Date=<@EntityAttributeDateBasedCapacity@>&mode
=Update&readOnly=<@IsReadOnlyAccess@>&locale=
<@UserLocale@>&returnURL=<@ReturnURL@>
Availability Both View and Update Modes
Allow Override to View Only Yes

Mode
Operation Text – Override Properties
Sequence Default value
SEVO ID DUPLICATE
Description Duplicate Capacity

p
StartDate@>&startDate=<@EntityAttributeStartDate
@>&endDate=<@EntityAttributeEndDate@>&specific
Date=<@EntityAttributeDateBasedCapacity@>&mode
=Duplicate&readOnly=<@IsReadOnlyAccess@>&local
e=<@UserLocale@>&returnURL=<@ReturnURL@>
Availability Update Mode Only

Mode
Operation Text – Override Duplicate
SEVO ID NEW
Description New Capacity

URL http://<@SmartbenchServerHostPort@>/tmria
/lcm.jsp


<@EntityLocationTypeID@>&specificDate=<@EntityA
ttributeDateBasedCapacity@>&mode=Create&readOnl
y=<@IsReadOnlyAccess@>&locale=<@UserLocale@>
&returnURL=<@ReturnURL@>
Availability Update Mode Only
Allow Override to View Only No

Mode
Operation Text – Override New
• Dock Commitment Gantt Chart using Dock Schedules > Locations with Docks > Dock
Schedule > Select Gantt Chart Entry > Capacity.
Screen Element ID ENTITY_DOCK_COMMITMENT_CHART_
SEVO ID CAPACITY
Description Capacity
p
StartDate@>&specificDate=true&mode=Update&read
Only=<@IsReadOnlyAccess@>&locale=<@UserLocale
@>&returnURL=<@ReturnURL@>
Availability Both View and Update Mode

Mode
Operation Text – Override Capacity
• List of Commitments for Dock using Dock Schedules > Locations with Docks > Dock
Schedule > Dock ID link > Capacity
Screen Element ID ENTITY_DOCK_COMMITMENT_LIST_
SEVO ID CAPACITY

p

Mode
• List of Dock Commitments using Dock Schedules > Dock Commitments > Capacity.
Screen Element ID DS_DOCK_COMMITMENT_LIST_
SEVO ID CAPACITY
p

Mode
Test the servers

This chapter describes how to test the Transportation Manager servers.

Test general connectivity

Use the following steps if you are having connectivity issues:
1. Open a command window in the TM_HOME directory.

2. If using UNIX, source your environment using . ./tmsrvenv.sh
3. Ensure that the DSC process runs without errors by starting it from the command prompt with -u
to prevent always up servers from also starting. Use the following command::
dsc -m info -u
4. Stop the DSC process.
5. Restart the DSC process from the command prompt, without the -u option. By default, a number
of always up servers also start. If they do not stay up, go back to step 1, and start each server
from the command prompt, as described in Preconfigured servers (on page 97) and Servers
configuration (on page 101).
6. Use ping to check the TCP/IP connectivity between machines. Ensure that the network can quickly
resolve host names if you are referencing machines by hostname. Also, ensure that when you ping
<hostname> on the application server, it resolves to the same IP address as when you ping it from
the clients.
7. If using an Oracle database, verify connectivity between the database server and any systems
using the Oracle and the sqlplus command, for example: sqlplus
jdatm_crp/jdatm_crp@jdatmdb
You can also use the tnsping command to verify if the alias has been set up properly. If you
cannot connect, verify the client configuration. It can be configured to point to the wrong
database, server, or port, or you can be using an invalid username or password.
Test Transportation Manager server functions

Most of the following tests require the TM servers to be running. Ensure that the DSC, TM-Web
Interface (WebLogic or WebSphere), and the CIS Agent are started on all applicable systems before
running these tests.
By default, the DSC process autostarts the following servers:
• Administration
• BusinessProcessModel
• Distance
• FinancialAndBatch
• Reporting
• TM Optimizer Request
This section also describes simple tests for Routing and Rating, the JDA Infrastructure Services
Interface, and Carrier Sequential Tender.
Administration server
This server authenticates client accounts when users log on to Transportation Manager. If you can log
into the TM-Web interface, this server is working.
BusinessProcessModelServer
This server is used during transactions with Transportation Manager and the database. This server
must also be working for a TM-Web login to succeed.

Distance Calculation server

This server calculates the distance between two points. It can interface with various distance engines,
as specified in JDA Transportation Manager Release Notes.
You can test this server from the command prompt, or the TM-Web Interface.
Note: In order to test from the TM-Web Interface, you need shipment data (either your own data, or
shipments from the Training schema).
Verify the distance engine from the command prompt

3. Enter the following command (on one line):
Windows
tools\DistPing -FROM "GEO:USA|TX|DALLAS|75234|" -TO "GEO:CAN|ON|TORONTO|M3M 3G1|"
UNIX
DistPing -FROM "GEO:USA|TX|DALLAS|75234|" -TO "GEO:CAN|ON|TORONTO|M3M 3G1|"
4. Click the Enter key to complete the test.
Note: If PC*Miler is your distance engine, this test must return a distance of about 1421 miles and a
time of 23.4 hours, depending on the version being used. Verify the output in the TM_HOME\logs
directory. If you want to activate console logging to see the DistPing results or to increase the server
logging level, see Server logging levels (on page 96) for instructions.
Verify the Distance/Transit time from the TM-Web interface

1. Log into the Web interface, and navigate to Shipment Processing > Shipments.
2. Select a shipment, and click Operations.
3. Select Distance/Transit Time from the pop-up list. The Distance Server auto-starts if not
running already.
4. Click Retrieve. The Distance and Transit Time fields must be populated with the correct values
from the call to the applicable distance engine.
5. Click Cancel to exit the override page.
FinancialAndBatchServer
This server processes the financial information and all supplementary purge requests for
Transportation Manager. Test it by issuing a FinancialAndBatchServer or purge request using the Web
interface.
In order to have minimal impact on system data, the safest way to test this server is to issue a purge
cache request for a distance engine that is not being used (for example, i2 Distance). See Purge
cached distances (on page 28) for instructions how to purge distance cache and how to monitor the
request queue.
Report server
This server uses a Crystal Reports runtime engine to process reports from Transportation Manager,
and must be run on a Windows server. You can print the reports or display them locally using the
viewer.
You can test this server from the TM-Web interface or the command prompt.

Test the Report server from the TM-Web interface

In order to perform this test, set up a Report Type, a Report Template and an actual Report. Do this
for the Sequences report (sequences.rpt) since it requires no operational data to run. The process of
setting up a report in the TM-Web interface is described in the JDA Transportation Manager System
Administration Guide, in the Setting Up Reports section. This report requires only one numeric
parameter, which is the sequence threshold. It then selects all sequences less than this number,
before the maximum value is exceeded. Sequences are stored in the database and provide automatic
sequential number generation for Load IDs and Container IDs.
Once the report is set up, print the report from the Reporting Center on the TM-Web interface and you
must see it on your browser. If it does not work, verify the Reporting Server command window or log
file for any error messages.
Test the Report server from the command prompt

2. Run the CmdTest program to send a report (for example, the Sequences report) to the email or
fax server as an attachment, as following (the last field is the threshold - only sequences with less
than this number are reported):
tools\cmdtest local x D sequences 1 * * * 1000000000
This command generates a PDF report (based on the D parameter above), and writes the location
where the file has been saved to a log file in the TM_HOME\logs directory. The log file is named
CmdTest_<pid>.log, where <pid> is the process ID.
If the file is not generated, look in the Reporting Server window or log file for any error messages.
If you want to activate console logging to see the CmdTest results in the command window or to
increase the server logging level, see Server logging levels (on page 96) for instructions.
TM optimizer request server

This server monitors the TM Optimizer request queue and forwards requests to the Transportation
Planner Shipment Consolidation adapter through the CIS agent. For interactive requests through the
TP user interface, you must use the TM Request Handler adapter. To run both the request handler and
the request server against the same schema at the same time, you must use Instance Groups to direct
requests appropriately.
Before testing, Transportation Planner must be installed, and the Shipment Consolidation adapter must
be started.
The adapter can be started from the command line, the TP launcher using
runTPShipmentConsolidationEngine64-OPT.py, or from the CIS console. If you start from the launcher,
Issue an optimizer request through the Request server

Note: The following steps create an optimized load if successful. Do not perform them in a production
environment unless you are sure this is the desired result. Otherwise, you can just ensure that all
required servers start up, and stop this test after step 4.
1. Log into the TM Web UI and navigate to Load Build > Work with Plan > Shipments >
Unassigned.
2. Select a shipment and click Select for Optimization.
Note: If you do not have any unassigned shipments, process your workflow to reach this stage.
3. Navigate to Load Build > Work with Plan > Control.
4. Click Optimize, and then Submit.

Both the Shipment Consolidation and TM Optimizer Request server windows indicate that the
optimization request has been processed. However, the request server cannot display any activity
if the console logging settings are too low.
5. Navigate to Load Build > Optimization Requests to confirm that your request is successfully
completed.
Routing and Rating

This Transportation Planner adapter calculates rates based on specific variables within Transportation
Manager. Before testing, Transportation Planner must be installed, and the Routing and Rating adapter
must be started.
Note: The adapter can be started from the command line, the TP launcher using
runTPShipmentConsolidationEngine64-RR.py, or from the CIS console. If you start from the launcher,
To test this server, rate a shipment using the Transportation Manager browser client.
Rate a shipment
1. Log into the TM Web UI and navigate to Shipment Processing > Shipments.
2. Select a shipment and click Rating.
3. Click Rate. If you get anything other than the following message indicates that the Routing and
Rating adapter is being accessed properly. Also, test the command window or adapter log on the
TP system to verify that the request is received and processed.
"Routing and Rating of Shipment 01002 failed : Cannot get any valid CIS Connection
to ShipmentConsolidation."
JDA Infrastructure services interface

This interface processes the inbound and outbound Infrastructure Services requests. Ensure to start
the CIS agent on all related machines before performing these steps.
Test the JDA Infrastructure services interface

2. If using the CISServer program, start it using the shortcut created during the installation. For
UNIX, use the command from the start_servers.sh program.
After successfully started, the server displays a message that it is ready to receive messages.
The required Java parameters (for example, -Xmx256m) are stored in a file in the
properties\cisapi folder called CISServer.properties. If you are using very large XML files and
running out of Java memory on an AIX system, add the following parameter to this file:
-Xoss7168k. This is the overall Java stack size for an AIX system.
3. If you are not using the CISServer, start the TransportationManager CIS adapter from the
Infrastructure Services Manager, or from a command prompt in the TM_HOME directory, as in the
following example:
Note: You must not start this adapter from the Services Manager on a production system. In this
mode, adapter activity is logged to memory and the process eventually runs out and fails.
For BindingServerName, substitute RMIServer, OperationServer (for webMethods), or
MQIntegrationContainer depending on your binding type.
For the <jvmArgs> values, search for CIS_HOME\conf\cisAdapters.xml file and identify the
jvmArgs parameter for the adapter that specifies the bindingFile as
APIEnterpriseBindings.xml.

The jvmArg values Xms and Xmx are initial and maximum heap size and Xss is the native stack
size per thread. Xoss is the overall Java stack size for the system (allocated as required), which is
only valid on AIX systems.
On Windows:
%CIS_HOME%\bin\launch %CIS_HOME%\bin\runBindingServerName.py C:\jda\tmgr\8.1
\MetaData\APIEnterpriseBindings.xml <jvmArgs>
On UNIX:
$CIS_HOME/bin/launch.sh $CIS_HOME/bin/runBindingServerName.py
/opt/jda/tmgr/8.1/MetaData/APIEnterpriseBindings.xml
<jvmArgs>
4. After successfully starting, the server displays a message that it has been started.
Note: To run the adapter from the Infrastructure Services Manager, ensure that the binding type
is correctly set before starting it (RMI, OperationServer (for webMethods), or MQ).
5. To send event notifications, start the Transportation Manager Event Notification server from the
Start Menu (or the start_servers.sh program on UNIX).
6. To publish outbound events in Infrastructure Services format, start the outbound
NotifyEventNotification CIS adapter from the Infrastructure Services Manager, or from a
command prompt in the TM_HOME directory, as follows. For BindingServerName, substitute
RMIServer, OperationServer (for webMethods), or MQIntegrationContainer depending on your
binding type.
%CIS_HOME%\bin\launch %CIS_HOME%\bin\runBindingServerName.py C:\jda\tmgr\8.1
\EventNotif\ENEnterpriseBinding.xml <jvmArgs>
Again, for the <jvmArgs> values, search for CIS_HOME\conf\cisAdapters.xml - this time under
the adapter that specifies a bindingFile of ENEnterpriseBinding.xml.
7. Edit one of the sample CIS XML files (CISRetrieveEquipType.xml, CISRetrieveCarrCode.xml, or
CISRetrieveCarr.xml) in the tools directory. Substitute a valid external Equipment Code, SCAC
code, or Carrier Code depending on the file being used.
8. Open a command window in the tools directory. If using UNIX, ensure to source the tmsrvenv.sh
program using . ./tmsrvenv.sh to set your environment.
9. Enter the testCIS command (or testCIS.sh on UNIX) to submit the request, for example:
testCIS CISRetrieveEquipType.xml MyUsername MyPassword
10. The program must return the output for the operation requested.
Shut down the adapters

After you finish testing, stop the adapters from the Infrastructure Services Manager, or from the
command line. Stop adapters from the command line using the launch command, and the appropriate
adapter port type. The format of the command is launch stopAdapter.py -p PortType, where
PortType can be TransportationManager or NotifyEventNotification.
For example:
%CIS_HOME%\bin\launch %CIS_HOME%\bin\stopAdapter.py -p TransportationManager
CarrierSequentialTenderingServer
This server automatically tenders loads using rate shop and user-defined criteria. It can cancel and re-
tender a load to another carrier after a predefined period has elapsed or the tender is rejected.
To test this server, automatically tender a load in Transportation Manager.

The field length of the service code is extended in TM 8.1. Therefore, when migrating from 6.3.5.1 to
8.1, execute CnvtAutoTdrInfo.exe to properly format the data in the Auto Tender table. Following
are the instructions:
1. Ensure that the TM servers are up and running.

2. Navigate to the <TM_INSTALL> folder through command prompt.
3. Run CnvtAutoTdrInfo.exe through command prompt as shown in the following example:
call <TM_INSTALL>\tools\CnvtAutoTdrInfo.exe –USER <TM_User> –PASS <TM_Password>
Caution: The following steps can send a tender to a carrier, depending on your configuration.
Automatically tender a load

1. Ensure that the TP Shipment Consolidation adapter for Routing and Rating has been started.
2. Start the CarrierSequentialTenderingServer manually, if it is not already running.
3. Within the Web UI, select Load Level for Auto Tender in the Global Settings (found under
Environment > Global Settings > Auto Tendering).
4. Submit a load for auto tendering as follows:
• Navigate to Load Processing > Loads
• Select a load and click Operations.
• Select Auto Tender > Start Auto Tender
A message that says - Sent to Auto Tendering, is displayed and you should also see the processing
activity in the CarrierSequentialTenderingServer log (and in the server command window, if console
logging settings allow).
Test email and fax connectivity

The system can be configured to send reports and notifications through email, fax, or both. You must
test your email and fax connectivity before running this test to identify any potential problems.
1. Ensure that the required software has been installed and configured.
2. Ensure that required parameters are properly configured in the RPT parameter set to match your
email and fax software. See Send reports and notifications through fax and email (on page 33) for
required settings.
3. Ensure that there are no other report servers running. The Report Server is usually configured to
run on a single machine.
4. If not using SMTP, start the email client program (Microsoft Messaging or Notes) if not already
started on the Windows machine running the Report Server.
5. Test an email or fax message sent through the email server to verify that the client is properly
configured.
6. Ensure that the DSC program is running on all applicable machines.
8. Run the CmdTest program to send a report (for example, the Sequences report) to the email or
fax server as an attachment, as follows (the last field is the threshold - only sequences with less
than this number are reported):
tools\cmdtest local x M sequences 1 * * * 1000000000
9. Press the Enter key when prompted with Enter Cc List.
10. Enter any text string when prompted with Enter Body on a line. This is the body of the email or
fax message.
11. The next prompt is Enter To List. Your input depends on whether you want to test the email or
fax connection. For email, the input format is:
[email:<recipient>]
for example, [email:John Smith].
Some email servers require you to determine the complete email address, for example:
John_Smith@mycompany.com.
To send a message to a fax server, the input depends on the fax server being used. The following
table lists some examples:
Fax server "To List" format Example

FaxMaker [faxmaker:<telephone [faxmaker:555-1212]
#>]
Fax for Domino [<name>@<tel [John Smith@555-
#>@<fax domain> 1212@faxdom1]
VSI-FAX [fax:<telephone #>] [fax:555-1212]
After Enter is pressed, the Report Server starts up, if not already running, and various status
messages are sent to the log file. If successful, the report is sent to the specified email or fax
destination.
If the test fails, verify the appropriate log files in the TM_HOME\logs directory. If the log file does
not include INFO level information, increase the logging level as described in Server logging levels
(on page 96), and rerun the test to obtain details of the cause of the failure.
After the CmdTest is successful, you are ready to test sending reports or notifications through fax
or email from within the application. For more information, see the Transportation Manager User
Guide or the OnLine Expert in Transportation Manager.
Test the Web interface

The Web interface provides an interface to Transportation Manager data. You can make online queries
and remote updates to the system, within the constraints of security and data integrity.
For more information, see the Transportation Manager User Guide or the OnLine Expert in
Transportation Manager.
Environment
Web components are mostly a collection of Java classes run on a Web application server using a
Servlet engine. You can use any compatible Web browser for the Web Interface. The client machine
must have the necessary TCP/IP and firewall access.
Use the following steps to test the Web interface:
1. Ensure that the Web server (if applicable) and the DSC are started on their respective machines.
2. If using WebLogic, ensure that the WebLogic server is started using the shortcut you created, or by
starting the TMWebService from the Windows services applet. On UNIX, use the
starttmgr_domain.sh or start_servers.sh shell.
3. If using WebSphere, ensure that the WebSphere application server is started.
4. Use a Web browser to open the login page on the Web server. See Access the TM-Web interface on
WebLogic (on page 56) or Access the TM-Web interface on WebSphere (on page 64).

Environment
Web components are mostly a collection of Java classes run on a Web application server using a
Servlet engine. You can use any compatible Web browser for the Web Interface. The client machine
must have the necessary TCP/IP and firewall access.
Use the following steps to test the Web interface:
1. Ensure that the Web server (if applicable) and the DSC are started on their respective machines.
2. If using WebLogic, ensure that the WebLogic server is started using the shortcut you created, or by
starting the TMWebService from the Windows services applet. On UNIX, use the
starttmgr_domain.sh or start_servers.sh shell.
3. If using WebSphere, ensure that the WebSphere application server is started.
4. Use a Web browser to open the login page on the Web server. See Access the TM-Web interface on
WebLogic (on page 56) or Access the TM-Web interface on WebSphere (on page 64).
Test Oracle objects

After running any script for an Oracle database, you can see INVALID packages, specifically with a
PUB_ADDR_PCK package. If a package is INVALID, compile it and ensure that there are no errors.
Verify the object status by connecting to the database using an SQL client such as SQL*Plus. Use the
appropriate schema ID and password.
1. Connect to the database using the Transportation Manager schema ID.

2. Enter the following SQL command to verify the user objects:
select * from user_objects where status <> ’VALID’;
This displays any packages that are not valid, for example:
PUB_ADDR_PCK
3. Compile any packages that are not valid, for example:
alter package pub_addr_pck compile;
4. Note any errors when compiling.
5. Compile any views that are not valid using @recompile.sql
Download JDA TM App from Apple Store

1. Load the Apple Store and download the JDA TM application.
2. Select a customer ID to change which customer is selected.
3. Enter the customer name that you provided as part of the CPS solution to map a customer name
to an ABPP server.
4. Test the login with your preferred Employee or Carrier users.

Troubleshooting
Chapter 7. Troubleshooting
• Symptom: Slow CIS API processing
Resolution: Edit APIEnterpriseBindings. Modify Schemavalidation = True to False. Save the file
and rerun the CIS_CONFIG_PARM process to reload the TMS CIS adapter
• Symptom: CIS API processing is throwing error Flex Field not allowed.
Resolution : Modify the CISAdapter.properties template file and change AllowFlex = True. Save
the file and rerun the CIS_CONFIG_PARM process to reload the TMS CIS adapter
• Symptom: TP shipmentconsolidationEngine does not start when using 64bit mode.
Resolution: TM/TP install requires 64bit JDK and oracle client to be installed. On systems where
both TM and TP reside the application will read from the environment variables and use the first
instance path to JDK or Oracle. To resolve, change the TP properties file to use the 64bit Oracle
path.
Install Gnome Display Manager (GDM) under Solaris 11-TM and TP

To make JDA products work properly, install GDM under Solaris 11. Solaris 11 is shipped with a basic
VNC (Virtual Network Computing) service that is partially available. VNC is used for exporting displays,
similar to x-manager or Reflection-X. You can completely enable VNC under Solaris 11 by installing
GDM.
Note: You must install the following packages as pre-requisites

• man
• telnet
1. Load GDM to add the required packages to the system. You must install slim_install package that
adds an additional 390 packages to the system. Run the following command:
pkg install slim_install
2. Run the following command after installing slim_install package. An error is displayed that a
consolekit dependency is restarting too quickly.
svcs consolekit
3. Run the following commands to check the consolekit dependencies and restart:
svcs -d consolekit
svcadm disable dbus
svcadm clear consolekit
svcadm enable -r consolekit
4. Provide a console to the passive VNC X Server through X Display Management Control
Protocol.Make sure that Enable = true and DisallowTCP= false in /etc/gdm/custom.conf
file.
5. Restart the Gnome Display Manager and enable Xvnc by running the following commands:
svcadm restart gdm
svccfg -s x11-server setprop options/tcp_listen=true
svcadm enable xvnc-inetd
Note:
You may uninstall the slim_install package if required.To do so,run the following command:
pkg uninstall slim_install

Troubleshooting
Remove IPV6 entries from the hosts file under Solaris 11-TM and TP
To make JDA products work properly, remove IPV6 entries from hosts file.
1. Run the following command to open the hosts file.

root@machinename:~# cat /etc/hosts
Note: Contact your system administrator to know the format of existing IPV6 entries. For
example, they may display in the hosts file as:
• ::1 machinename localhost
• 127.0.0.1 machinename localhost loghost
2. Create a backup of the existing hosts file for future reference, if there are any IPV6 entries.To do
so,run the following command:
root@machinename:~#cat /etc/hosts.bkup
3. Remove IPV6 entries from the existing hosts file and save it.

Software ordering information
Appendix A. Software ordering information

The following is a list of suppliers for software used with Transportation Manager and not included on
the product installation package. If you have any questions, log on to the JDAUser website
(http://www.jdauser.com) or contact your account representative.
3rd Party Software Supplier / Phone # Website

.NET Framework Microsoft • For 64-bit, see the following
Note: .NET Framework Client Microsoft websites:
Profile and .NET Framework • website
Extended must be installed (http://www.microsoft.c
before installing Crystal om/en-
Runtime. us/download/details.asp
x?id=17718)
• website
(http://www.microsoft.c
om/en-
us/download/details.asp
x?id=22833)
Acrobat Reader Adobe Adobe website
(http://www.adobe.com).
Crystal Reports Business Objects SAP website
(http://www.sap.com/solu
tions/sme/business-
intelligence-crystal-
solutions.epx).
RateWare Server and SMC3 Mike Davidson: 770- SMC3 website
RateWareXL 486-5800 (http://www.smc3.com).
FaxMaker for Exchange GFI Fax & Voice USA Faxmaker website
(http://www.faxmaker.com
).
IntelliRoute, MileMaker Rand McNally Rebecca Rand McNally website
Drake: 847-329-6776 or (http://www.randmcnally.c
Commercial Transportation om/rmc/tdm/tdmHome.jsp
No.: 800-234-4069 ?cmty=0).
JDK/JRE (Windows or Sun Microsystems Oracle website

Solaris) (http://java.sun.com/prod
ucts/archive).
JAVA SDK (with JRE) IBM IBM website (http://www-
Note: You will need an IBM 128.ibm.com/developerwor
ID and Password to access ks/java/jdk/aix/service.ht
this download. ml).
Oracle Server Oracle Oracle website

(http://www.oracle.com).
PC*Miler ALK Associates Alice Elgrim: PC*Miler website
877-573-0138 (http://www.pcmiler.com).
Sun Java System Web Sun Microsystems Oracle website
Server (http://www.sun.com/soft
ware).
VMware VMware VMware website

Software ordering information
3rd Party Software Supplier / Phone # Website

(http://www.vmware.com).
WebLogic Server Oracle Oracle website
(http://www.oracle.com/u
s/products/middleware/ap
plication-
server/index.htm).
WebSphere Application IBM IBM website (http://www-
Server 01.ibm.com/software/webs
phere/?pgel=ibmhzn&cm_r
e=masthead-_-products-_-
sw-websphere).
iFMI Server CHAINalytics Chainalytics website
(http://www.chainalytics.c
om/what-we-do/supply-
chain-intelligence/freight-
market-intelligence-
consortium/).

Server platform information
Appendix B. Server platform information

Certain servers have not been ported to UNIX due to third party software dependencies on Windows,
or a lack of demand for some functions on UNIX.
A few server functions which have been ported might still need to run on Windows if an interface is
required to Windows-only third party software.
These combinations are detailed below:
Servers available on both UNIX and Windows

The default configuration for UNIX environments is to run all servers listed in the following table on
UNIX. Contact JDA Support if you have a UNIX application server and need to configure Transportation
Manager to run any servers besides Distance, Reporting, or Transportation Planner on a Windows
machine. In this case, you need to confirm that your proposed configuration is tested and supportable.
Server Function Executable Name*

Administration AdmSrv.exe
CarrierSequentialTenderingServ AutoTdrSrv.exe
er
BusinessProcessModelServer BObjSrv.exe
Distance Calculator DistSrv.exe
FinancialAndBatchServer FinSrv.exe
Infrastructure Services CISServer.exe
Interface
Monitoring Server (Optional) MntrIntprtAgent.exe
Notification Agent NotifAgent.exe
Report Distribution DistribRptSrv.exe
TM Optimizer Request Server TMOptRequestServer.exe
Web Application Runs within WebLogic (java
process)
Note: * There is no .exe extension on UNIX systems. For example, FinSrv.exe (Windows naming
convention) is called FinSrv on UNIX.
For UNIX environments, the Distance Calculator should be run on the UNIX machine if you are using
PC*Miler (North America) or i2Distance as your distance engine. For any other distance engine, you
must run on Windows due to third party software restrictions.
Also for UNIX environments, Transportation Planner should be run on the UNIX machine unless you
need to use Czar tariffs or rating. That software is only available on Windows.
Servers available only on Windows

The remaining server functions are available only on Windows for this release. This includes the main
Report Server (as opposed to the Report Distribution Server), which must run on Windows. This is the
only platform available for the Crystal Reports report generation engine.

Troubleshooting
Index
A
Access the TM-Web interface on WebLogic • 159, 160
Access the TM-Web interface on WebSphere • 159, 160
Allow monitoring access to a user group • 149
Alternative configurations • 97
B
Begin the refreshJSFiles process • 53
C
Change default error message • 53, 62
Change the date format and presentation of days/hours • 53, 62
Change the WebLogic configuration using TM_Web_Config • 50, 109
Complete the bootstrap schema configuration • 20
Complete the refreshJSFiles process • 63
Complete the upgrade • 25
Complete the Web interface installation • 64, 110
Configure different tablespace • 15
Configure for different tablespace • 16
Configure for different tablespaces • 14
Configure parameter set • 35
Configure preferred countries • 53, 62
Configure SSL transport • 100
Configure the Distance Calculator server • 20, 26, 27, 28
Configure the Distributed Service Coordinator (DSC) • 44, 47, 93, 94, 99, 100
Configure the monitoring server • 46
Configure the Oracle server • 22
Configure the Process Monitor • 29, 98
Configure TP on AIX • 41, 85
Configure TP on Solaris • 39, 80
Configure TP on Windows • 36
Configure WebLogic CLASSPATH information for CIS port • 113, 115
Create tablespaces • 14, 15, 16
Customize the Web interface banner for announcements • 53
D
Deploy applications from the WebLogic console • 114, 116
Deploy JDA applications in Production mode • 113
Deploy JDA Applications in Production Mode • 115
Deploy JDA Transportation Manager ABPP • 66, 90, 91
F
For older schemas • 22

Troubleshooting
I
Install distance calculation engines • 17
Install Oracle database scripts • 21, 27
Install PC*Miler on Windows systems • 102
Install Routing and Rating/Optimizer engine instances on Windows • 73, 79, 84
Install shipment scheduler engine instances on Windows • 73
Install Transportation Manager server • 17
Install-time licensing • 70, 77, 82
M
Materialized views • 27
Modify server autostart settings • 92, 98, 101
O
Oracle Client configuration requirements (on Application servers) • 17
Oracle server configuration requirements • 18
P
Preconfigured servers • 153
Prepare to install the Web interface • 66
Purge cached distances • 154
R
Remove a previous deployment • 58, 60, 110
Remove the JDBC provider information • 58
Run the TP installation program on AIX • 117
S
Sample Scripts • 8
Send reports and notifications through fax and email • 98, 158
Server logging levels • 154, 155, 159
Server platform information • 94
Servers configuration • 153
Single active instance servers • 98, 101
Software ordering information • 6, 45
SSL from Java clients to TM servers • 108
Standard Oracle requirements • 3, 27
Start the DSC • 98
Start the Web interface Installation • 52, 62
Start TP as an enterprise application • 118
T
TM optimizer request server • 99
Topology • 44
Transportation Manager product integrity • 3
U
Uninstall TP programs on AIX • 42
Troubleshooting
Uninstall TP programs on Solaris • 40

Uninstall TP programs on Windows • 38
Upgrade existing schemas • 17
Use parameter sets • 35, 99, 102
W
Workaround for Java Strong encryption error • 111

Transportation Install Admin Guide 8.1

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Transportation Install Admin Guide 8.1

Enviado por

Direitos autorais:

Formatos disponíveis

Installation/Administration

Modifications to the contents of this document

Rights to the functionality of this document

Software implementation advisement

Provide feedback on this document

Chapter 2. Pre-requisites ................................................................................................. 6

Install the TM RIA-Web interface for WebSphere .......................................................... 65

Chapter 5. Post-installation ........................................................................................... 92

Set up the TP help for deployment ................................................................... 116

Chapter 6. Utilities and common tasks ........................................................................ 149

Chapter 7. Troubleshooting ......................................................................................... 161

Appendix A. Software ordering information................................................................. 163

Appendix B. Server platform information .................................................................... 165

Index ........................................................................................................................... 166

Task Description Required or Optional

Server hardware must consist of a minimum of two server machines:

• one for the RDBMS

Minimum Windows P3-1000+ 2 GB 1 GB *

WAN: Browser clients

JDA Transportation Installation/Administration Guide 2

Test environments and Test plans

Fault tolerance, backup and recovery, and disaster recovery

JDA Transportation Installation/Administration Guide 3

System Administrator (UNIX and Windows)

The major Transportation Planner components are:

• Routing and Rating Server

JDA Transportation Installation/Administration Guide 4

• Shipment Scheduler, in this deployment, the installed components are:

JDA Transportation Installation/Administration Guide 5

Standard Oracle requirements

Transportation Manager product integrity

Schema naming conventions

Standard schemas Optional additional schemas

Name Purpose Name Purpose

jdatm_train Training jdatm_at Acceptance Testing

JDA Transportation Installation/Administration Guide 6

Oracle Client configuration requirements (on Application servers)

Oracle server configuration requirements

JDA Transportation Installation/Administration Guide 7

• shared_pool_size: Minimum: 150 MB, Recommended: 150+ MB (see note below)

Oracle configuration recommendations

Materialized views and import errors

The dump files do not include active materialized views.

autoextend on next 512m maxsize unlimited

extent management local

uniform size 1m;

• create tablespace i2tm_pstl_data

reuse extent management local uniform size 256k

segment space management auto ;

JDA Transportation Installation/Administration Guide 9

• create tablespace i2tm_pstl_index

reuse extent management local uniform size 256k

segment space management auto ;

• create tablespace i2tm_data

reuse autoextend on next 100m maxsize unlimited

extent management local uniform size 256k

segment space management auto ;

• create tablespace i2tm_index

reuse autoextend on next 100m maxsize unlimited

extent management local uniform size 256k

segment space management auto ;

Create Schema: jdatm_crp

Application schema for Transportation Manager CRP

create user jdatm_crp identified by jdatm_crp