Chapter 2   Solaris Installation

This chapter provides the information required to install and configure TradingXpert software on the Solaris platform. Aside from having common hardware and software requirements, installation and configuration of TradingXpert depends upon whether the product is being deployed in a Sun ONE Application Server 6.5 or a Sun ONE Application Server 7.0 environment. Hence, this chapter is broken down into the following sections:

• "Hardware and Software Requirements"
• "Installing TradingXpert in a Sun ONE Application Server 6.5 Environment"
• "Installing TradingXpert in a Sun ONE Application Server 7.0 Environment"

Hardware and Software Requirements

---

The minimum requirements for installing TradingXpert on a Solaris platform are indicated in Table 2-1.

Table 2-1    Hardware and Software Requirements for Solaris 

Component	Requirements
Operating system	Solaris 2.6, 7, and 8
CPU	Sun Ultra™ 1 (or compatible) workstation that is TCP/IP networked
RAM	512 Mbytes
Hard drive space	The installed product requires approximately 200 Mbytes Document storage might require up to 6 Gbytes.
Other dependent software	See Table 1-1 for the supported versions of the Java Runtime Environment (JRE), Java Software Development Kit (JDK), Oracle, and supported versions of other software products on which TradingXpert depends.

Installing TradingXpert in a
Sun ONE Application Server 6.5 Environment

---

This section, specific to the Sun ONE Application Server 6.5, covers the following topics:

• Pre-Installation Tasks
• Installation Steps
• Configuring a TradingXpert Installation

Pre-Installation Tasks (Application Server 6.5)

You should perform the following tasks before installing TradingXpert in a Sun ONE Application Server 6.5 environment. These tasks should be performed under the same non-root user account: the ECXpert administrator account (for example, ecxadmin).

1. Check that all hardware and software requirements (Table 2-1) are met by your Solaris system.
2. Install ECXpert 3.6.2 and check that it is running properly. In particular, make sure that Oracle is up and running and that the BDGHOME environment variable is set on the ECXpert host machine (see "Checking the BDGHOME Environment Variable").

If ECXpert is running on a host machine different from the one on which TradingXpert is to be installed, then you will have to perform additional setup operations for TradingXpert to run in this configuration (see "Configuring TradingXpert to Run on a Different Machine from ECXpert").

3. Check that Sun ONE Web Server 6.0 is installed and configured properly.

If Sun ONE Web Server 6.0 has not previously been installed, install it and create an instance that will receive requests from TradingXpert's browser-based user interface (see "Creating a Web Server Instance for TradingXpert").

4. Check that Sun ONE Application Server 6.5 is installed and configured properly.

If Sun ONE Application Server 6.5 has not previously been installed, install it, and configure it to communicate with the Sun ONE Web Server instance to be used by TradingXpert (see your application server documentation for procedures).

Checking the BDGHOME Environment Variable

The value of the BDGHOME environment variable (see Table 3) must be properly set on the ECXpert host computer.

1. Check for BDGHOME.

The value of BDGHOME should be the full path to your ECXpert installed directory structure (see Table 3).

2. If BDGHOME has not been properly set:

setenv BGDHOME Root_ECX_Install/NS-apps/ECXpert

where Root_ECX_Install is the root installation directory of ECXpert software.

Creating a Web Server Instance for TradingXpert

1. Launch the Sun ONE Web Server's Administration Server.
2. Enter the Administration Console URL:

http://web_server_host:port

where web_server_host is the name of your web server's host computer, and port is the number of the port used for web server administration.

3. Log in under the web server administrator account.

The Administration Console window opens up.

4. Click Add Server.
5. Enter the Server Name.

This is the web server's host computer (web_server_host)

6. Enter the Server Port.

This is the number of the port on which the web server instance will be listening for requests from the TradingXpert browser-based user interface.

7. Enter the Server Identifier.

Use an instance identifier such as tradingx

8. Click OK.
9. Click Configure Your New Server.
10. Turn on the new server instance.

A success window confirmation appears.

11. Click OK.

Installation Procedures (Application Server 6.5)

Installation of TradingXpert requires you to locate the software distribution files in the Sun ONE Integration Server, B2B Edition CD-ROM set and run the TradingXpert install script.

To run the TradingXpert installation script

1. Log in under the same user account (for example, ecxadmin) that was used to install ECXpert, Sun ONE Web Server 6.0, and Sun ONE Application Server 6.5.
2. Insert the Sun ONE Integration Server B2B Edition 3.6.2 Solaris CD-ROM into your CD-ROM drive.
3. Change directories to the directory on the CD-ROM which contains the install_all file:

/TradingXpert3.6.2/install_bits/TX_for_AppServer6.5/

4. Type the following command at the command prompt:

install_all

The installer script requests that you enter the following values:

• the directory (Root_AS_Install) where Application Server 6.5 is installed. Enter the full path. There is no default value.
• the ECXpert version supporting TradingXpert
  Enter the value 3.6.2

Configuration Tasks (Application Server 6.5)

The TradingXpert installer script performs the following operations:

• sets up a directory structure and copies TradingXpert files into it (see "TradingXpert Directory Structure: Application Server 6.5")
• registers TradingXpert with the application server
• makes required modifications to the application server classpath.

The installer script does not, however, configure TradingXpert to inter-operate with ECXpert. Therefore, once TradingXpert software is installed, you have to perform the following configuration tasks:

• edit the TradingXpert configuration file (FXproperties) to specify the TradingXpert installation directory, the location of the ECXpert configuration file (ecx.ini), and the TradingXpert URL prefix (TX)
• copy TradingXpert map files, as needed, to the appropriate ECXpert map directory
• optionally, configure TradingXpert to run on a different host machine from ECXpert

These tasks are described in the sections that follow.

Editing the TradingXpert Configuration File

You are required to edit the TradingXpert configuration file (FXproperties)to specify the TradingXpert installation directory (FX.rootdir), the location of the ECXpert configuration file (FX.ecxini.file), and the TradingXpert URL prefix (FX.basedir).

The configuration file is located in:

TX_HOME/common/ (Application Server 6.5)

TX_HOME/config/ (Application Server 7.0)

The properties you are required to set, and a number of additional TradingXpert properties that you might optionally set, are described in Table 2-2.

Table 2-2    TradingXpert Configuration Properties 

Property	Default Value	Description
FX.rootdir	no default	Points to the TradingXpert installation directory (TX_HOME). Note that the path should end with a trailing slash. For example: /disk1/ias6.5/ias/APPS/FX/
FX.ecxini.file	no default	TradingXpert needs to access the ECXpert properties file (ecx.ini), normally located in BDGHOME/config.
FX.basedir	TX	The URL prefix you use to access the TradingXpert login screen and other TradingXpert functions.
FX.session.timeout	8 (in minutes)	Sets the time (in minutes) from the last user action to when TradingXpert times out. On timeout, the user is requested to log in again. For production environments, it is recommended that you set the timeout value to 30 minutes.
FX.remoteSubmission	FALSE	Specifies remote submission of documents by TradingXpert to ECXpert. A value of FALSE means TradingXpert and ECXpert run on the same host machine. A value of TRUE means TradingXpert and ECXpert run on different hosts. (See "Configuring TradingXpert to Run on a Different Machine from ECXpert".)
FX.remoteECXPathPrefix	no default	Only applies if TradingXpert and ECXpert run on different hosts (FX.remoteSubmission= TRUE). If needed (Solaris environments), this property specifies an ECXpert mount point to be pre-pended to directory paths used in the retrieval of ECXpert documents. (See "Configuring TradingXpert to Run on a Different Machine from ECXpert".)
FX.debug	FALSE	Sets the debugging flag. When TRUE, TradingXpert prints a large volume of messages to kjs logs to facilitate debugging. In production environments, the value should be set to FALSE.

Copying TradingXpert Map Files to ECXpert

The TradingXpert installer places default map files in the following directory:

TX_HOME/maps_etc/maps/solaris

These default map files can be used as is, as source for customizing your TradingXpert installation, or as examples for creating your own map files. Whatever the case, the map files used for TradingXpert processing need to be placed in the following ECXpert directory, where they can be accessed to perform data transformations:

BDGHOME/maps

If you want to test your TradingXpert installation using the test scenario provided with the product (see Chapter 4 "Testing Your TradingXpert Installation"), then copy the 850html.sun and html810.sun default maps to the BDGHOME/maps directory.

Configuring TradingXpert to Run on a Different Machine from ECXpert

This section provides additional configuration tasks required if TradingXpert is installed on a machine different from ECXpert, as shown in Figure 2-1. The tasks described assume the following scenario:

• "TX Host" is the host for TradingXpert. This includes, also, the Sun ONE Application Server and an Oracle client.
• "ECX Host" is the host for ECXpert and can also host an Oracle client (if Oracle is running on a remote host).
• "Oracle Host" is the host for the Oracle database server. (Oracle might also be running locally on ECX Host.)

Figure 2-1    TradingXpert and ECXpert on Different Machines

The general procedures required to set up this configuration are detailed below.

To configure TradingXpert to run on a machine different from ECXpert

1. Set up TX Host as if ECXpert were installed locally. This involves providing access to the ECXpert directory structure and configuration file (ecx.ini), and setting a BDGHOME environment variable. See "Setting up TX Host as if ECXpert Were Installed Locally".
2. Set up TX Host to access the Oracle database used by ECXpert (it is assumed that ECX Host is already set up to access the database). See "Setting up TX Host to Access the Oracle Database Used by ECXpert".

These procedures apply to an initial installation of TradingXpert on a separate machine, or to a migration of TradingXpert away from the machine hosting ECXpert. They allow TradingXpert to submit document files to ECXpert, retrieve documents from ECXpert, and access the partnership and process tracking information stored in the Oracle database.

Setting up TX Host as if ECXpert Were Installed Locally

To set up TX Host as if ECXpert were installed locally

1. Mount the ECX Host's ECXpert installed directory structure (the directory referenced by BDGHOME) on TX Host.
2. Set the BDGHOME environment variable on TX Host.

The BDGHOME environment variable on TX Host should point to the same directory as the BDGHOME environment variable on ECX Host.

3. Give the TradingXpert user privileges to access (read) ECXpert's BDGHOME/data directory.
4. Restart TX Host.

This is necessary for the changes in environment variable settings to take effect.

5. Edit the ecx.ini file on ECX Host to specify a static TCP/IP port for communication with ECXpert (this is used to submit documents to ECXpert):

1. Open the ecx.ini file.

The file is located in the BDGHOME/config directory

2. Modify the [tcpip-connector] section as follows:

port_location = static
admin_port_type = manual
admin_port = any unused port
listener_port_type = manual
listener_port = any unused port

3. Restart ECXpert for these changes to take effect.

6. Modify TradingXpert's FXproperties file on TX Host.

1. Turn on the FXremoteSubmission property:

FX.remoteSubmission: TRUE

2. Set the FXremoteECXPathPrefix property to specify the ECXpert mount point in Step 1. This path is to be pre-pended to directory paths specified in the ecx.ini file for the retrieval of ECXpert documents. For example, if the mountpoint is /h/EXC_Host, then TradingXpert will retrieve files from ECXpert at /h/ECX_Host/BDGHOME/data...
3. Restart TradingXpert on TX Host for property edits to take effect.

Setting up TX Host to Access the Oracle Database Used by ECXpert

To set up TX Host to access Oracle

1. Install the Oracle client on TX Host, if not already installed.
2. Give the TradingXpert user privileges to access Oracle client software.
3. Edit the tnsnames.ora file to reference the Oracle Server
4. Check that the ORACLE_HOME and ORACLE_SID variables are properly set on ECX Host.

These entries are found in the [ORACLE_ENV] section of the ecx.ini file, locate the DB_SERVER parameter.

5. Check the DB_SERVER parameter of the ecx.ini file.

In the [DB_SECTION] section of the ecx.ini file, locate the DB_SERVER parameter. If not already included, enter the following lines in the [DB_SECTION] section:

   [DB_SECTION]
   DB_SERVER=Oracle DB alias
   DB_USER=Oracle username
   DB_SERVER=Oracle password

where Oracle DB alias is the Oracle database alias from the tnsnames.ora file in Step 3.

Installing TradingXpert in a
Sun ONE Application Server 7.0 Environment

---

This section, specific to the Sun ONE Application Server 7.0, covers the following topics:

• Pre-Installation Tasks
• Installation Steps
• Configuring a TradingXpert Installation

Pre-Installation Tasks (Application Server 7.0)

You should perform the following tasks before installing TradingXpert in a Sun ONE Application Server 7.0 environment. These tasks (except where noted) should be performed under the same non-root user account: the ECXpert administrator account (for example, ecxadmin).

1. Check that all hardware and software requirements (Table 2-1) are met by your Solaris system.
2. Install ECXpert 3.6.2 and check that it is running properly. In particular, make sure that Oracle is up and running and that the BDGHOME environment variable is set on the ECXpert host machine (see "Checking the BDGHOME Environment Variable").

If ECXpert is running on a host machine different from the one on which TradingXpert is to be installed, then you will have to perform additional setup operations for TradingXpert to run in this configuration (see "Configuring TradingXpert to Run on a Different Machine from ECXpert").

3. Check that Sun ONE Application Server 7.0—which includes a built-in web server—is installed and properly configured. (If Sun ONE Application Server 7.0 has not previously been installed, you must log in as root to install it.) With the application server running, perform the following steps:

1. Log in under your TradingXpert user account (for example, ecxadmin).
2. Create an application server instance that will host TradingXpert (see "Creating an Application Server Instance for TradingXpert," below).
3. Modify the server.policy file for the application server instance so that the TradingXpert setup script can delete temporary files (see "Modifying the server.policy File").

Creating an Application Server Instance for TradingXpert

1. Launch the Sun ONE Application Server's Administration Server.
2. Enter the Administration Console URL:

http:\\AS_admin_host:port

where AS_admin_host is the server hosting the Application Server's administration server and port is the port number of the listener.

3. Log in under the application server administrator account.

The Administration Console window opens, displaying existing application server instances.

4. Click New.

The new application server instance dialogue is displayed.

5. Enter the Instance Name.

This is the name of the application server instance that will host TradingXpert (for example, tradingx).

6. Enter the HTTP Port.

This is the port on which the application server instance (web server instance) will be listening for requests from the TradingXpert browser-based user interface.

7. Enter a user account in the Run As User field.

Use the account under which TradingXpert will be running (for example, ecxadmin).

8. Click OK.

The Administration Console window will display the new application server instance.

9. Click the link for the newly created application server instance.

A multi-tabbed dialog is displayed.

10. Click Start to turn on the new server instance.

Modifying the server.policy File

To modify the server.policy file

1. Open the server.policy file found in the following directory:

Root_AS_Install/domains/domain1/appServer_instance/config/

where Root_AS_Install is the root installation directory for the application server and appServer_instance is the name of the application server instance to be used by TradingXpert (for example, tradingx)—see "Creating an Application Server Instance for TradingXpert".

2. Find the following entry:

permission java.io.FilePermission "<<ALL FILES>>", "read,write";

3. Add permission to delete.

"read,write,delete"

4. Save the file.
5. Restart the appliction server instance for the change to take effect.

Installation Procedures (Application Server 7.0)

Installation of TradingXpert requires you to locate the software distribution files in the Sun ONE Integration Server, B2B Edition CD-ROM set and run the TradingXpert setup script.

To run the TradingXpert setup script

1. Log in under the same user account (for example, ecxadmin) that was used to install ECXpert and to create the application server instance for TradingXpert (see "Creating an Application Server Instance for TradingXpert").
2. Insert the Sun ONE Integration Server B2B Edition 3.6.2 Solaris CD-ROM into your CD-ROM drive.
3. Change directories to the directory on the CD-ROM which contains the setup file:

/TradingXpert3.6.2/install_bits/TX_for_AppServer7.0/

4. Type the following command at the command prompt:

setup

The installer script requests that you enter the following values:

• the TradingXpert application directory, TX_HOME (see "TradingXpert Application Directory" and Table 3)
  Be sure to enter the full path. There is no default value.
• the value of the ECXpert BDGHOME environment variable (see Table 3).
  Be sure to enter the full path. There is no default value.
• the domain of the application server instance that will support TradingXpert (see "Creating an Application Server Instance for TradingXpert").
  Be sure to type in the domain name (for example, domain1). There is no default value.
• the application server administrator account and password
• the name of the application server instance in which TradingXpert is to run (for example, tradingx)
• the application server administrator access port number

The installer uses these values to modify the FXproperties and TX.war files, deploy the TX.war file, update the TradingXpert native library directory path, and, finally, stop and restart the application server instance.

Configuration Tasks (Application Server 7.0)

The TradingXpert installer script performs the following operations:

• places a number of TradingXpert files into a predefined directory structure (see "TradingXpert Application Directory").
• deploys the TradingXpert web archive file (TX.war):

• configures the application server (and included web server) to run TradingXpert
• places a number of files in the application server directory structure (see "J2EE Module Directory").

• modifies the TradingXpert configuration file (FXproperties) to point to the root TradingXpert installation directory and to the ECXpert configuration file

Once TradingXpert software is installed, however, you still have to perform two optional configuration tasks, depending on your use of TradingXpert, for TradingXpert to inter-operate with ECXpert:

• copy TradingXpert map files, as needed, to the appropriate ECXpert map directory (see instructions in "Copying TradingXpert Map Files to ECXpert")
• configure TradingXpert to run on a different host machine from ECXpert (see instructions in "Configuring TradingXpert to Run on a Different Machine from ECXpert").