tibco fulfillment order management installation and ......tib_af_3.0.2_readme.txt file. install and...

TIBCO® Fulfillment Order ManagementInstallation and ConfigurationSoftware Release 3.0.2June 2016

Two-Second Advantage®

mkentgen

Typewritten Text

mkentgen

Typewritten Text

Document Updated: August 2016

mkentgen

Typewritten Text

mkentgen

Typewritten Text

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCHEMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (ORPROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THEEMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANYOTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS ANDCONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTEDSOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THECLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOADOR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE)OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USERLICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THESOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, ANDYOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BEBOUND BY THE SAME.

This document contains confidential information that is subject to U.S. and international copyright lawsand treaties. No part of this document may be reproduced in any form without the writtenauthorization of TIBCO Software Inc.

TIBCO, Two-Second Advantage, TIBCO ActiveMatrix BusinessWorks, TIBCO Runtime Agent, TIBCOAdministrator, and TIBCO Enterprise Message Service are either registered trademarks or trademarksof TIBCO Software Inc. in the United States and/or other countries.

Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform EnterpriseEdition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks ofOracle Corporation in the U.S. and other countries.

All other product and company names and marks mentioned in this document are the property of theirrespective owners and are mentioned for identification purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOTALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASEDAT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWAREVERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.

THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSOR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICALERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESECHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCOSOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S)AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.

THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY ORINDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE,INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

Copyright © 2010-2016 TIBCO Software Inc. All rights reserved.

TIBCO Software Inc. Confidential Information

2

TIBCO® Fulfillment Order Management Installation and Configuration

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Operating System and Database Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Required Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Required Third-Party Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Installing JDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Installing ANT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Required TIBCO Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

TIBCO Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Installation Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installation Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installer Disk Space Requirements in Temporary Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Installation Registry History and Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Installation and Deployment Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Typical or Custom Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Installation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Installing TIBCO Fulfillment Order Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Installing in GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Installing in Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Installing in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Uninstalling TIBCO Fulfillment Order Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Post-Installation Task 1: Backing up the Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Post-Installation Task 2: Backing up the OMS Database Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Post-Installation Task 3: Deleting Content from the Webapps Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Post-Installation Task 4: Copying Files into the Webapps Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Post-Installation Task 5: Updating the ConfigValues_OMS.xml File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Post-Installation Task 6: Updating the ConfigValues_AOPD.xml File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Post-Installation Task 7: Updating the OMSServerLog4j.xml File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Post-installation Task 8: Upgrading the OMS Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Post-Installation Task 9: Migrating the Non-Partitioned OMS Database into the Partitioned OMS Database . . . . . . . . . . . . . 26

Post-Installation Task 10: Upgrading the TIBCO EMS Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

3


Post-Installation Task 11: Starting the TIBCO FOM Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Configuring and Verifying Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Copying WAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Restarting the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Verifying Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

TIBCO Fulfillment Order Management Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Upgrading from FOM 2.1.2 HF5 to FOM 3.0.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Prepare TIBCO Fulfillment Order Management 2.1.2 for the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Backup the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Install TIBCO Fulfillment Order Management 3.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35



Possible Changes in Process Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Perform the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Start TIBCO Fulfillment Order Management 3.0.2 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Upgrading from FOM 3.0.1 to FOM 3.0.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Prepare TIBCO Fulfillment Order Management 3.0.1 for the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Backup the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41


Possible Changes in Process Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Perform the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Start TIBCO Fulfillment Order Management 3.0.2 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Installation FAQs and Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

4


Figures

TIBCO Installation Welcome Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

TIBCO Installation Home Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

TIBCO Installation Components Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Pre-Install Summary Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Post-Install Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

JMS Connection Parameters for Orchestrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Starting Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Order View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Plan Grid View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Plan Gantt View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

5


Installation Overview

TIBCO® Fulfillment Order Management provides advanced order provisioning and fulfillment features.

This chapter provides information about the system requirements in terms of operating systems anddisk space, the recommended setup for TIBCO Fulfillment Order Management installation, variablesand properties required, and important files necessary to perform the post-install log analysis.

The following are links to detailed information for preinstall requirements and settings, and the installand post-install steps.

Prerequisites

TIBCO Fulfillment Order Management 3.0.2 requires TIBCO Fulfillment Order Management 3.0.1 to beinstalled on the system. If the 3.0.1 version is not already installed on your system, install TIBCOFulfillment Order Management 3.0.1 first, before proceeding to install the 3.0.2 version. For details toinstall TIBCO Fulfillment Order Management 3.0.1, refer to TIBCO Fulfillment Order Management 3.0.1Installation Guide https://docs.tibco.com/products/tibco-fulfillment-order-management-3-0-1.

Preinstall

To ensure that you have a good experience installing TIBCO Fulfillment Order Management, it isalways recommended to check whether your computer is ready for the installation. The pre-installsection gives you the prerequisites to install TIBCO Fulfillment Order Management.

1. Operating System and Database Requirements on page 6: This section provides you withinformation about the platforms that TIBCO Fulfillment Order Management supports.

2. Required Products on page 7: TIBCO Fulfillment Order Management requires a number ofsoftware components to be installed. For a complete list of versions and platforms supported, seethe TIB_af_3.0.2_readme.txt file. Install and configure them in the mentioned order.

3. Installation Options on page 9: This section provides you with information about the options forinstalling TIBCO Fulfillment Order Management.

4. Installation Registry History and Log Files on page 11: These files inform you about:

a. The log files, which contain important data about installation and uninstallation of TIBCOFulfillment Order Management.

b. Where you can find the log files, and post-installation.

c. Nomenclature of the log files.

d. Details about the log data.

Install

● Installation and Deployment Options: TIBCO Fulfillment Order Management supports differentinstallation modes. This chapter provides you with information about the available installationmodes, the flow of the installation, and post-install steps you need to perform.

● Installing TIBCO Fulfillment Order Management: Step-by-step instructions are provided to helpyou install TIBCO Fulfillment Order Management using different installation modes. This chapteralso describes the steps required to uninstall TIBCO Fulfillment Order Management.

Post-install

Post-Installation Tasks on page 21: After you complete the installation of TIBCO Fulfillment OrderManagement, you should complete the post-installation tasks. The post-installation tasks list theconfiguration and deployment steps of the components that you have just installed.

Operating System and Database RequirementsTIBCO Fulfillment Order Management supports the following platforms and databases:

6


https://docs.tibco.com/products/tibco-fulfillment-order-management-3-0-1

Operating System

Red Hat Enterprise Linux Server 6.x, 7.x 64-bit on x86-64

Non-Partitioned Database

Oracle 11g SE and above (Oracle 11.2.x), single and RAC

Oracle 12c SE and above (Oracle 12.1.x), single and RAC

Partitioned Database

Oracle 11g EE (Oracle 11.2.x), single and RAC

Oracle 12c EE (Oracle 12.1.x), single and RAC

For version number details, refer to the product readme document.

Required ProductsYou must install the third-party products and TIBCO products listed in this section.

Required Third-Party ProductsThe following table lists the required third-party products:

Required Third-Party Products

Products Version Purpose

JDK 1.8 (or greater) A Java Development Kit (JDK) is a program developmentenvironment which you can use for writing Java applets andapplications.

This is required for OMS and Jeopardy Management System(henceforth, referred to as JeoMS).

See below the JDK installation details.

OracleDatabase

11g Release 2and 12c (orgreater)

An Oracle database is required by Fulfillment OrderManagement to store data.

The Oracle server can be installed on a separate machine basedon the installation requirement.

Databasedriver

ojdbc6.jar andojdbc7.jar for11g Release 2

This is required on the machine where Fulfillment OrderManagement is installed.

The driver is used to connect to and query the Oracle server.

The driver (ojdbc6.jar) can be found in the Oracle databaseinstallation or it can be downloaded directly from the Oraclewebsite.

7


Products Version Purpose

Hibernate 3.6.9.Final The installer downloads this JAR automatically depending onthe selection option.

If the machine where you install Fulfillment Order Management,does not have Internet connection, then you will have todownload the file separately and make it available to themachine where Fulfillment Order Management is going to beinstalled. The file is platform independent. The URL where tofind the file is: product_tibco_hibernate_3.6.9.001.zip.

Note where you dropped the zip, the installer, during theinstallation, will ask you where to find the file.

GnomeBinding

3.7.2 The installer downloads this file automatically depending on theselection option.

If the machine where you install Fulfillment Order Management,does not have Internet connection, then you will have todownload the file separately and make it available to themachine where Fulfillment Order Management is going to beinstalled. The file is platform dependent. The URL where to findthe files is: product_tibco_eclipse_lgpl_rcp_3.7.2.001_linux24gl23_x86_64.zip.

Note where you dropped the zip, the installer, during theinstallation, will ask you where to find the file.

ANT 1.8 (or greater) This build tool is required to run the Deployment Tool(command-line).

You also need to download and copy the ant-contrib-<version>.jar file to the $ANT_HOME/lib directory.

See below the JDK installation details.

For product version details, you can also refer to the Fulfillment Order Management readme file.

Installing JDK

Create the following environment variables after installing JDK:

● Set JAVA = /usr/java/jdk1.8.0_11/bin/java● Set JAVA_HOME = /usr/java/jdk1.8.x● In the PATH variable, add JAVA_HOME/bin.

Installing ANT

Create the following environment variables after installing ANT:

● Set ANT_HOME for example /usr/ant/1.8.x● In the PATH variable, add ANT_HOME/bin.

Required TIBCO ProductsThe Fulfillment Order Management requires some TIBCO products.

8


http://public.tibco.com/pub/tibco_oss/hibernate/product_tibco_hibernate_3.6.9.001.zip

http://public.tibco.com/pub/tibco_oss/eclipse_lgpl/product_tibco_eclipse_lgpl_rcp_3.7.2.001_linux24gl23_x86_64.zip

Required TIBCO Products for TIBCO Fulfillment Order Management

The following table lists the required TIBCO products for TIBCO Fulfillment Order Management:

The TIBCO Fulfillment Order Management installer does not verify if the required products areinstalled. Nonetheless, those products have to be installed before TIBCO Fulfillment OrderManagement is installed.

It is possible to install several TIBCO products at once, and let the installer installs the products in theright order. Just unzip all the TIBCO products in a single directory. The only caveat is that some TIBCOproducts use a later version of the TIBCO Universal installer. So, if you decide to install all the productat once, make sure to unzip TIBCO Fulfillment Order Management (that uses the latest TIBCOuniversal installer version) the last.

Required TIBCO Products for TIBCO Fulfillment Order Management

Product & Version Purpose For more information, refer to:

TIBCO EnterpriseMessage Service™ 8.3.x

Standards-based messagingsoftware that can serve as thebackbone of an SOA byproviding Java Message Service(JMS)-compliantcommunications across a widerange of platforms andapplication technologies.

EMS is a pre-requisitebut is not a part of theTIBCO FulfillmentOrder Managementproduct license.

TIBCO Enterprise Message Service™Installation

Installation OptionsDepending on how you want to use TIBCO Fulfillment Order Management there are different ways toinstall it.

First, there is the concept of TIBCO environment that you need to understand before we explain thedifferent ways to use this application and the corresponding installation options.

TIBCO EnvironmentThe TIBCO environment is a directory where one or more TIBCO products are installed. It is also calledinstallation directory or TIBCO home, because it will correspond to the environment variable$TIBCO_HOME.

The installer prompts you to specify or create a TIBCO environment. An environment consists of aname, description, and directory on the disk. Each TIBCO environment is isolated so the same softwarecan be installed into the different environments safely (e.g. different versions of the same software). Youcan also install multiple TIBCO products into the same environment.

Each time you run the installer, it will ask you which TIBCO environment to use. An installer installs oruninstalls a product from a TIBCO environment. If you want to install several times a same product,then you will have to do it in different TIBCO environment. Each time, you will have to run the installer(an installation session only deals with one single TIBCO environment).

Before installing a product in a particular TIBCO environment, the installer verifies that all thedependencies are already installed in that TIBCO environment.

9


By default the installer suggests to use the following directories as TIBCO environment (i.e.TIBCO_HOME):

● For root users, the default installation directory is /opt/tibco.

● For non-root users, the default installation directory is /myhome/tibco, where myhome is the homedirectory of the user.

You can choose any other directory. For performance reasons, it is recommended to install the producton a local disk (as opposed to network mounted or NFS partition).

Installation ScenarioTIBCO Fulfillment Order Management is made of several sub-systems or components. Each of thosecomponents have a specific responsibility. Here is a brief list of the major components:

● Order Management Server

● Offer and Price Engine

● Order Capture System

● Orchestrator

● Automated Order Plan Development

For a complete list of all the components and their detailed role and relationships, see TIBCO FulfillmentOrder Management Concepts and Architecture and TIBCO Fulfillment Order Management User's Guide.

Scenario

The TIBCO environment has TIBCO Enterprise Message Service (EMS) installed, before TIBCOFulfillment Order Management gets installed.

After the application is installed, the installation will look like this:

Installation Environment VariablesRecommended Environment Variables Setup

It is recommended that you set the following environment variables where Fulfillment OrderManagement is installed:

Environment Variable Value

export AF_HOME $TIBCO_HOME/af/3.0

10


Environment Variable Value

exportAF_CONFIG_HOME

$AF_HOME/config

export ORACLE_HOME /usr/local/app/oracle/product/<ORACLE_VERSION>/db_1

export JAVA_HOME /local/affuser/jdk1.8.x

export ANT_HOME /local/affuser/apache-ant-1.8.x

export EMS_HOME $TIBCO_HOME/ems/8.3

export PATH $ANT_HOME/bin:$ORACLE_HOME/bin:$JAVA_HOME/bin:$EMS_HOME/

bin:$PATH

export NODE_ID Member1

exportLD_LIBRARY_PATH

$ORACLE_HOME/lib:$LD_LIBRARY_PATH

export CLASSPATH $ANT_HOME/lib:$CLASSPATH

exportAF_OMS_CONTEXT_URL

http://<host>:<port>/omsServer

Host/port - OMS Server IP and its port details.

The context URL is used if it requires to create users with appropriateroles by the $AF_HOME/bin/userservice.sh utility.

Installer Disk Space Requirements in Temporary AreaThis section describes the temporary disk space requirements for TIBCO Fulfillment OrderManagement.

Unix Platform

The installer launcher first extracts a Java Virtual Machine (JVM) in a temporary directory and uses thisJVM to launch itself. The size of the extracted JVM differs from platform to platform.

On UNIX platforms, the following disk space is required in the temporary area:

● 256 MB of free disk space in /tmp

If your system does not have sufficient free disk space in the above temporary area, you can still run theinstaller with a different temporary area by using the following option when starting the installer:

install_package_name.bin -is:tempdir /new_tmp

where /new_tmp has sufficient free disk space.

Installation Registry History and Log FilesInstallation and uninstallation log files are in the $HOME/.TIBCO directory within the installer’s userhome directory. The files use this format:

● Install log

.TIBCO/install_<yyyy-mm-dd.hhmmss>/

tibco_universal_installer.<affuser>_install.log

11


● Uninstall log

.TIBCO/uninstall_<yyyy-mm-dd.hhmmss>/

tibco_universal_installer.<affuser>_uninstall.log

The installation and uninstallation log files log the history and maintain the registry files in the $HOME/InstallShield directory.

Do not edit, rename, move, or remove the files in the $HOME/InstallShield directory.

12


Installation and Deployment Options

The following table summarizes the tasks for installing, configuring, and verifying TIBCO® FulfillmentOrder Management.

Task Instructions Description

Install® TIBCO FulfillmentOrder Management

Install from one of theavailable options:

● GUI Mode

● Console Mode

● Silent Mode

TIBCO Fulfillment OrderManagement supports installationusing GUI mode, Console modeand Silent mode.

You can use any one of the modesto install TIBCO Fulfillment OrderManagement.

Complete the post-installation steps

For details, see Post-Installation Tasks on page21.

After you complete the TIBCOFulfillment Order Managementinstallation, you need to performsome post-installation steps.

Verify the installation For details, see VerifyingInstallation on page 27.

This section is about verifying yourinstallation by performing a fewsimple tests to see that TIBCOFulfillment Order Management isproperly installed with appropriateconnectivity between its variouscomponents.

Typical or Custom InstallDownload the TIBCO Fulfillment Order Management installation package or install the componentsfrom a CD. The installer prompts you to accept the license agreement, then to choose to perform atypical install or custom install (full installer only).

● The Typical installation type installs all the components in the package on the specified platform.

● The Custom installation type allows you to select one or more components to be installed.

Installation ModesThe installer allows you to run in the following modes:

● GUI Mode

● Console Mode

● Silent Mode

GUI ModeIn GUI mode, the installer presents panels that allow you to make choices about product selection,product location, and so on. When you run the installer by double-clicking on the icon, GUI mode isused.

For more information, refer to Installing in GUI Mode on page 15.

13


Console ModeConsole mode allows you to run the installer from the command prompt or terminal window.

For more information, refer to Installing in Console Mode.

Silent ModeSilent mode either installs using default settings or uses a response file that was saved during an earlierinstallation. Silent mode installs without prompting you for information.

For more information, refer to Installing in Silent Mode.

14


Installing TIBCO Fulfillment Order Management

This section describes the installation and uninstallation of TIBCO® Fulfillment Order Managementusing TIBCO Universal Installer.

Installing in GUI ModeThe following procedure explains how to install TIBCO® Fulfillment Order Management in GUI mode:

1. Open the physical media or download the TIBCO Fulfillment Order Management product package.

2. Extract the TIBCO Fulfillment Order Management product archive file to a temporary directory.

3. Navigate to the temporary directory that contains the universal installer.

4. Run TIBCOUniversalInstaller-(platform).bin (the name of the executable depends on the platform,the ends with the .bin extension).

5. Review the information in the Welcome dialog, and click the Next button.

TIBCO Installation Welcome Screen

6. The License Agreement dialog appears.

Choose "I accept the terms of the license agreement" and click the Next button. The InstallationProfile Selection dialog appears. If you do not agree to the terms of the license agreement, click theCancel button to exit from the installation process.

7. The TIBCO Installation Home dialog appears.

Specify an installation environment and click the Next button.

15


TIBCO Installation Home Screen

You can choose to either create a new TIBCO installation environment or select an existingenvironment. A TIBCO installation environment is used for software installations and consists of aDirectory (the path where the product would be installed) and Name fields. Products installed intodifferent installation environments do not share components; therefore you can keep productinstallations completely isolated from each other.

Create a new TIBCO_HOME

If this is the first time that you are installing a TIBCO product using the Universal Installer, youmust create an installation environment by specifying the following:

● Directory: The root directory into which all TIBCO products are installed. Individual productswill use sub-directories. Type a path or click Browse to specify the path or accept the defaultlocation.

The path cannot contain special characters such as "*", "#", "?", ">", "<", "%", "&", "$", "`" or "|".The path cannot be the same as the path of an existing environment.

● Name: Identifies the installation environment. The name cannot contain special characters suchas "*", "?", ">", "<", ":", "|", "/", "\", or quotation marks (").

Use an existing TIBCO_HOME

If you have previously installed a TIBCO product using the Universal Installer, you can install theproduct into a previously created installation environment (by selecting the environment from thelist). If you do this, the Directory and Name fields are populated automatically and cannot beedited.

8. You can choose an installation profile from the list on the left. Select Typical to install all the featuresor choose the features to install by selecting Customize Installation. After making your choice, clickthe Next button.

16


● Core Components

Order Management Server, Offer and Price Engine, Automatic Order Plan Development,Orchestrator, Jeopardy Management System, User Interface, etc.

● Samples

Samples to help users start with FOM

● Optional Component added during installation customization

Order Capture System

TIBCO Installation Components Screen

9. The Configurator Settings dialog is displayed.

The Configurator is a configuration tool used to do advanced configuration for this application. It isa web-based GUI. You can configure during the installation, the port numbers to access theConfigurator later.

Specify the Configurator server properties and click the Next button.

10. After the installer configures your installation choices, the Pre Install Summary dialog is displayed.Review the information displayed in the dialog and make sure that it is correct.

If you want to change any of your choices, click the Back button to step back through the dialogs tothe appropriate point. You can then continue the installation process from that point.

17


Pre-Install Summary Screen

11. When you are satisfied with your choices, click the Install button.

12. The Post Install Summary dialog appears which summarizes the installation process. Click theFinish button to complete the installation process and close the installer window.

18


Post-Install Screen

13. Complete the post-installation tasks described in Post-Installation Tasks on page 21.

Installing in Console ModeThe following procedure lists the steps to install TIBCO Fulfillment Order Management in consolemode:



3. Using a console window, navigate to the temporary directory that contains the universal installerand run the installer using this command line:bash-3.00$ ./TIBCOUniversalInstaller-<os>.bin -console

4. Complete the installation by responding to the console window prompts.

Installing in Silent ModeThe TIBCOUniversalInstaller.silent file is packaged in the directory that contains the universalinstaller. Edit the file with information for your environment before launching the silent installation.The file includes comments that describe the installation properties you can set.

While you can use the TIBCOUniversalInstaller.silent file, it is a good practice to copy the file to adifferent name and then edit the file for silent mode. Modify the following details in the silent file:

● installationRoot

● Set the createNewEnvironment value to be false.

● environmentName

19


● environmentDesc

Change other optional parameter values as required.

Save the silent file.

If errors occur during installation, they will be listed in the installation log file, which is located in the$HOME/.TIBCO directory.

The following procedure lists the steps to install TIBCO Fulfillment Order Management in silent mode.



3. Using a console window, navigate to the temporary directory that contains the universal installer.

4. Copy the TIBCOUniversalInstaller.silent file and name the file.

5. Using a text editor, open the TIBCOUniversalInstaller.silent file, and update the installlocation and the list of features to install.

6. Run the installer:

TIBCOUniversalInstaller-<os>.bin -silent

When installation completes, a line similar to the following is written to the installer log file:

Install, com.tibco.installer.util.TIBCOInstaller, dbg.Debug, The installation has

completed. Please check the log file for additional information.

7. Complete the post-installation tasks described in Post-Installation Tasks on page 21.

Uninstalling TIBCO Fulfillment Order ManagementTo uninstall Fulfillment Order Management from the supported UNIX platform, navigate to the$TIBCO_HOME/tools/universal_installer directory and run the TIBCOUniversalInstaller-<os-type>.bin script.

20


Post-Installation Tasks

This section gives an overview of the steps you need to perform upon successful installation of TIBCO®

Fulfillment Order Management. Each post-installation step given below must be finished before youperform the next step.

Complete the following steps in the given order to configure the installed components:

1. Back up the files.

2. Back up the OMS database Schema.

3. Delete content from the webapps directory.

4. Copy files into the webapps directory.

5. Update the ConfigValues_OMS.xml file.

6. Update the ConfigValues_AOPD.xml file.

7. Update the OMSServerLog4j.xml file.

8. Upgrade the OMS database.

9. Migrate the non-partitioned database into the partitioned OMS database.

10. Upgrade the TIBCO EMS channel.

11. Start the TIBCO FOM engines.

Use the HTML documentation to copy and past code snippets in to the XML files.

Post-Installation Task 1: Backing up the FilesBack up the following file located in the $AF_HOME/config/ directory:

● ConfigValues_OMS.xml

● OMSServerLog4j.xml

● ConfigValues_AOPD.xml

Back up the following war files from the Apache Tomcat instance:

● omsServer.war

● omsui.war

● aopd.war

● ope.war

● ocs-app.war

● dashboard.war

Post-Installation Task 2: Backing up the OMS Database SchemaBack up the OMS database schema so that the OMS database can be restored if the service pack has tobe uninstalled for some reason.

Post-Installation Task 3: Deleting Content from the Webapps DirectoryDelete the following artifacts in the webapps ($AF_HOME/apache-tomcat-<version>/webapps)directory from all the Apache Tomcat instances in the cluster:

21


● omsServer (directory)

● omsServer.war (file)

● omsui (directory)

● omsui.war (file)

● aopd (directory)

● aopd.war (file)

● ope (directory)

● ope.war (file)

● ocs-app (directory)

● ocs-app.war (file)

The ocs-app.war file must be deleted under the OCS tomcat ($AF_HOME/ocs-apache-tomcat-<version>/webapps).

● dashboard (directory)

● dashboard.war (file)

The aopd.war file and the aopd directory will exist only if the AOPD component is deployed in astandalone mode. Also, the ope.war file and the ope directory will exist only if the OPE component isdeployed in a standalone mode.

Post-Installation Task 4: Copying Files into the Webapps DirectoryCopy the following files into the webapps ($AF_HOME/apache-tomcat-<version>/webapps) directoryfrom all of the Apache Tomcat instances in the cluster:

● $AF_HOME/oms/webapps/omsServer.war

● $AF_HOME/oms/webapps/omsui.war

● $AF_HOME/oms/webapps/aopd.war (Only if the AOPD component is deployed in standalone mode)

● $AF_HOME/oms/webapps/ope.war (Only if the OPE component is deployed in standalone mode)

● $AF_HOME/oms/webapps/ocs-app.war (The ocs-app.war file must be copied under the OCStomcat ($AF_HOME/ocs-apache-tomcat-<version>/webapps)

● $AF_HOME/oms/webapps/dashboard.war

The aopd.war file should be deployed only if the AOPD component is to be deployed in a standalonemode. Also, the ope.war file should be deployed only if the OPE component is to be deployed in astandalone mode.

Post-Installation Task 5: Updating the ConfigValues_OMS.xml FileAdd properties from the Configurator application itself by selecting the category and Add NewProperty, or manually update the $AF_HOME/config/ConfigValues_OMS.xml file.

When migrating from previous TIBCO Fulfillment Order Management releases, you must already havemade the changes to the ConfigValues_OMS.xml file up to version 3.0.1 of TIBCO Fulfillment OrderManagement.

1. Add the following entries within the existing parent category "Orchestrator Configuration" and sub-category "Generic Configuration" under the cluster configuration:

● <ConfValue description="Enable JMS connection Check" isHotDeployable="true" name="Enable JMS connection Check" propname="com.tibco.fom.orch.jms.jndiLookup.connection.enableJMSConnectionVali

22


dation" readonly="false" sinceVersion="3.0" visibility="Basic"> <ConfString default="false" value="false"/></ConfValue>

● <ConfValue description="Threshold for invalidating the Resource Cached Data" isHotDeployable="true" name="Threshold for invalidating the Resource Cached Data" propname="com.tibco.fom.orch.resource.connection.invalidateCacheStatusdataThreshold" readonly="false" sinceVersion="3.0" visibility="Basic"> <ConfString default="20000" value="20000"/></ConfValue>

● <ConfValue description="Executor Processor Threads for DB Ping" isHotDeployable="true" name="Executor Processor Threads for DB Ping" propname="com.tibco.fom.orch.resource.connection.executorProcessorThreadCount" readonly="false" sinceVersion="3.0" visibility="Basic"> <ConfString default="5" value="5"/></ConfValue>

● <ConfValue description="JMS/DB connection check Monitor Interval in milliseconds" isHotDeployable="true" name="JMS/DB connection check Monitor Interval in milliseconds" propname="com.tibco.fom.orch.jms.health.intervalMonitoring" readonly="false" sinceVersion="3.0" visibility="Basic"> <ConfString default="1500" value="1500"/></ConfValue>

● <ConfValue description="Enable Concurrent Order Request Detection" name="Enable Concurrent Order Request Detection" propname="com.tibco.af.oms.submitorder.isDuplicateOrderRequestValidationEnabled" readonly="false" sinceVersion="3.0" visibility="Basic"> <ConfString default="false" value="false"/></ConfValue>

● <ConfValue description="Maximum number of milestones coresponding to StateMachine to be kept in Heap Memory" isHotDeployable="true" name="Maximum number of milestones coresponding to StateMachine to be kept in Heap Memory" propname="com.tibco.fom.orch.maxNoMilestonesLoadedinMemory" readonly="false" sinceVersion="3.0" visibility="Basic"> <ConfString default="0" value="0"/></ConfValue>

● <ConfValue description="The number of threads to be created in Orchestrator for shutdown task" name="Shutdown Threads Count" propname="com.tibco.fom.orch.shutdownThreadsCnt" readonly="false" sinceVersion="3.0" visibility="Basic"> <ConfString default="10" value="10"/></ConfValue>

● <ConfValue description="Enable idle time after Model loading" isHotDeployable="true" name="Enable idle time after Model loading" propname="com.tibco.fom.oms.modelLoadingMaxIdle" readonly="false" sinceVersion="3.0" visibility="Basic"> <ConfBool default="false" value="false"/></ConfValue>

● <ConfValue description="Enable Milestone Release during activation" name="Enable Milestone Release during activation" propname="com.tibco.fom.orch.enableMilestoneReleaseDuringActivation" readonly="false" sinceVersion="2.1" visibility="Basic"> <ConfString default="true" value="true"/></ConfValue>

2. Add the following entry within the existing category "Messaging Configuration":<ConfValue description="Post Models on EMS for AOPD and OPE Disabled" name="Post Models on EMS for AOPD and OPE Disabled" propname="com.tibco.af.oms.model.ems.post.disabled" sinceVersion="3.0" visibility="Basic"> <ConfBool default="true" value="true"/></ConfValue>

3. Add the following entry within the existing category "Offline Catalog Configuration" at the clusterlevel:<ConfValue description="Enable Model Cache Persistence" name="Model Cache Persistence" propname="com.tibco.af.oms.model.cache.enabled" sinceVersion="3.0"

23


visibility="Basic"> <ConfBool default="true" value="true"/></ConfValue>

<ConfValue description="Designated model loading member instance" name="Model loading member" propname="com.tibco.af.oms.model.loading.member" sinceVersion="3.0" visibility="Basic"> <ConfString default="member1" value="member1"/></ConfValue>

4. Add the following entries within the existing parent category "Data Interfaces Configuration" andsub-category "Data Interface Flags" under the cluster configuration:<ConfValue description="Flag to enable update of UDF during order amendment." name="EnableUDFUpdateDuringAmendment" propname="com.tibco.fom.oms.tds.enable.udfUpdate.DuringAmendment" sinceVersion="2.1.2" visibility="Advanced"> <ConfString default="true" value="true"/></ConfValue>

<ConfValue description="Lock Retry Interval" name="Lock Retry Interval" propname="com.tibco.af.oms.lock.retryInterval" sinceVersion="3.0" visibility="Advanced"> <ConfNum default="5000" value="5000"/></ConfValue>

<ConfValue description="Lock Retry Count" name="Lock Retry Count" propname="com.tibco.af.oms.lock.retryCount" sinceVersion="3.0" visibility="Advanced"> <ConfNum default="5" value="5"/></ConfValue>

5. For all of the following properties, the configuration needed for the Oracle database support isdefault. Make the non-default selection for each property when you want to configure for the otherdatabase. Find and replace the following properties for the category "Data Source Configuration"and for the category "Archive Data Source Configuration":

a. Find and replace the property com.tibco.af.oms.pooledDataSource.validationQuery with thefollowing property:<ConfValue description="Pooled Data Source Validation Query" name="Pooled Data Source Validation Query" propname="com.tibco.af.oms.pooledArchiveDataSource.validationQuery" sinceVersion="2.0" visibility="Advanced"> <ConfEnum> <EnumValue default="true" selected="true" value="select 1 from dual"/> <EnumValue value="SELECT 1"/> </ConfEnum></ConfValue>

b. Find and replace the propertycom.tibco.af.oms.dataSource.pooledDataSource.connectionProperty with the followingproperty:<ConfValue description="Pooled Database Connection Property" name="Pooled Database Connection Property" propname="com.tibco.af.oms.dataSource.pooledDataSource.connectionProperty" sinceVersion="2.1" visibility="Advanced"> <ConfEnum> <EnumValue default="true" selected="true" value="oracle.jdbc.ReadTimeout=120000"/> <EnumValue value=""/> </ConfEnum></ConfValue>

6. For all of the following properties, the configuration needed for the Oracle database support isdefault. Make the non-default selection for each property when you want to configure for the otherdatabase. Find and replace the following properties for only the "Archive Data SourceConfiguration" category:

24


a. Find and replace the property com.tibco.af.oms.pooledDataSource.driverClassName with thefollowing property:<ConfValue description="Pooled Data Source Driver Class Name" name="Pooled Data Source Driver Class Name" propname="com.tibco.af.oms.pooledArchiveDataSource.driverClassName" sinceVersion="2.0" visibility="Basic"> <ConfEnum> <EnumValue default="true" selected="true" value="oracle.jdbc.driver.OracleDriver"/> <EnumValue value="org.postgresql.Driver"/> </ConfEnum></ConfValue>

b. Find and replace the property com.tibco.af.oms.pooledDataSource.url with the followingproperty:<ConfValue description="Pooled Data Source URL" name="Pooled Data Source URL" propname="com.tibco.af.oms.pooledArchiveDataSource.url" sinceVersion="2.0" visibility="Advanced"> <ConfEnum> <EnumValue default="true" selected="true" value="jdbc:oracle:thin:@//${com.tibco.af.oms.pooledDataSource.host}:${com.tibco.af.oms.pooledDataSource.port}/${com.tibco.af.oms.pooledDataSource.database}"/> <EnumValue value="jdbc:postgresql://${com.tibco.af.oms.pooledDataSource.host}:${com.tibco.af.oms.pooledDataSource.port}/${com.tibco.af.oms.pooledDataSource.database}"/> </ConfEnum></ConfValue>

c. Find and replace the property com.tibco.af.oms.pooledDataSource.validationQuery with thefollowing property:<ConfValue description="Pooled Data Source Validation Query" name="Pooled Data Source Validation Query" propname="com.tibco.af.oms.pooledArchiveDataSource.validationQuery" sinceVersion="2.0" visibility="Advanced"> <ConfEnum> <EnumValue default="true" selected="true" value="select 1 from dual"/> <EnumValue value="SELECT 1"/> </ConfEnum></ConfValue>

7. Add the following properties:

1. Add the following entry within the existing category "Persistence":<ConfValue description="Database Type. Allowed values are oracle or postgres" name="Database Type" propname="com.tibco.af.oms.databaseType" readonly="false" sinceVersion="3.0" visibility="Advanced"> <ConfEnum> <EnumValue default="true" selected="true" value="oracle"/> <EnumValue value="postgres"/> </ConfEnum></ConfValue>

2. Under the existing category "Persistence", find and replace the propertycom.tibco.af.oms.hibernate.dialect with the following property:<ConfValue description="" name="com.tibco.af.hibernate.dialect" propname="com.tibco.af.oms.hibernate.dialect" sinceVersion="1.1" visibility="Advanced"> <ConfEnum> <EnumValue default="true" selected="true" value="org.hibernate.dialect.Oracle10gDialect"/> <EnumValue value="org.hibernate.dialect.PostgreSQLDialect"/> </ConfEnum></ConfValue>

25


Post-Installation Task 6: Updating the ConfigValues_AOPD.xml FileUpdate the $AF_HOME/config/ConfigValues_AOPD.xml file by completing the following step:

1. Add the following category within the existing category "AOPD Application Flags configuration":<ConfValue description="Enable Parent_ID UDF check for plan item equivalence" name="EnableParentIDUdfCheck" propname="com.tibco.af.aopd.flags.enableparentidudfcheck" sinceVersion="3.0" visibility="Basic"> <ConfBool default="true" value="true" /></ConfValue>

Post-Installation Task 7: Updating the OMSServerLog4j.xml FileUpdate the $AF_HOME/config/OMSServerLog4j.xml to monitor the usage of the JDBC pool. Thefollowing configuration has to be performed to enable the connection of pooling logs:<category name="com.tibco.aff.oms.db.datasource.impl.FOMDataSourceProxy" additivity="false"> <priority value ="INFO"/> <appender-ref ref="console" /> <appender-ref ref="LocalLogFileAppender"/> </category>

Post-installation Task 8: Upgrading the OMS DatabaseThis upgrade task requires a new privilege (CREATE ANY JOB). The readme fileUpgradeOMS_FOM3.0_to_FOM3.0.1_README.txt provides details for this.

See the "Database Schema Upgrade" section in the Perform the Upgrade topic for the details tocomplete this task.

Post-Installation Task 9: Migrating the Non-Partitioned OMS Database intothe Partitioned OMS Database

Complete the following step if the user wants to migrate the non-partitioned OMS database into thepartitioned OMS database.

1. Run the script OMS_Partition_Migration.sql manually to migrate the non-partitioned 3.0.2 databaseinto the partitioned TIBCO Fulfillment Order Management 3.0.2 OMS database.

Details of the migration including additional privileges and required prerequisites are in thePartition_Migration_Readme.txt file.

Post-Installation Task 10: Upgrading the TIBCO EMS ChannelSee the "EMS Channel Upgrade" section in the Perform the Upgrade topic for the details to completethis task.

Post-Installation Task 11: Starting the TIBCO FOM EnginesStart the TIBCO Fulfillment Order Management engines:

● Apache Tomcat (OMS, AOPD, OMSUI, OPE, and OCS)

26


Configuring and Verifying Installation

After installation and post-installation tasks, a set of steps are supposed to be performed to ensuresuccessful installation of TIBCO Fulfillment Order Management. Configuring and verifying installationdeals with tasks like copying the war files, restarting the server, and verifying the installation.

Copying WAR filesAOPD can be deployed and used in two different ways. Either the collocated mode (which is thedefault mode) or the standalone mode. You can choose the deployment mode in $AF_CONFIG_HOME/profiles.properties.

OPE can be deployed and used in two different ways. Either the standalone mode (which is the defaultmode) or the collocated mode. You can choose the deployment mode in $AF_CONFIG_HOME/profiles.properties.

In the standalone mode, you need to manually copy all the *.war files (including aopd.war andope.war) from $AF_HOME/oms/webapps/ to $AF_HOME/apache-tomcat-<version>/webapps

Additional Environment Variables for Deployment

1. If the EMS server and oms are deployed on different machines, then following configuration needsto be done for proper deployment of omsServer:

a. Copy the files tibjms.jar, tibcrypt.jar and jms-2.0.jar to some folder. These files aretypically located at $EMS_HOME/lib folder.

b. Set the environment variable EMS_LIB_PATH to this folder location.

2. If the database server and oms modules are deployed on different machine then set the environmentvaraible ORACLE_JDBC_DRIVER_PATH to location where ojdbc6.jar is located.

3. Configure this application, following instructions in the configuration section.

Restarting the Server

1. Go to the $AF_HOME/apache-tomcat-<version>/bin directory.

2. Set environment variable NLS_LANG to AMERICAN_AMERICA.UTF8 and LANG to en_US.utf8.

3. To start the Tomcat server, run the following command:

$./startup.sh

Verifying InstallationThis section provides instructions for verifying that TIBCO Fulfillment Order Management hasinstalled correctly and for verifying the connectivity between various components. TheAF_TestHarness project referred to in this section is intended for testing only.

You must have TIBCO ActiveMatrix BusinessWorks installed on your machine to use the TestHarness.

Procedure

1. After performing installation and post-installation steps for TIBCO Fulfillment Order Managementengines, start Tomcat if it not started, and verify that the following servers have been started ordeployed without any errors.To start the OMS server, perform the following steps:

27


1. To start the server, run the following command:$cd $AF_HOME/apache-tomcat-<version>/bin$./startup.sh

Application Log File Located in

OMS/JEOMS Server $AF_HOME/apache-tomcat-<version>/logs/

OMS UI $AF_HOME/apache-tomcat-<version>/logs/

2. Open the AF_TestHarness project available in $AF_HOME/samples/TestHarness/AF_TestHarness.zip using TIBCO Designer. Import AF_Orchestrator_ForDesigner.projlibavailable under the $AF_HOME/be/projectLibs directory. Save the project asAF_TestHarness_Test to localize all the resources from the imported libraries and to update therequired global variables values.

3. Change the values of global variables related to JMS connection parameters for Orchestrator and thetest harness output directory path as shown in the following figures.

JMS Connection Parameters for Orchestrator

The AF_TestHarness project contains several BW processes integrating with AF Orchestrator orOMS Server components over the JMS channels as according to the following list. These are the stubprocesses just to show how the integration is done, and to have an end-to-end run.

28


● process component stubs (execute, suspend, activate)

● error handler stub

● pre-qualification failed handler stub

● status notification subscriber stubs

All these processes log the relevant details (for example, execution request payload) in differentfiles. These files are created under the directory named as orderref of the corresponding order.These directories are created under a parent directory whose path is configured in testhHarness/outputPath global variable.

4. Start the following starter processes in TIBCO Designer.

Starting Processes

Orchestrator Notifications Listener Processes:

● utilities/notifications/orderAmendmentNotification.process

● utilities/notifications/orderLineNotification.process

● utilities/notifications/orderNotification.process

● utilities/notifications/planDevelopmentNotification.process

● utilities/notifications/planItemNotification.process

● utilities/notifications/planNotification.process

These processes subscribe to the various notification events from the Orchestrator. Using theseevents the exact state of the order/plan can be known.

The publishing of status change notifications for each entity is not enabled in Orchestratorout of the box. In order to subscribe to the status change notifications using the abovementioned processes, the notification publishing must be enabled for each entity using therespective flags. These flags are available in the Orchestrator Configuration > GenericConfiguration category in the Configurator UI.

Orchestrator Task Stubs:

● utilities/stubs/planItemActivateStub

29


● utilities/stubs/planItemExecuteStub

● utilities/stubs/planItemSuspendStub

The process planItemExecuteStub is a dummy process component implementation. It calls a defaultprocess that gets and sets plan/planItem data using JMS based data acess interfaces and finallysends an execution success response to Orchestrator. The planItemSuspendStub andplanItemActivateStub processes are used for testing the order amendments functionality.

5. Verify that the following queues or topics are up and have listeners:

● tibco.aff.oms.ordersService

● tibco.aff.catalog.planfragment.request

● tibco.aff.catalog.product.request

6. Publish the following models:

Model Send Model on Queue Sample Located In

Product Model tibco.aff.catalog.product.reques

t

$AF_HOME/samples/Models/

ProductModel.xml

Plan FragmentModel

tibco.aff.catalog.planfragment.r

equest

$AF_HOME/samples/Models/

PlanFragmentModel.xml

To send the model on the queue, the content of the model should be sent on the queue.

7. Use only UTF-8 encoding type in the web service request.

Submit a dummy order through SOAP1over HTTP 2, or SOAP over JMS to the OMS serveraccording to the SubmitOrderRequest sample located at $AF_HOME/samples/Webservice/SubmitOrderRequest.xml. Use the WSDL available at $AF_HOME/schemas/wsdl/http/OrderServiceHTTP.wsdl or $AF_HOME/schemas/wsdl/jms/OrderServiceJMS.wsdl to submitorders. For instance, http://localhost:8080/omsServer/api/orderService?wsdl.

8. Verify that the jobs of various processes selected in the test harness are created. TheplanItemExecute stub acts as the basic process component which processes and responds to theexecution request sent by Orchestrator for each plan item.

9. Navigate to http://<machineIPAddress>:<port number>/omsui/Login/Login.jsp. Verify thatyou can see the order and the plan in the OMS UI as shown in the following sample figures. Checkwhether the status of the order is 'Complete'. For additional information on how to navigatethrough the OMS UI, see TIBCO Fulfillment Order Management User's Guide.

1 a simple XML-based protocol to let applications exchange information over HTTP.2 The Hypertext Transfer Protocol (HTTP) is an application protocol for distributed, collaborative, hypermedia information systems

30


Order View

Plan Grid View

31


Plan Gantt View

32


TIBCO Fulfillment Order Management Upgrade

This section is relevant for users who have a previous version of TIBCO Fulfillment OrderManagement, specifically 2.1.2HF5 or 3.0.1, to fulfill the orders and are now upgrading the software tothe new version TIBCO Fulfillment Order Management 3.0.2. While it is important to upgrade thesoftware or environment to the more recent versions to exploit more efficient approach and processesfor business benefits, it is equally important to preserve the business data during the system upgrade.This chapter provides all the necessary steps and precautions to be taken while migrating fromprevious versions of TIBCO Fulfillment Order Management to TIBCO Fulfillment Order Management3.0.2.

Upgrading from FOM 2.1.2 HF5 to FOM 3.0.2The following are the major steps required for upgrading from Fulfillment Order Management 2.1.2HF5 to 3.0.2:

1. Prepare TIBCO Fulfillment Order Management 2.1.2 for the upgrade.

2. Backup the database.

3. Install TIBCO Fulfillment Order Management 3.0.0.



6. Review the possible changes in process components.

7. Perform the upgrade.

8. Start the TIBCO Fulfillment Order Management 3.0.2 environment.

Prepare TIBCO Fulfillment Order Management 2.1.2 for the UpgradeThis topic describes all the necessary steps that must be carried out before starting the upgrade toTIBCO Fulfillment Order Management version 3.0.2.

The messages corresponding to the in-process orders in 2.1.2 will not be allowed to remain in thepending state on the respective queues. These messages must be processed using TIBCO FulfillmentOrder Management 2.1.2 before upgrading. However there are couple of queues on which messageswill be pending.

1. Stop the northbound system (for example, Siebel CRM) which sends the order request messages toTIBCO Fulfillment Order Management for fulfillment. Doing this ensures that there will be no neworder messages coming on the queue tibco.aff.oms.ordersService. All the existing messagesmust be processed by the OMS server component in 2.1.2.

2. Stop the southbound process component systems which are integrated with TIBCO FulfillmentOrder Management for processing various requests for plan items such as execute request, suspendrequest, activate request, and milestone release request. Doing this ensures that there will be no newmessages coming on the following queues. All the existing messages must be processed byOrchestrator in 2.1.2.

● tibco.aff.orchestrator.planItem.execute.reply

● tibco.aff.orchestrator.planItem.suspend.reply

● tibco.aff.orchestrator.planItem.milestone.notify.request

This also ensures that there will not be any new messages coming from process components on thefollowing queues associated with the JMS based data access interfaces which are used to get theorder data and get or set the plan/plan item data from OMS. All the existing messages must beprocessed by OMS server in 2.1.2.

33


● tibco.aff.tds.order.read.request

● tibco.aff.tds.plan.request

● tibco.aff.tds.plan.read.request

Keep the TIBCO Fulfillment Order Management 2.1.2 components running for appropriate timeduration to let them process all pending messages associated with the in-flight orders on their inboundqueues. The details for all the important queues are as follows:

1. If offer configuration and validation flag was enabled in OMS configurations, ensure that there areno messages pending on the following queues:

● tibco.aff.ocv.events.offer.validate.request

● tibco.aff.ocv.events.offer.validate.reply.oms

These queues will be deleted during the upgrade of the TIBCO EMS channels as the BEOCV component is no longer supported.

2. Ensure that there are no messages pending on the following queues related to the various types oforder requests submitted to Orchestrator:

● tibco.aff.orchestrator.order.submit

● tibco.aff.orchestrator.order.suspend

● tibco.aff.orchestrator.order.activate

● tibco.aff.orchestrator.order.withdraw

3. If the order feasibility check is enabled in the Orchestrator configuration, ensure that there are nomessages pending on the following queues. The external feasibility provider component shouldprocess all the request messages and Orchestrator should process all the reply messages.

● tibco.aff.orchestrator.provider.order.feasibility.request

● tibco.aff.orchestrator.provider.order.feasibility.reply

4. Ensure that there are no messages pending on any of the following queues that are used for theintegration between Orchestrator and the standalone AOPD components for execution plangeneration. There will not be any messages on any of these queues if AOPD component is deployedin the AOPD_colocated mode which is specified as default in the $AF_HOME/config/profiles.properties file.

● tibco.aff.orchestrator.provider.order.opd.request

● tibco.aff.ocv.events.plan.new.request

● tibco.aff.ocv.events.plan.amend.request

● tibco.aff.ocv.events.newplan.reply

● tibco.aff.ocv.events.amendplan.reply

● tibco.aff.orchestrator.provider.order.opd.reply

5. If order pre-qualification handling is enabled in Orchestrator configuration, ensure that there are nomessages pending on the following queues. The external pre-qualification failed request handlershould process all the request messages and Orchestrator should process all the reply messages.

● tibco.aff.orchestrator.provider.order.prequal.failed.request

● tibco.aff.orchestrator.provider.order.prequal.failed.reply

6. Ensure that there are no messages pending on any of the following queues that are used forintegration between Orchestrator and external plan item error handler component for processingthe failed plan item requests.

34


● tibco.aff.orchestrator.provider.planItem.failed.request

● tibco.aff.orchestrator.provider.planItem.failed.reply

7. Ensure that there are no messages pending on the following queue that is used by the externalsystems to release the external dependencies on the plan items. All the messages must be processedby Orchestrator.

● tibco.aff.orchestrator.planItem.externalDependency.release.request

8. Ensure that there are no messages pending on the following queue that are used by Orchestrator forinternal processing.

● tibco.aff.orchestrator.cache.addEvent

● tibco.aff.orchestrator.cache.cleanup

Considering the pending messages on all the earlier mentioned queues are processed by the respectiveTIBCO Fulfillment Order Management components, there will be messages pending only on thefollowing queues. These are the outbound queues for Orchestrator to send various requests for planitems to the process components. The messages on these queues will be processed once the processcomponent systems are started after the upgrade.

● tibco.aff.orchestrator.planItem.execute.request

● tibco.aff.orchestrator.planItem.suspend.request

● tibco.aff.orchestrator.planItem.activate.request

● tibco.aff.orchestrator.planItem.milestone.release.request

If the requestReply header property was set to false in GetOrder, GetPlan, GetPlanItem, SetPlan orSetPlanItem data access requests, there will be messages pending on either of the following queues oron the queues passed as replyTo destinations in the requests. These are also the outbound queues forthe OMS server. The pending messages on these queues will also be processed once the processcomponent systems are started after the upgrade.

● tibco.aff.tds.order.reply

● tibco.aff.tds.plan.reply

After ensuring that no further processing is going on in any of the Apache Tomcat servers of TIBCOFulfillment Order Management 2.1.2, they can be shut down at this stage. Also, shutdown all theexternal components, such as feasibility provider, pre-qualification failed request handler, externalOPD, plan item error handler component, and so on.

Backup the DatabaseSince the upgrade involves changes in the database, make sure to backup the OMS database instancethat has been used by TIBCO Fulfillment Order Management 2.1.2.

Install TIBCO Fulfillment Order Management 3.0.0To install TIBCO Fulfillment Order Management 3.0.0, see TIBCO® Fulfillment Order ManagementInstallation and Configuration Guide of Fulfillment Order Management 3.0.0

Complete all the post-installation tasks for TIBCO Fulfillment Order Management 3.0.0 before installingTIBCO Fulfillment Order Management 3.0.1.

35


Install TIBCO Fulfillment Order Management 3.0.1To install TIBCO Fulfillment Order Management 3.0.1, see TIBCO® Fulfillment Order ManagementInstallation and Configuration Guide of Fulfillment Order Management 3.0.1

You must complete all the post-installation tasks for TIBCO Fulfillment Order Management 3.0.1 beforeinstalling TIBCO Fulfillment Order Management 3.0.2.

Install TIBCO Fulfillment Order Management 3.0.2This topic describes Fulfillment Order Management 3.0.2 installation for the migration process.

● To install Fulfillment Order Management 3.0.2, see Installing in GUI Mode, Installing in ConsoleMode, or Installing in Silent Mode.

● Fulfillment Order Management 3.0.2 is installed at the $TIBCO_HOME/af/3.0.2 location.Henceforth, it is referred to as $AF_HOME.

Update the environment variables as per TIBCO Fulfillment Order Management 3.0.2 installation. Forexample:

● export AF_HOME = /opt/tibco/af/3.0● export AF_CONFIG_HOME = $AF_HOME/config

Possible Changes in Process ComponentsThis topic describes the changes that might need to be done in process component systems.

The codes and messages being returned in the responses of JMS based data access interfaces -GetOrder, GetPlan, GetPlanItem, SetPlan, and SetPlanItem - have been changed in TIBCO FulfillmentOrder Management. This has been done to make them consistent across all the interfaces, in messageheader and payload too. If the process component systems implementation has any logic on the basis ofthese values then it must be updated with the new ones. See the topic "Data Access Interfaces" in TIBCOFulfilment Order Management Users Guide for the details of the codes and messages being returned byeach interface in various situations.

Perform the UpgradeThis section describes the step by step upgrade process.

TIBCO Fulfillment Order Management User Upgrade

To successfully execute TIBCO Fulfillment Order Management 2.1.2 HF5 to TIBCO Fulfillment OrderManagement 3.0.2 database upgrade, your database user needs a special privilege. Execute thefollowing query to assign the privilege:GRANT CREATE ANY JOB TO <<OMS_DB_USER>>;

Database Schema Upgrade

The database being used by TIBCO Fulfillment Order Management 2.1.2 HF5 needs the schemaupgrade to be used with TIBCO Fulfillment Order Management 3.0.2. The database schema changesinclude the creation of few new tables and altering the existing ones for indexes and columns changes.Before starting the database upgrade, ensure that the backup of the existing database is complete, sothat it can be reused in case of any failures during the upgrade.

Run the following script using the TIBCO Fulfillment Order Management database user credentials forthe upgrade:

$AF_HOME/db/oracle/oms/UpgradeOMS_FOM2.1.2HF5_to_FOM3.0.2.sql <fom_tablespace_name>

The name of the corresponding Oracle table space must be given as an argument while running thisscript since the DDL statements in the script requires it. The script can be run using the Oracle sqlpluscommand line program or Oracle SQL Developer UI client.

36


EMS Channel Upgrade

The EMS channels (queues, topics, bridges) being used by TIBCO Fulfillment Order Management2.1.2HF5 needs to be upgraded so that it can be used with TIBCO Fulfillment Order Management 3.0.2.The EMS channel upgrade includes creating new queues and topics, and deleting some of the existingqueues, topics, and bridges that are obsolete.

Run the following script using TIBCO EMS administration command line utility for the upgrade:$AF_HOME/ems/FOM_UpgradeEMSChannel_2.1.2HF5_to_3.0.2.txt.

The command to run the upgrade script is as follows:

$EMS_HOME/bin/tibemsadmin64 -ignore -server $EMS_SERVER_URL -user $EMS_USERNAME -

password $EMS_PASSWORD -script $AF_HOME/ems/

FOM_UpgradeEMSChannel_2.1.2HF5_to_3.0.2.txt.

Update the profiles.properties File

Add the following property under the profile.properties file:

com.tibco.fom.ope.deployMode=OPE_standalone

Merge Existing Application and Log4J Configuration Properties

Migrate the application configuration and log4j configuration properties being used by TIBCOFulfillment Order Management 2.1.2 HF5 into the corresponding files in the TIBCO Fulfillment OrderManagement 3.0.2 installation. This can be done by running a Java based command line utility whichcan be launched using $AF_HOME/migration/bin/migrateConfigProperties.sh. This utility requiresall jar files present in the $AF_HOME/migration/lib directory. This utility refers to the following threeenvironment variables, which must be set before running it. The utility fails with the appropriate errormessage if any of the following environment variables are not set:

1. JAVA_HOME- This is the variable for the set path of the Java installation. For example: /usr/java/jdk1.8.0_112.

2. AF_HOME- This is the variable for the set path of the TIBCO Fulfillment Order Management 3.0.2installation directory. For example: $TIBCO_HOME/af/3.0.

3. OLD_AF_HOME- This is the variable for the set path of the TIBCO Fulfillment Order Management2.1.2 installation directory. For example: $TIBCO_HOME/af/2.1.

The utility refers to the following two files from the $AF_HOME/migration/config directory:

1. migrationIgnore.properties - This file contains the property name of the configuration properties,which will be ignored during migration. By default, there are only three configuration propertieswhich will be ignored (com.tibco.af.oms.jms.cf.beo.deliverymode,com.tibco.af.oms.dataSource.pooledDataSource.connectionProperty, andcom.tibco.af.oms.pooledArchiveDataSource.url).

2. MigrationLog4j.xml - This file contains the log4j configurations for the utility with the default loglevelset at INFO level. It can be changed to DEBUG for more granular logging. The utility writes thelogs in the $AF_HOME/migration/logs/fom- property-migration.log file.

This utility migrates the application configuration properties for the following components in thementioned files.

1. OmsServer and Orchestrator - $AF_HOME/config/ConfigValues_ OMS.xml

2. AOPD - $AF_HOME/config/ConfigValues_ AOPD.xml

3. JEOMS - $AF_HOME/config/ConfigValues_ JEOMS.xml

This utility also migrates the log4j configuration properties for the following components in thementioned files:

37


1. OmsServer, Orchestrator and JEOMS - $AF_HOME/config/ OMSServerLog4j.xml

2. AOPD - $AF_HOME/config/AOPDLog4j.xml

3. OMSUI - $AF_HOME/config/OMSUILog4j.xml

The application and log4j configurations for OPE and OCS components cannot be migrated. Theirconfiguration needs to be done manually by using the TIBCO Fulfillment Order ManagementConfigurator UI.

Start TIBCO Fulfillment Order Management 3.0.2 EnvironmentThis topic covers the steps to start the Fulfillment Order Management 3.0.2 environment:

Additional Configurations

Perform any additional configuration changes that are required using the Configurator web UI.

For example, Offer and Price Engine (OPE) requires the price and discount models for itsfunctionalities. So the offline catalog directories for loading these models in the application should beconfigured here.

Post-Installation Tasks

Perform the steps mentioned in the Post-Installation Tasks topic.

Cluster Setup

The migrated database already contains the cluster members that were running in TIBCO FulfillmentOrder Management 2.1.2 HF5 environment. For running additional Apache Tomcat instances in acluster or setting up a new cluster, refer to the "Deployment Topologies" section in the TIBCOFulfillment Order Management Administration Guide.

Start all required Apache Tomcat server instances to start the configured TIBCO Fulfillment OrderManagement members in the cluster. Upon starting up, the engines will load the existing data models(product and action) from the database. As per the model loading configurations (online or offline), theadditional data models will be loaded in the application and will also be stored into the database asexplained in the "Data Models" section in TIBCO Fulfillment Order Management Administration Guide.

Monitor the logs of each member to ensure that all the members have started successfully. At this stagethe TIBCO Fulfillment Order Management 3.0.2 environment is ready to process any incomingrequests, but since there are no pending messages, processing will not occur.

Start External Components

Start the external components which integrate with Orchestrator through EMS and the ones that werestopped before the upgrade. This includes the following components:

1. Feasibility provider

2. Prequalification failed handler

3. External dependency releasing systems

4. Plan item error handler

Start Southbound Process Components

Start the process component system. The process components will start processing the plan itemexecute, suspend, activate, and milestone release messages pending on the four outbound queues ofOrchestrator and will also send the corresponding reply messages to Orchestrator. Orchestrator willprocess the incoming reply messages to move the state of the corresponding plan items appropriately.Based on this, it will also schedule the requests for the further plan items in the execution plan to fulfill

38


the orders. With this way, the orders that were in-progress in Fulfillment Order Management 2.1.2before the upgrade will be processed in TIBCO Fulfillment Order Management 3.0.2.

Start Northbound System

Start the northbound systems (for example, Siebel) to submit the new orders to be fulfilled usingFulfillment Order Management 3.0.2.

Upgrading from FOM 3.0.1 to FOM 3.0.2The following are the major steps required for migrating from Fulfillment Order Management 3.0.1 to3.0.2:

1. Prepare TIBCO Fulfillment Order Management 3.0.1 for the upgrade.

2. Backup the database.

3. Install TIBCO Fulfillment Order Management 3.0.2

4. Review the possible changes in process components.

5. Perform the upgrade.

6. Start the TIBCO Fulfillment Order Management 3.0.2 environment

Prepare TIBCO Fulfillment Order Management 3.0.1 for the UpgradeThis topic describes all the necessary steps that must be carried out before starting the upgrade toTIBCO Fulfillment Order Management version 3.0.2.

The messages, corresponding to the in-process orders in 3.0.1, will not be allowed to remain in thepending state on the respective queues. These messages must be processed using TIBCO FulfillmentOrder Management 3.0.1 before upgrading. However there are couple of queues on which messageswill be pending.

1. Stop the northbound system (for example, Siebel CRM) which sends the order request messages toTIBCO Fulfillment Order Management for fulfillment. Doing this ensures that there will not be anynew order messages coming on the queue tibco.aff.oms.ordersService. All the existingmessages must be processed by the OMS server component in 3.0.1.

2. Stop the southbound process component systems which are integrated with Fulfillment OrderManagement for processing various requests for plan items such as execute request, suspendrequest, activate request, and milestone release request. Doing this ensures that there will be no newmessages coming on the following queues. All the existing messages must be processed byOrchestrator in 3.0.1.

● tibco.aff.orchestrator.planItem.execute.reply

● tibco.aff.orchestrator.planItem.suspend.reply

● tibco.aff.orchestrator.planItem.milestone.notify.request

This also ensures that there will not be any new messages coming from process components on thefollowing queues associated with the JMS based data access interfaces which are used to get theorder data and get or set the plan/plan item data from OMS. All the existing messages must beprocessed by OMS server in 3.0.1.

● tibco.aff.tds.order.read.request

● tibco.aff.tds.plan.request

● tibco.aff.tds.plan.read.request

Keep the TIBCO Fulfillment Order Management 3.0.1 components running for appropriate timeduration to let them process all pending messages associated with the in-flight orders on their inboundqueues. The details for all the important queues are as follows:

39


1. Ensure that there are no messages pending on the following queues related to the various types oforder requests submitted to Orchestrator:

● tibco.aff.orchestrator.order.submit

● tibco.aff.orchestrator.order.suspend

● tibco.aff.orchestrator.order.activate

● tibco.aff.orchestrator.order.withdraw

2. If the order feasibility check is enabled in the Orchestrator configuration, ensure that there are nomessages pending on the following queues. The external feasibility provider component shouldprocess all the request messages and Orchestrator should process all the reply messages.

● tibco.aff.orchestrator.provider.order.feasibility.request

● tibco.aff.orchestrator.provider.order.feasibility.reply

3. Ensure that there are no messages pending on any of the following queues that are used for theintegration between Orchestrator and the standalone AOPD components for execution plangeneration. There will not be messages on any of these queues if AOPD component is deployed inAOPD_colocated mode which is specified as default in the $AF_HOME/config/profiles.properties file.

● tibco.aff.orchestrator.provider.order.opd.request

● tibco.aff.ocv.events.plan.new.request

● tibco.aff.ocv.events.plan.amend.request

● tibco.aff.ocv.events.newplan.reply

● tibco.aff.ocv.events.amendplan.reply

● tibco.aff.orchestrator.provider.order.opd.reply

4. If order prequalification handling is enabled in Orchestrator configuration, ensure that there are nomessages pending on the following queues. The external prequalification failed request handlershould process all the request messages and Orchestrator should process all the reply messages.

● tibco.aff.orchestrator.provider.order.prequal.failed.request

● tibco.aff.orchestrator.provider.order.prequal.failed.reply

5. Ensure that there are no messages pending on any of the following queues that are used forintegration between Orchestrator and external plan item error handler component for processingthe failed plan item requests.

● tibco.aff.orchestrator.provider.planItem.failed.request

● tibco.aff.orchestrator.provider.planItem.failed.reply

6. Ensure that there are no messages pending on the following queue that is used by the externalsystems to release the external dependencies on the plan items. All the messages must be processedby Orchestrator.

● tibco.aff.orchestrator.planItem.externalDependency.release.request

7. Ensure that there are no messages pending on the following queue that are used by Orchestrator forinternal processing.

● tibco.aff.orchestrator.cache.addEvent

● tibco.aff.orchestrator.cache.cleanup

Considering the pending messages on all the earlier mentioned queues are processed by the respectiveTIBCO Fulfillment Order Management components, there will be messages pending only on the

40


following queues. These are the outbound queues for Orchestrator to send various requests for planitems to the process components. The messages on these queues will be processed once the processcomponent systems are started after the upgrade.

● tibco.aff.orchestrator.planItem.execute.request

● tibco.aff.orchestrator.planItem.suspend.request

● tibco.aff.orchestrator.planItem.activate.request

● tibco.aff.orchestrator.planItem.milestone.release.request

If the requestReply header property was set to false in GetOrder, GetPlan, GetPlanItem, SetPlan orSetPlanItem data access requests, there will be messages pending on either of the following queues oron the queues passed as replyTo destinations in the requests. These are also the outbound queues forthe OMS server and the pending messages on these queues will also be processed once the processcomponent systems are started after the upgrade.

● tibco.aff.tds.order.reply

● tibco.aff.tds.plan.reply

After ensuring that no further processing is going on in any of the Apache Tomcat servers of TIBCOFulfillment Order Management 3.0.1, they can be shut down at this stage. Also, shutdown all theexternal components, such as feasibility provider, pre-qualification failed request handler, externalOPD, plan item error handler component, and so on.

Backup the DatabaseSince the upgrade involves changes in the database, make sure to backup the OMS database instancethat has been used by TIBCO Fulfillment Order Management 3.0.1.

Install TIBCO Fulfillment Order Management 3.0.2This topic describes Fulfillment Order Management 3.0.2 installation for the migration process.

● To install Fulfillment Order Management 3.0.2, see Installing in GUI Mode, Installing in ConsoleMode, or Installing in Silent Mode.

● Fulfillment Order Management 3.0.2 is installed at the $TIBCO_HOME/af/3.0.2 location.Henceforth, it is referred to as $AF_HOME.

Update the environment variables as per TIBCO Fulfillment Order Management 3.0.2 installation. Forexample:

● export AF_HOME = /opt/tibco/af/3.0

● export AF_CONFIG_HOME = $AF_HOME/config

Possible Changes in Process ComponentsThis topic describes the changes that might need to be done in process component systems.

The codes and messages being returned in the responses of JMS based data access interfaces -GetOrder, GetPlan, GetPlanItem, SetPlan, and SetPlanItem - have been changed in TIBCO FulfillmentOrder Management. This has been done to make them consistent across all the interfaces, in messageheader and payload too. If the process component systems implementation has any logic on the basis ofthese values then it must be updated with the new ones. See the topic "Data Access Interfaces" in TIBCOFulfilment Order Management Users Guide for the details of the codes and messages being returned byeach interface in various situations.

41


Perform the UpgradeThis section describes the step by step upgrade process.

Database Schema Upgrade

The database being used by TIBCO Fulfillment Order Management 3.0.1 needs the schema upgrade tobe used with TIBCO Fulfillment Order Management 3.0.2. The database schema changes include thecreation of a few new tables and altering the existing ones for indexes and column changes. Therefore,when starting the database upgrade, ensure that the backup of the existing database is completed sothat it can be reused in case of any failures during the upgrade.

Run the following script using the application database user credentials for the upgrade:

$AF_HOME/db/oracle/oms/UpgradeOMS_FOM3.0.1_to_FOM3.0.2.sql <fom_tablespace_name>

The name of the corresponding Oracle table space must be given as an argument while running thisscript since the DDL statements in the script requires it. The script can be run using the Oracle sqlpluscommand line program or Oracle SQL Developer UI client.

EMS Channel Upgrade

The EMS channels (queues, topics, and bridges) being used by TIBCO Fulfillment Order Management3.0.1 needs upgrade so that it can be used with TIBCO Fulfillment Order Management 3.0.2. The EMSchannel upgrade includes creating new queues and topics, and deleting some of the existing queues,topics, and bridges that are obsolete.

Run the following script using TIBCO EMS administration command line utility for the upgrade:$AF_HOME/ems/FOM_UpgradeEMSChannel_3.0.1_to_3.0.2.txt.

The command to run the upgrade script is as follows:

$EMS_HOME/bin/tibemsadmin64 -ignore -server $EMS_SERVER_URL -user $EMS_USERNAME -

password $EMS_PASSWORD -script $AF_HOME/ems/FOM_UpgradeEMSChannel_3.0.1_to_3.0.2.txt.

Start TIBCO Fulfillment Order Management 3.0.2 EnvironmentThis topic covers the steps to start the Fulfillment Order Management 3.0.2 environment:

Additional Configurations

Perform any additional configuration changes that are required using the Configurator web UI.

For example, OPE component requires the Price and Discount models for its functionalities. So theoffline catalog directories for loading these models in the application should be configured here.

Post Installation Tasks

Perform the steps mentioned in the Post-Installation Tasks on page 21.

Cluster Setup

The migrated database already contains the cluster members that were running in the TIBCOFulfillment Order Management 3.0.1 environment. For running additional Apache Tomcat instances ina cluster or setting up a new cluster, refer to the "Deployment Topologies" section in the TIBCOFulfillment Order Management Administration Guide.

Start all required Apache Tomcat server instances to start the configured TIBCO Fulfillment OrderManagement members in the cluster. Upon starting up, the engines will load the existing data models(Product and Action) from the database. As per the model loading configurations (online or offline), theadditional data models will be loaded in the application and stored into the database as explained inthe "Data Models" section in TIBCO Fulfillment Order Management Administration Guide.

42


Monitor the logs of each member to ensure that all the members have started successfully. At this stagethe Fulfillment Order Management 3.0.2 environment is ready to process any incoming requests, butsince there are no pending messages, processing will not occur.

Start External Components

Start the external components which integrate with Orchestrator through EMS and the ones that werestopped before the upgrade. These include the following components:

1. Feasibility provider

2. Prequalification failed handler

3. External dependency releasing systems

4. Plan item error handler

Start Southbound Process Components

Start the process component system. The process components will start processing the plan itemexecute, suspend, activate, and milestone release messages pending on the four outbound queues ofOrchestrator and will also send the corresponding reply messages to Orchestrator. Orchestrator willprocess the incoming reply messages to move the state of the corresponding plan items appropriately.Based on this, it will also schedule the requests for the further plan items in the execution plan to fulfillthe orders. With this way, the orders that were in-progress in Fulfillment Order Management 3.0.1before the upgrade will be processed in TIBCO Fulfillment Order Management 3.0.2.

Start Northbound System

Start the northbound systems (for example, Siebel) to submit the new orders to be fulfilled using TIBCOFulfillment Order Management 3.0.2.

43


Installation FAQs and Troubleshooting

This section can help you troubleshoot some common error messages that you may receive.

What should I do if the Enterprise Message Service destination creation fails while configuringFulfillment Order Management?

If TIBCO Enterprise Message Service is not installed on the same machine as Fulfillment OrderManagement, the destination creation fails. Create the destinations manually using the EnterpriseMessage Service Administration utility on the machine where Enterprise Message Service is installed.

For details, see $AF_HOME/ems/AF_CreateEMSChannel.txt (for non-OMS component). Another scriptis used for OMS located at $AF_HOME/ems/OMS_EmsConfiguration.txt.

What should I do when I get the "ORA-00942: table or view does not exist" error. I have created OMSdatabase using the Database Wizard and see the tables created correctly in the database. What couldbe the problem?

Ensure you have configured the hibernate.default_catalog property correctly. This property can beconfigured using the Configurator UI and is located at the following path: "Order management System-> Member 1 -> Persistence -> hibernate.default_catalog. The value of this property should be thedatabase user name of the OMS database.

What should I do if I get the following error related to the Oracle driver?

SEVERE: Error while registering Oracle JDBC Diagnosability MBean.

javax.management.MalformedObjectNameException: Invalid character ' ' in value part ofproperty

at javax.management.ObjectName.construct(ObjectName.java:602)

at javax.management.ObjectName.<init>(ObjectName.java:1394)

This could be an Oracle driver issue. Try downloading the drivers from OTN again. A patch has beenadded for fixing this issue. To know whether you have the patch, run:

java -jar ojdbc6.jar

● If the ojdbc6.jar contains the patch, the following is displayed:

Oracle 11.1.0.6.0-Production+ JDBC 4.0 complied with JDK6

● If the ojdbc6.jar does not contain the patch, the following is displayed:

Oracle 11.1.0.6.0-Production JDBC 4.0 complied with JDK6

What should I do to get the Hibernate component if the servers where Fulfillment OrderManagement will be deployed do not have Internet connectivity?

Download the product_tibco_hibernate_3.6.9.001.zip file from the http://public.tibco.com/pub/tibco_oss/hibernate/product_tibco_hibernate_3.6.9.001.zip location.

What should I do if I see the ORACLE related errors during migration?

Set of ORACLE errors are bound to occur if other scripts have already been executed. For example,purge scripts. Such ORACLE errors have been added to the ignore list and they do not cause themigration to fail. However, any error other than the defined list results in the database migrationfailure.

All the errors are logged in the $AF_HOME/migration/log/DBmigration<<dd-mm-yyhr:min:dec>>.log file:

44




ErrorCodes Description

ORA-00942

Table or view does not exist

ORA-00955

Name is already used by an existing object

ORA-01418

Specified index does not exist

ORA-02289

Sequence does not exist

ORA-02442

Cannot drop nonexistent unique key

ORA-02443

Cannot drop constraint - nonexistent constraint

What should I do to upgrade EMS from version X to 8.x.x?

Ensure you back up all the data store and configuration files before performing any upgrade.

For single EMS server, perform the following steps:

Steps to upgrade the EMS server:

1. Disconnect all your applications connecting to the current EMS versions.

2. Stop the EMS server.

3. Back up all the configuration files and the data store for the EMS server.

4. Uninstall the current version of EMS server.

You can skip this step if you want to have multiple EMS server versions on the box. It isnot recommended.

5. Install EMS server 8.x.x.

6. Update the environment variables accordingly on the EMS server box to reflect the new EMSinstallation path.

EMS 8.x.x is installed in the $TIBCO_HOME/ems/8.x folder. Ensure that you modify theenvironment variables set for the EMS servers and other applications accordingly.

7. Start the EMS server against your old configuration files and data store.

8. Start all the applications that you want to connect the EMS server.

If you have set up the EMS server to work on Fault Tolerant, perform the following steps:

1. Back up the .conf and .db files.

2. Shutdown the standby EMS server (version X) by connecting to it through EMSAdmin and issuing theshutdown command.

Ensure that you are connected to the standby server by executing the info command andverifying the state before issuing the shutdown command.

45


3. Restart the standby version 8.x.x EMS server having the same configuration setup as that of thestandby server. This locks the database files and becomes the standby server. The standby serverthen runs with the EMS version X.

4. Shutdown active version X EMS server by connecting to it through EMSAdmin and issuing theshutdown command.

This step activates the standby server, resulting in the shared state conversion to the 8.x.xversion. The active server then runs with the 8.x.x version.

5. View the active server log file to verify that the original standby server has been successfullyactivated.

6. To ensure that applications remain connected and they are processing messages, wait for a fewminutes.

7. Restart the previously active EMS server in standby mode with the 8.x.x EMS version with the sameconfiguration file of the previous active EMS server (version X).

8. To fail back to the original server, shut down the active server.

This step is optional. To ensure that both the EMS servers are able to become active duringfailover, start the standby EMS server to make both EMS servers run in FT mode.

What should I do if I get the following error message?"Resource Bundle Not found as perlocale - java.util.MissingResourceException: Can't find bundle for base name

com.tibco.mdm.properties.activecatalog.HierarchyMessages" in OMS-UI startup logs.

Ignore this message

46


tibco fulfillment order management installation and ......tib_af_3.0.2_readme.txt file. install and...

Documents