tibco fulfillment order management installation and ... · tibco® fulfillment order management...

TIBCO® Fulfillment OrderManagement Installation andConfigurationSoftware Release 3.0.0July 2015

TIBCO® Fulfillment Order Management Installation and Configuration

2 |

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDEDOR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITEDADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLEDSOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FORANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF ALICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT,OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENTWHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH ISDUPLICATED IN LICENSE.PDF) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT ORCLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OFTHE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOURUSE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.

This document contains confidential information that is subject to U.S. and international copyright laws and treaties.No part of this document may be reproduced in any form without the written authorization of TIBCO SoftwareInc.

TIBCO, Two-Second Advantage, TIBCO ActiveMatrix BusinessWorks, TIBCO Runtime Agent, TIBCO Administrator,and TIBCO Enterprise Message Service, are either registered trademarks or trademarks of TIBCO Software Inc. inthe United States and/or other countries.

EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of SunMicrosystems, Inc. in the U.S. and other countries.

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

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALLOPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAMETIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFICOPERATING SYSTEM PLATFORM.

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

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGESARE PERIODICALLYADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATEDIN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/ORCHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANYTIME.

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

Copyright © 2010-2015 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information.


Contents

Preface..................................................................................................7Related Documentation............................................................................................................8

Typographical Conventions......................................................................................................9

Connecting with TIBCO Resources........................................................................................10

Chapter 1 Installation Overview.....................................................11Operating System and Database Requirements....................................................................13

Required Products..................................................................................................................14

Required Third-Party Products....................................................................................14

Required TIBCO Products...........................................................................................15

Installation Options.................................................................................................................16

TIBCO Environment....................................................................................................16

Installation Scenarios..................................................................................................16

Installation Environment Variables...............................................................................17

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

Installation Registry, History, and Log Files............................................................................19

Chapter 2 Installation and Deployment Options...........................21Typical or Custom Install........................................................................................................22

Installation Modes..................................................................................................................23

GUI Mode....................................................................................................................23

Console Mode.............................................................................................................23

Silent Mode..................................................................................................................23

Chapter 3 Installing TIBCO Fulfillment Order Management.........25Installing in GUI Mode............................................................................................................26

Installing in Console Mode.....................................................................................................32

Installing in Silent Mode.........................................................................................................33

Uninstalling TIBCO Fulfillment Order Management...............................................................34

Chapter 4 Post-installation Tasks...................................................35Creating Bridge to Publish the Models from Fulfillment Catalog............................................36

Chapter 5 Configuring and Verifying Installation..........................37Copying WAR files..................................................................................................................38

Restarting the Server.............................................................................................................39


TOC | 5

Verifying Installation...............................................................................................................40

Chapter 6 Fulfillment Order Management Migration....................45Migration from FOM 2.1.2 HF2 to FOM 3.0.0.........................................................................46

Prepare Fulfillment Order Management 2.1.2 for Migration........................................46

Backup Database........................................................................................................48

Install Fulfillment Order Management 3.0.0.................................................................48

Possible Changes in Process Components.................................................................48

Perform the Migration..................................................................................................48

Start Fulfillment Order Management 3.0.0 Environment.............................................49

Chapter 7 Installation FAQs and Troubleshooting........................51


6 | TOC

Preface

The preface contains information about documentation related to the current document, typographicalconventions, and information on how to contact TIBCO support.


Related Documentation

This section lists documentation resources you may find useful.

TIBCO Fulfillment Order Management Documentation

• TIBCO Fulfillment Order Management Concepts and Architecture This manual describes terminology and conceptsof TIBCO Fulfillment Order Management.

• TIBCO Fulfillment Order Management Installation and Configuration Read this manual for instructions on sitepreparation, installation, and configuration.

• TIBCO Fulfillment Order Management Administration Read this manual for instructions on administration tasks.• TIBCO Fulfillment Order Management User's Guide This manual describes the features and functionality as well

as all the screens.• TIBCO Fulfillment Order Management Web Services Read this manual for information about the web services.• TIBCO Fulfillment Order Management Release Notes Read the release notes for a list of features. This document

also contains the list of known issues for this release.

Other TIBCO Product Documentation

You may find it useful to read the documentation for the following TIBCO products:

• TIBCO Administrator™ Installation: Read this manual for instructions on the installation of TIBCOAdministrator.

• TIBCO BusinessEvents™ Installation : Read this manual for instructions on the installation of TIBCOBusinessEvents.

• TIBCO Enterprise Message Service™ Installation: Read this manual for instructions on the installation of TIBCOEnterprise Message Service.

• TIBCO Runtime Agent™ Installation: Read this manual for instructions on the installation of TIBCO RuntimeAgent.


8 | Preface

Typographical Conventions

The following typographical conventions are used in this manual:

Table 1: General Typographical Conventions

UseConvention

Many TIBCO products are installed within the same home directory. This directory isreferenced in documentation as TIBCO_HOME. The value of TIBCO_HOME depends onthe operating system. For example, on Unix systems the default value is $HOME/tibco.

TIBCO_HOME

TIBCO Fulfillment Order Management is installed into a directory inside TIBCO_HOME.This directory is referenced in documentation as AF_HOME. The value of AF_HOME

AF_HOME

depends on the operating system. For example, on UNIX systems the default value is$TIBCO_HOME/af/3.0.

Bold code font is used in the following ways:bold code font

• In procedures, to indicate what a user types. For example: Type admin.• In large code samples, to indicate the parts of the sample that are of particular

interest.• In command syntax, to indicate the default parameter for a command. For example,

if no parameter is specified, MyCommand is enabled: MyCommand [enable |disable]

Italic font is used in the following ways:italic font

• To indicate a document title. For example: See TIBCO BusinessWorks Concepts.• To introduce new terms. For example: A portal page may contain several portlets.

Portlets are mini-applications that run in a portal.• To indicate a variable in a command or code syntax that you must replace. For

example: MyCommand pathname

The note icon indicates information that is of special interest or importance, for example,an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply theinformation provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example, dataloss or corruption if certain steps are taken or not taken.


Preface | 9

Connecting with TIBCO Resources

How to Join TIBCOmmunity

TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts—a place toshare and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs,and access to a variety of resources. To register, go to http://www.tibcommunity.com.

How to Access All TIBCO Documentation

After you join TIBCOmmunity, you can access the documentation for all supported product versions here:

https://docs.tibco.com.

How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, please contact TIBCO Support asfollows:• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this

site:

http://www.tibco.com/services/support

• If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a username and password. If you do not have a username, you can request one.


10 | Preface

http://www.tibcommunity.com

https://docs.tibco.com

http://www.tibco.com/services/support

https://support.tibco.com

Chapter

1Installation Overview

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

This chapter provides information about the system requirements in terms of operating systems and disk space,recommended setup for TIBCO

® Fulfillment Order Management installation, variables and properties required,

and important files necessary to perform the post-install log analysis.

Provided below are links to detailed information for preinstall requirements and settings, and the install andpost-install steps.

Preinstall

To ensure that you have a good experience installing TIBCO Fulfillment Order Management, it is alwaysrecommended to check whether your computer is ready for the installation. The pre-install section gives you theprerequisites to install TIBCO Fulfillment Order Management:1. Operating System and Database Requirements on page 13: This section provides you with information about

the platforms that TIBCO Fulfillment Order Management supports.2. Required Products on page 14: TIBCO Fulfillment Order Management requires a number of software components

to be installed. For a complete list of versions and platforms supported, see TIB_af_3.0.0.readme.txt file.Install and configure them in the mentioned order.

3. Installation Options on page 16: This section provides you with information about theoptions for installingTIBCO Fulfillment Order Management.

4. Installation Registry, History, and Log Files on page 19: These files inform you about:a. The log files, which contain important data about installation and uninstallation of TIBCO Fulfillment 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 different installationmodes. This chapter provides you with information about the available installation modes, the flow of theinstallation, and post-install steps you need to perform.

• Installing TIBCO Fulfillment Order Management: Step-by-step instructions are provided to help you installTIBCO Fulfillment Order Management using different installation modes. This chapter also describes the stepsrequired to uninstall TIBCO Fulfillment Order Management.

Post-install

Post-installation Tasks on page 35: After you complete the installation of TIBCO Fulfillment Order Management,you should complete the post-installation tasks. The post-installation tasks list the configuration and deploymentsteps of the components that you have just installed.

Topics

• Operating System and Database Requirements• Required Products


• Installation Options• Installer Disk Space Requirements in Temporary Area• Installation Registry, History, and Log Files


12 | Installation Overview

Operating System and Database Requirements

TIBCO Fulfillment Order Management supports the following platforms and databases:

Operating System

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

Database

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

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

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


Installation Overview | 13

Required Products

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

Required Third-Party Products

The following table lists the required third-party products:

Table 2: Required Third-Party Products

PurposeVersionProducts

A Java Development Kit (JDK) is a program development environment whichyou can use for writing Java applets and applications.

1.8 (orgreater)

JDK

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

See below the JDK installation details.

An Oracle database is required by Fulfillment Order Management to store data.11g Release2 and 12c(or greater)

OracleDatabase

The Oracle server can be installed on a separate machine based on the installationrequirement.

This is required on the machine where Fulfillment Order Management is installed.ojdbc6.jarand

Databasedriver

The driver is used to connect to and query the Oracle server.ojdbc7.jarfor 11gRelease 2

The driver (ojdbc6.jar) can be found in the Oracle database installation or it canbe downloaded directly from the Oracle website.

The installer downloads this JAR automatically depending on the selection option.3.6.9.FinalHibernate

If the machine where you install Fulfillment Order Management, does not haveInternet connection, then you will have to download the file separately and makeit available to the machine where Fulfillment Order Management is going to beinstalled. The file is platform independent. The URL where to find the file is:product_tibco_hibernate_3.6.9.001.zip.

Note where you dropped the zip, the installer, during the installation, will askyou where to find the file.

The installer downloads this file automatically depending on the selection option.3.7.2GnomeBinding

If the machine where you install Fulfillment Order Management, does not haveInternet connection, then you will have to download the file separately and makeit available to the machine where Fulfillment Order Management is going to beinstalled. The file is platform dependent. The URL where to find the files is:product_tibco_eclipse_lgpl_rcp_3.7.2.001_linux24gl23_x86_64.zip.

Note where you dropped the zip, the installer, during the installation, will askyou where to find the file.

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

ANT



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

PurposeVersionProducts

You also need to download and copy the ant-contrib-<version>.jar file tothe $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 Products

The Fulfillment Order Management requires some TIBCO products.

Required TIBCO Products for FOM

The following table lists the required TIBCO products for FOM:

The FOM installer does not verify if the required products are installed. Nonetheless, those productshave to be installed before FOM 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 FOM (that uses the latest TIBCO universal installer version) the last.

Table 3: Required TIBCO Products for FOM

For more information, refer to:PurposeProduct & Version

TIBCO Enterprise Message Service™Installation

Standards-based messaging softwarethat can serve as the backbone of anSOA by providing Java Message

TIBCO Enterprise MessageService™ 8.2.0

Service (JMS)-compliantcommunications across a wide rangeof platforms and applicationtechnologies.

EMS is a pre-requisite but isnot a part of the TIBCOFulfillment OrderManagement product license.



Installation Options

Depending on how you want to use TIBCO Fulfillment Order Management (FOM) there are different waysto install it.

First, there is the concept of TIBCO environment that you need to understand before we explain the differentways to use FOM and the corresponding installation options.

TIBCO Environment

The 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 a name,description, and directory on the disk. Each TIBCO environment is isolated so the same software can beinstalled into the different environments safely (e.g. different versions of the same software). You can alsoinstall 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, thenyou will have to do it in different TIBCO environment. Each time, you will have to run the installer (aninstallation session only deals with one single TIBCO environment).

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

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 home directory

of the user.

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

Installation Scenario

TIBCO Fulfillment Order Management (FOM) 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 the Concepts and User'sGuides.

Depending on if you want to use it, or not, the process to install FOM is different.

Scenario

The TIBCO environment has TIBCO Enterprise Message Service (EMS) installed, before FOM gets installed.

Once FOM is installed, the installation will look like this:



Installation Environment Variables

Recommended Environment Variables Setup

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

ValueEnvironment Variable

$TIBCO_HOME/af/3.0export AF_HOME

$AF_HOME/configexport AF_CONFIG_HOME

/usr/local/app/oracle/product/<ORACLE_VERSION>/db_1export ORACLE_HOME

/local/affuser/jdk1.8.xexport JAVA_HOME

/local/affuser/apache-ant-1.8.xexport ANT_HOME

$TIBCO_HOME/ems/8.2export EMS_HOME

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

Member1export NODE_ID

$ORACLE_HOME/lib:$LD_LIBRARY_PATHexport LD_LIBRARY_PATH

$ANT_HOME/lib:$CLASSPATHexport CLASSPATH

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

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

exportAF_OMS_CONTEXT_URL

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



Installer Disk Space Requirements in Temporary Area

This section describes the temporary disk space requirements for TIBCO Fulfillment Order Management.

Unix Platform

The installer launcher first extracts a Java Virtual Machine (JVM) in a temporary directory and uses this JVMto 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 Files

Installation and uninstallation log files are in the $HOME/.TIBCO directory within the installer’s user homedirectory. The files use this format:

• Install log

.TIBCO/install_<yyyy-mm-dd.hhmmss>/tibco_universal_installer.<affuser>_install.log

• 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.



Chapter

2Installation and Deployment Options

The following table summarizes the tasks for installing, configuring, and verifying TIBCO® Fulfillment Order

Management.

DescriptionInstructionsTask

TIBCO Fulfillment Order Managementsupports installation using GUI mode,Console mode and Silent mode.

You can use any one of the modes toinstall TIBCO Fulfillment OrderManagement.

Install from one of the availableoptions:

Install® TIBCO Fulfillment

Order Management

• GUI Mode• Console Mode• Silent Mode

After you complete the TIBCO FulfillmentOrder Management installation, you needto perform some post-installation steps.

For details, see Post-installationTasks on page 35.

Complete the post-installationsteps

This section is about verifying yourinstallation by performing a few simple

For details, see VerifyingInstallation on page 40.

Verify the installation

tests to see that TIBCO Fulfillment OrderManagement is properly installed withappropriate connectivity between itsvarious components.

Topics

• Typical or Custom Install• Installation Modes


Typical or Custom Install

Download the TIBCO Fulfillment Order Management installation package or install the components from aCD. The installer prompts you to accept the license agreement, then to choose to perform a typical install orcustom 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.


22 | Installation and Deployment Options

Installation Modes

The installer allows you to run in the following modes:

GUI Mode

In GUI mode, the installer presents panels that allow you to make choices about product selection, productlocation, and so on. When you run the installer by double-clicking on the icon, GUI mode is used.

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

Console Mode

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

For more information, refer to Installing in Console Mode on page 32.

Silent Mode

Silent 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 on page 33.


Installation and Deployment Options | 23

Chapter

3Installing TIBCO Fulfillment Order Management

This section describes the installation and uninstallation of TIBCO® Fulfillment Order Management using TIBCO

Universal Installer.

Topics

• Installing in GUI Mode• Installing in Console Mode• Installing in Silent Mode• Uninstalling TIBCO Fulfillment Order Management


Installing in GUI Mode

The 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.

Figure 1: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 Installation ProfileSelection dialog appears. If you do not agree to the terms of the license agreement, click the Cancel buttonto exit from the installation process.


26 | Installing TIBCO Fulfillment Order Management

Figure 2:TIBCO Installation License Screen

7. The TIBCO Installation Home dialog appears.

Specify an installation environment and click the Next button.

Figure 3:TIBCO Installation Home Screen


Installing TIBCO Fulfillment Order Management | 27

You can choose to either create a new TIBCO installation environment or select an existing environment.A TIBCO installation environment is used for software installations and consists of a Directory (the pathwhere the product would be installed) and Name fields. Products installed into different installationenvironments do not share components; therefore you can keep product installations completely isolatedfrom each other.

Create a new TIBCO_HOME

If this is the first time that you are installing a TIBCO product using the Universal Installer, you mustcreate an installation environment by specifying the following:– Directory: The root directory into which all TIBCO products are installed. Individual products will

use sub-directories. Type a path or click Browse to specify the path or accept the default location.

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

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

Use an existing TIBCO_HOME

If you have previously installed a TIBCO product using the Universal Installer, you can install the productinto a previously created installation environment (by selecting the environment from the list). If you dothis, the Directory and Name fields are populated automatically and cannot be edited.

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

• 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



Figure 4:TIBCO Installation Components Screen

9. The Configurator Settings dialog is displayed.

The Configurator is a configuration tool used to do advanced configuration for FOM. It is a web-basedGUI. You can configure during the installation, the port numbers to access the Configurator 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. Reviewthe 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 to theappropriate point. You can then continue the installation process from that point.



Figure 5: 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 the Finish

button to complete the installation process and close the installer window.



Figure 6: Post-Install Screen

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



Installing in Console Mode

The following procedure lists the steps to install TIBCO Fulfillment Order Management in console 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. Using a console window, navigate to the temporary directory that contains the universal installer and 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 Mode

The TIBCOUniversalInstaller.silent file is packaged in the directory that contains the universal installer.Edit the file with information for your environment before launching the silent installation. The file includescomments 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• 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.

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. 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 install location 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 35.



Uninstalling TIBCO Fulfillment Order Management

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



Chapter

4Post-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 you perform the next step.

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

Topics

• Creating Bridge to Publish the Models from Fulfillment Catalog


Creating Bridge to Publish the Models from Fulfillment Catalog

TIBCO Fulfillment Order Management provides the following queues to receive the published modelsfrom TIBCO Fulfillment Catalog:

• tibco.aff.catalog.product.request

• tibco.aff.catalog.planfragment.request

• tibco.aff.catalog.action.request

• tibco.aff.catalog.price.request

• tibco.aff.catalog.discount.request

If you are using Fulfillment Catalog to send the models to Fulfillment Order Management, then create abridge between Fulfillment Catalog topic to the corresponding Fulfillment Order Management queue asfollows:

TARGET QUEUESOURCE TOPIC

tibco.aff.catalog.product.requesttibco.ac.productmodel.topic

tibco.aff.catalog.planfragment.requesttibco.ac.planfragmentmodel.topic

tibco.aff.catalog.action.requesttibco.ac.actionmodel.topic

tibco.aff.catalog.price.requesttibco.ac.pricemodel.topic

tibco.aff.catalog.discount.requesttibco.ac.discountmodel.topic

The following are the commands to create these bridges:

create bridge source=topic:tibco.ac.productmodel.topictarget=queue:tibco.aff.catalog.product.request

create bridge source=topic:tibco.ac.planfragmentmodel.topictarget=queue:tibco.aff.catalog.planfragment.request

create bridge source=topic:tibco.ac.actionmodel.topictarget=queue:tibco.aff.catalog.action.request

create bridge source=topic:tibco.ac.pricemodel.topictarget=queue:tibco.aff.catalog.price.request

create bridge source=topic:tibco.ac.discountmodel.topictarget=queue:tibco.aff.catalog.discount.request


36 | Post-installation Tasks

Chapter

5Configuring and Verifying Installation

After installation and post-installation tasks, a set steps are supposed to be performed to ensure successful installationof FOM. Configuring and verifying installation deals with tasks like copying the war files, restarting the server,and verifying the installation.

Topics

• Copying WAR files• Restarting the Server• Verifying Installation


Copying WAR files

AOPD can be deployed and used in two different ways. Either the collocated mode (which is the defaultmode) 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 default mode)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 and ope.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 needs to bedone for proper deployment of omsServer:a. Copy the files tibjms.jar, tibcrypt.jar and jms-2.0.jar to some folder. These files are typically

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 FOM, following instructions in the configuration section.


38 | Configuring and Verifying Installation

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


Configuring and Verifying Installation | 39

Verifying InstallationThis section provides instructions for verifying that TIBCO Fulfillment Order Management has installedcorrectly and for verifying the connectivity between various components. The AF_TestHarness projectreferred 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 Management engines,start Tomcat if it not started, and verify that the following servers have been started or deployed withoutany errors.To start the OMS server, perform the following steps:1. To start the server, run the following command:$cd $AF_HOME/apache-tomcat-<version>/bin$./startup.sh

Log File Located inApplication

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

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

2. Open the AF_TestHarness project available in $AF_HOME/samples/TestHarness/AF_TestHarness.zipusing TIBCO Designer. Import AF_Orchestrator_ForDesigner.projlib available under the$AF_HOME/be/projectLibs directory. Save the project as AF_TestHarness_Test to localize all theresources from the imported libraries and to update the required global variables values.

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



Figure 7: JMS Connection Parameters for Orchestrator

The AF_TestHarness project contains several BW processes integrating with AF Orchestrator or OMSServer components over the JMS channels as according to the following list. These are the stub processesjust to show how the integration is done, and to have an end-to-end run.• 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 different files.These files are created under the directory named as orderref of the corresponding order. These directoriesare created under a parent directory whose path is configured in testhHarness/outputPath globalvariable.

4. Start the following starter processes in TIBCO Designer.



Figure 8: 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 these events theexact state of the order/plan can be known.

The publishing of status change notifications for each entity is not enabled in Orchestrator out ofthe box. In order to subscribe to the status change notifications using the above mentioned processes,the notification publishing must be enabled for each entity using the respective flags. These flagsare available in the Orchestrator Configuration > Generic Configuration category in theConfigurator UI.

Orchestrator Task Stubs:• utilities/stubs/planItemActivateStub

• 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 finally sends anexecution success response to Orchestrator. The planItemSuspendStub and planItemActivateStubprocesses 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:



Sample Located InSend Model on QueueModel

$AF_HOME/samples/Models/

ProductModel.xml

tibco.aff.catalog.product.requestProduct Model

$AF_HOME/samples/Models/

PlanFragmentModel.xml

tibco.aff.catalog.planfragment.requestPlan FragmentModel

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 server according tothe 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 submit orders. For instance,http://localhost:8080/omsServer/api/orderService?wsdl.

8. Verify that the jobs of various processes selected in the test harness are created. The planItemExecute stubacts as the basic process component which processes and responds to the execution request sent byOrchestrator for each plan item.

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

Figure 9: Order View

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



Figure 10: Plan Grid View

Figure 11: Plan Gantt View



Chapter

6Fulfillment Order Management Migration

This section is relevant for users who have TIBCO Fulfillment Order Management 2.1.2 product to fulfill the ordersand are now upgrading the software to the new version TIBCO Fulfillment Order Management 3.0.0. While it isimportant to upgrade the software or environment to the more recent versions to exploit more efficient approachand processes for business benefits, it is equally important to preserve the business data during system upgrade.This document provides all the necessary steps and precautions to be taken while migrating from TIBCO FulfillmentOrder Management 2.1.2 to TIBCO Fulfillment Order Management 3.0.0.

Topics

• Migration from FOM 2.1.2 HF2 to FOM 3.0.0


Migration from FOM 2.1.2 HF2 to FOM 3.0.0The major steps required for migrating from Fulfillment Order Management 2.1.2 HF2 to 3.0.0 are:

• Prepare Fulfillment Order Management 2.1.2 for Migration• Backup Database• Install Fulfillment Order Management 3.0.0• Possible Changes in Process Components• Perform the Migration• Start Fulfillment Order Management 3.0.0 Environment

Prepare Fulfillment Order Management 2.1.2 for MigrationThis topic describes all the necessary steps that must be carried out before starting migration to TIBCOFulfillment Order Management (FOM) version 3.0.0.

The messages, corresponding to the in-process orders in 2.1.2, will not be allowed to remain in the pendingstate on the respective queues. These messages must be processed using Fulfilment Order Management 2.1.2before migration. However there are couple of queues on which messages will be pending.

1. Stop the northbound system (for example, Siebel CRM) which sends the order request messages toFulfillment Order Management for fulfilment. Doing this ensures that there will be no new order messagescoming on the queue tibco.aff.oms.ordersService. All the existing messages must be processed bythe OMS server component in 2.1.2.

2. Stop the southbound process component systems which are integrated with Fulfillment Order Managementfor processing various requests for plan items such as execute request, suspend request, activate request,and milestone release request. Doing this ensures that there will be no new messages coming on thefollowing queues. All the existing messages must be processed by Orchestrator 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 be no new messages coming from process components on the followingqueues associated with the JMS based data access interfaces which are used to get the order data and getor set the plan/plan item data from OMS. All the existing messages must be processed by OMS server in2.1.2.• tibco.aff.tds.order.read.request

• tibco.aff.tds.plan.request

• tibco.aff.tds.plan.read.request

Keep the Fulfillment Order Management 2.1.2 components running for appropriate time duration to let themprocess all pending messages associated with the in-flight orders on their inbound queues. The details forall the important queues are as follows:

1. If offer configuration and validation flag was enabled in OMS configurations, ensure that there are nomessages 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 migration of EMS channels as BE OCV component is nomore supported.

2. Ensure that there are no messages pending on the following queues related to the various types of orderrequests submitted to the orchestrator:– tibco.aff.orchestrator.order.submit


46 | Fulfillment Order Management Migration

– tibco.aff.orchestrator.order.suspend

– tibco.aff.orchestrator.order.activate

– tibco.aff.orchestrator.order.withdraw

3. If the order feasibility check is enabled in Orchestrator configuration, ensure that there are no messagespending on the following queues. The external feasibility provider component should process all therequest messages and the 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 the integrationbetween the orchestrator and the standalone AOPD components for execution plan generation. There willbe no messages on any of these queues if AOPD component is deployed in AOPD_colocated mode whichis specified as default in $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 prequalification handling is enabled in the orchestrator configuration, ensure that there are nomessages pending on the following queues. The external prequalification failed request handler shouldprocess all the request messages and the 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 for integrationbetween the orchestrator and external plan item error handler component for processing the failed planitem requests.– 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 external systemsto release the external dependencies on the plan items. All the messages must be processed by theorchestrator.– tibco.aff.orchestrator.planItem.externalDependency.release.request

8. Ensure that there are no messages pending on the following queue that are used by the 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 respectiveFulfillment Order Management components, there will be messages pending only on the following queues.These are the outbound queues for Orchestrator to send various requests for plan items to the processcomponents. The messages on these queues will be processed once the process component systems are startedafter the migration.• 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 or SetPlanItemdata access requests, there will be messages pending on either of the following queues or on the queuespassed as replyTo destinations in the requests. These are also the outbound queues for OMS server and the


Fulfillment Order Management Migration | 47

pending messages on these queues will also be processed once the process component systems are startedafter the migration.• 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 FOM 2.1.2, theycan be shut down at this stage. Also shutdown all the external components such as feasibility provider,pre-qualification failed request handler, external OPD, plan item error handler component, and so on.

Backup Database

Since the migration involves the changes in database, make sure to take the backup of the OMS databaseinstance which has been used by TIBCO Fulfillment Order Management 2.1.2.

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

• To install Fulfillment Order Management 3.0.0, see Installing in GUI Mode on page 26, Installing inConsole Mode on page 32, or Installing in Silent Mode on page 33.

• Fulfillment Order Management 3.0.0 is installed at the $TIBCO_HOME/af/3.0 location. Henceforth, it isreferred to as $AF_HOME.

Update the environment variables as per FOM 3.0.0 installation. For example:• 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 FOM 3.0.0. This has been done tomake them consistent across all the interfaces, in message header and payload too. If the process componentsystems implementation has any logic on the basis of these values then it must be updated with the newones. See the topic "Data Access Interfaces" in TIBCO Fulfilment Order Management Users Guide for the detailsof the codes and messages being returned by each interface in various situations.

Perform the MigrationThis section describes the step by step migration process. The utilities and resources to be used for migrationare available in $AF_HOME/migration directory.

Database Schema Migration

The database being used by FOM 2.1.2 needs the schema migration to be used with FOM 3.0.0. The databaseschema changes include the creation of few new tables and altering the existing ones for indexes and columnschanges. Before starting the database migration, ensure that the backup of the existing database is taken sothat it can be reused in case of any failures in migration.

Run the following script $AF_HOME/migration/db/UpgradeOMS_2.1.X_to_3.0.0.sql<fom_tablespace_name> using FOM database user credentials for migration. The name of the correspondingOracle table space must be given as an argument while running this script since the DDL statements in thescript requires that. The script can be run using Oracle sqlplus command line program or using Oracle SQLDeveloper UI client.



EMS Channel Migration

The EMS channels (queues, topics, bridges) being used by FOM 2.1.2 needs migration so that it can be usedwith FOM 3.0.0. The EMS channel migration includes creating new queues and topics, and deleting some ofthe existing queues, topics, and bridges that are obsolete.

Run the following script using TIBCO EMS administration command line utility for migration:$AF_HOME/migration/ems/UpgradeEMSChannels_2.1.X_to_3.0.0.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/migration/ems/UpgradeEMSChannels_2.1.X_to_3.0.0.txt.

Application and Log4J Configuration Properties for Migration

The application configuration and log4j configuration properties being used by FOM 2.1.2 needs to be migratedinto the corresponding files in FOM 3.0.0 installation. This can be done by running a Java based commandline utility which can be launched using $AF_HOME/migration/bin/migrateConfigProperties.sh. Thisutility requires all jar files present in $AF_HOME/migration/lib directory.

This utility refers the following three environment variables, which must be set before running it. The utilityfails with the appropriate error message, if any of the following environment variables are not set:1. JAVA_HOME- Path of Java installation example /opt/Java/jdk1.8.02. AF_HOME- Path of FOM 3.0.0 installation directory for example /opt/tibco/af/3.03. OLD_AF_HOME- Path of FOM 2.1.2 installation directory for example /opt/tibco/af/2.1

The utility refers the following two files from $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 two configuration properties whichwill be ignored.

2. MigrationLog4j.xml – This file contains the log4j configurations for the utility with the default log levelset at INFO level. It can be changed to DEBUG for more granular logging.

The utility writes the logs in $AF_HOME/migration/logs/fom-property-migration.log file.

This utility migrate the application configuration properties for the following components in the mentionedfiles.1. OmsServer and Orchestrator - $AF_HOME/config/ConfigValues_OMS.xml2. AOPD - $AF_HOME/config/ConfigValues_AOPD.xml3. JEOMS - $AF_HOME/config/ConfigValues_JEOMS.xml

It also migrates the log4j configuration properties for the following components in the mentioned files:

1. OmsServer, Orchestrator and JEOMS - $AF_HOME/config/OMSServerLog4j.xml2. AOPD - $AF_HOME/config/AOPDLog4j.xml3. OMSUI - $AF_HOME/config/OMSUILog4j.xml

The application and log4j configurations for OPE and OCS components cannot be migrated sincethese are the newly introduced components in version 3.0.0. Their configuration needs to be donemanually for the first time using FOM configurator web UI.

Start Fulfillment Order Management 3.0.0 EnvironmentThis topic covers the steps to start the Fulfillment Order management 3.0.0 environment:

Additional Configurations

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


Fulfillment Order Management Migration | 49

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

Post Installation Tasks

Perform the steps mentioned in the Post-installation Tasks on page 35.

Cluster Setup

The migrated database already contains the cluster members that were running in FOM 2.1.2 environment.For running additional Apache Tomcat instances in cluster or setting up altogether new cluster, refer to the"Deployment Topologies" section in the TIBCO Fulfillment Order Management Admin Guide.

Start all required Apache Tomcat server instances to start the configured FOM members in the cluster. Uponstarting up, the engines will load the existing data models (Product and Action) from the database. As perthe model loading configurations (online or offline), the additional data models will be loaded in FOM andalso be stored into the database as explained in the "Data Models" section in TIBCO Fulfillment OrderManagement Admin Guide.

Monitor the logs of each member to ensure that all the members have started successfully. At this stage theFulfillment Order Management 3.0.0 environment is ready to process any incoming requests. But since thereare no pending messages processing will not occur.

Start External Components

Start the external components which integrate with Fulfillment Order Management Orchestrator throughEMS and the ones that were stopped before starting migration. These include:1. Feasibility provider2. Prequalification failed handler3. External dependency releasing systems4. Plan item error handler

Start Southbound Process Components

Start the process component system. The process components will start processing the plan item execute,suspend, activate, and milestone release messages pending on the four outbound queues of Orchestrator andwill also send the corresponding reply messages to the orchestrator. The orchestrator will process the incomingreply messages to move the state of the corresponding plan items appropriately. Based on this, it will alsoschedule the requests for the further plan items in the execution plan to fulfil the orders. In this way, theorders that were in-progress in Fulfillment Order Management 2.1.2 before migration will be processed in3.0.0.

Start Northbound System

Start the northbound systems (for example, Siebel) to submit the new orders to be fulfilled using FulfillmentOrder Management 3.0.0.



Chapter

7Installation 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 configuring FulfillmentOrder Management?

If TIBCO Enterprise Message Service is not installed on the same machine as Fulfillment Order Management, thedestination creation fails. Create the destinations manually using the Enterprise Message Service Administrationutility on the machine where Enterprise Message Service is installed.

For details, see $AF_HOME/ems/AF_CreateEMSChannel.txt (for non-OMS component). Another script is used forOMS 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 OMS databaseusing the Database Wizard and see the tables created correctly in the database. What could be the problem?

Ensure you have configured the hibernate.default_catalog property correctly. This property can be configuredusing 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 the database user name of theOMS 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 of property

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 been added forfixing 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 Order Management will bedeployed do not have Internet connectivity?

Download the product_tibco_hibernate_3.6.9.001.zip file from thehttp://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 the migration to fail. However, anyerror other than the defined list results in the database migration failure.


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

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

DescriptionError Codes

Table or view does not existORA-00942

Name is already used by an existing objectORA-00955

Specified index does not existORA-01418

Sequence does not existORA-02289

Cannot drop nonexistent unique keyORA-02442

Cannot drop constraint - nonexistent constraintORA-02443

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 is not recommended.

5. Install EMS server 8.x.x.6. Update the environment variables accordingly on the EMS server box to reflect the new EMS installation path.

EMS 8.x.x is installed in the $TIBCO_HOME/ems/8.x folder. Ensure that you modify the environmentvariables 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 the shutdown

command.

Ensure that you are connected to the standby server by executing the info command and verifying thestate before issuing the shutdown command.

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

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

This step activates the standby server, resulting in the shared state conversion to the 8.x.x version. Theactive 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 successfully activated.6. To ensure that applications remain connected and they are processing messages, wait for a few minutes.


52 | Installation FAQs and Troubleshooting

7. Restart the previously active EMS server in standby mode with the 8.x.x EMS version with the same configurationfile 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 during failover, startthe 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 per locale -java.util.MissingResourceException: Can't find bundle for base name

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

Ignore this message


Installation FAQs and Troubleshooting | 53

tibco fulfillment order management installation and ... · tibco® fulfillment order management...

Documents