Installation Guide for Oracle Siebel eStatement Manager

Installation Guide for Oracle Siebel eStatement Manager Version 4.7

May 2009

For IBM AIX 5.3 Operating Environment, IBM WebSphere 6.1 Server, and Oracle Database

Copyright © 2005, 2009 Oracle. All rights reserved.

The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS

Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

Oracle, JD Edwards, and PeopleSoft are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.


3

Contents

1 About This Guide 7

2 Preparing Your Platform for Installation 11

Overview of the Installation Process 11 Oracle Siebel eStatement Manager System Requirements 12

3 Installing Oracle Siebel eStatement Manager 15

UNIX Permissions for Installation 15 Installing Oracle Siebel eStatement Manager from the Distribution Medium 15 Installing Design Tools 15

Installing in a Distributed Environment 15

Configuring Your Database 16 Oracle Siebel eStatement Manager Directory Structure 16

4 Configuring Your Database Server 19

UNIX Permissions for Your Database Server 19 Using Database Partitioning with Oracle Siebel eStatement Manager 20

5 Configuring Oracle Siebel eStatement Manager for Oracle Database 11g 21

Preparing to Run the Ant Script to Build the Database 21 Configuring edxadmin.properties 21 Configuring a New Oracle Siebel eStatement Manager Database 23 Migrating an Existing Oracle Siebel eStatement Manager Database 27 Configuring a New Oracle Siebel ePayment Manager Database 27

Configuring the Properties File 27

Configuring the Oracle Siebel ePayment Manager Database Using the Automated Ant Target 28

Contents

4 Installation Guide for Oracle Siebel eStatement Manager Version 4.7

Configuring the Oracle Siebel ePayment Manager Database Manually Database Using the Ant Script 29

Migrating the Oracle Siebel ePayment Manager Database 30

6 Using the IBM WebSphere Console to Configure JMS Resources 33

Accessing the IBM WebSphere Console 33 Creating, Starting, and Stopping an IBM WebSphere Application Server Account 33 Setting Classpath and Environment Variables for IBM WebSphere 34 Configuring eXtended Middleware Architecture 36

Configuring eXtended Middleware Architecture for Notification 36

Configuring Hibernate Properties 36

Configuring the Logger 37 Configuring Java Resources 39

Configuring the Data Source 39

Configuring the JMS Resources 39

7 Configuring IBM WebSphere Application Server for UNIX 43

UNIX Permissions for IBM WebSphere Application Server 43 Starting and Stopping IBM WebSphere 44 UNIX Environment Variables for IBM WebSphere 44 Capturing Your UNIX Environment for Oracle Siebel ePayment Manager 47

8 Configuring Java Resources for WebSphere for UNIX 49

Setting Total Transaction Lifetime Timeout 49 Configuring Java Database Connectivity for Oracle Siebel eStatement Manager 49

About JDBC Connections for Oracle Siebel eStatement Manager 50

Configuring JDBC Connections for IBM WebSphere 50

Creating a JDBC Provider 50

Contents

Installation Guide for Oracle Siebel eStatement Manager Version 4.7 5

Establishing Database Connectivity for Oracle Siebel eStatement Manager 51

Testing Data Sources 53 Configuring JMS Resources for Oracle Siebel eStatement Manager 53 Creating J2C Authentication Aliases 57 Deploying the Oracle Siebel eStatement Manager Application 57 Running Oracle Siebel eStatement Manager 60 Running Scheduler 61

9 Running Oracle Siebel eStatement Manager 63

Setting the Security Level 63 Configuring the sas.client.props File 63

10 Packaging the Hibernate and C3PO Libraries 65

Prerequisites to Packaging the Hibernate and C3PO Libraries 65 Configuring the Environment for Packaging the Hibernate and C3PO Libraries 65 Downloading and Installing the Third-Party Libraries 66 Packaging Oracle Siebel eStatement Manager 66 Failure Recovery 67

11 Uninstalling Oracle Siebel eStatement Manager 69

Appendix A: Configuring a User Repository 71

Configuring a User Repository 71

Appendix B: Database Server Environment Variables 73

Oracle Database 11g Server Environment Variables 73

Index 75

Contents



7

About This Guide1

This guide describes how to install Oracle® Siebel eStatement Manager and configure the third-party platforms that support the production environment for Oracle Siebel eStatement Manager.

This guide is intended for system administrators and other technical personnel responsible for installing, configuring, and maintaining Oracle Siebel eStatement Manager. It assumes in-depth understanding of and practical experience with system administrator responsibilities, including the following tasks.

Operating System Administration Requirements Start up and shut down the system

Log in and out of the system

Determine software patch/pack levels

Install software & patches/packs

Navigate the file system

Manipulate text files

Create files and directories

Change permissions of files and directories

Use basic network commands

Transfer files with FTP

Monitor processes & system resource usage

Perform system backups and recovery

Implement system security

Database Administration Requirements Install and configure your database server

Start and stop your database server and database instances

Use administrative tools

Manage users, privileges, and resources

Create an operational database

Manage database files

Manage tables and indexes

Back up and restore databases

About This Guide ▪ Overview of the Installation Process


Monitor database performance

If you are unfamiliar with any of these tasks, please consult the related documentation for your system requirements.

Application Server Administration Requirements Install and configure your application server

Start and stop your application server

Use administrative tools

Manage users, privileges, and resources

Configure Java resources

Package and deploy Web applications

Monitor application server performance

This guide does not describe general UNIX or Microsoft Windows system administration. See the appropriate UNIX or Microsoft Windows user documentation.

If you are unfamiliar with any of these tasks, consult the related documentation for your system requirements.

Related Documentation For more information about using Oracle Siebel eStatement Manager, see the guides listed in the following table.

Print Document Description

Installation Guide for Oracle Siebel eStatement Manager

How to install and configure eStatement Manager in a distributed environment.

Deploying and Customizing J2EE Applications Guide for Oracle Siebel eStatement Manager

How to deploy and customize the J2EE applications provided by eStatement Manager. This guide also describes how to deploy the Sample application provided by eStatement Manager and how to validate that it is set up correctly by running a job through your installed eStatement Manager environment.

Data Definition (DefTool) Guide for Oracle Siebel eStatement Manager

How to create Data Definition Files (DDFs) for use in indexing your application and extracting data for live presentment.

Presentation Design (Composer Guide) for Oracle Siebel eStatement Manager

How to create Application Logic Files (ALFs) to present statement data for dynamic online display.



Print Document Description

Administration Guide for Oracle Siebel eStatement Manager

How to set up and run a live Oracle Siebel eStatement Manager application in a J2EE environment.

SDK Guide for Oracle Siebel eStatement Manager

How to work with auditing data streams, user management frameworks, line item disputes and annotations, custom jobs, content access, and charting.

Reporting Guide for Oracle Siebel eStatement Manager

How to use the Reporting and Analytics Module to create preconfigured telecommunication reports from live and indexed data for various criteria.

Troubleshooting Guide for Oracle Siebel eStatement Manager

How to initiate the troubleshooting process, identify critical information about what is happening in your system and applications when a problem occurs, and resolve the problem.

Migration Guide for Oracle Siebel eStatement Manager

How to migrate an existing Oracle Siebel eStatement Manager database to a newer version.

Oracle Siebel eStatement Manager 4.7 Release Notes

This discusses any open issues at the time of release of the application.

The SDK and Installation Guide for Oracle Siebel eaAssist

How to install and set up Oracle Siebel eaAssist.

http://download.oracle.com/docs/cd/E10573_01/books/eaAssistSDKInstall_v47.pdf

http://download.oracle.com/docs/cd/E10573_01/books/eaAssistSDKInstall_v47.pdf


11

tform is ready:

ation server.

For distributed environments, make sure you have any required database client software installed on your application server and any other client computers of your database server.

The process of installing and setting up Oracle Siebel eStatement Manager includes the following

1 g and ature.

m Services and Oracle Siebel eStatement Manager on different servers, you must install Platform Services and start it running before installing

2 Installing DefTool and Composer on Microsoft Windows XP Professional or Microsoft Windows

d.

After you successfully install Oracle Siebel eStatement Manager and configure your database and application servers, you can customize and deploy your J2EE application.

the following:

Connect to your Oracle Siebel eStatement Manager database before configuring your application server.

our Platform for Installation

2 Preparing Y

Before installing Oracle Siebel eStatement Manager, verify that your pla

Install and test required hardware and software for your platform.

Define required user and group permissions for your database server and applic

Start and test your database server. See your database server documentation.

Start and test your application server. See your application server documentation.

Overview of the Installation Process

steps:

Installin Oracle Platform Services and Oracle Siebel eStatement Manager on your databaseapplication servers. You can install these individually or together using the Custom install fe

NOTE: If you are installing Platfor

Oracle Siebel eStatement Manager.

Server 2003 SP1.

3 Configuring the database server.

4 Configuring the application server.

Follow the chapters in this guide in sequence, consulting your third-party documentation as neede

Configuring your Database Server Configuring your database server requires you to do

Define database server environment variables.

Create and configure the database for Oracle Siebel eStatement Manager.

Preparing Your Platform for Installation ▪ Oracle Siebel eStatement Manager System Requirements


Configuring your Application Server Configuring your application server requires you to do the following:

Define application server environment variables.

Configure JDBC resources for Oracle Siebel eStatement Manager on your application server.

Configure JMS resources for Oracle Siebel eStatement Manager on your application server.

Customizing and Deploying J2EE Applications After installing Oracle Siebel eStatement Manager and configuring your database and application servers, you can perform any of the following tasks:

1 Customize your J2EE Web applications for Oracle Siebel eStatement Manager.

2 Deploy J2EE Web applications for Oracle Siebel eStatement Manager.

3 Deploy your custom J2EE Web application.

Oracle Siebel eStatement Manager System Requirements The following are system requirements for Oracle Siebel eStatement Manager.

Operating Systems IBM AIX 5.3

For Microsoft Windows-based DefTool and Composer Tools only, either one of these:

Microsoft Windows XP Professional

Microsoft Windows Server 2003 SP1

Hardware CD-ROM

Disk space (database) 2.6 Gigabytes

Disk space (software) 60 Megabytes

Swap space 512 Megabytes per CPU (1 Gigabyte recommended)

RAM 512 Megabytes per CPU (1 Gigabyte recommended)

JAVA and C++ J2RE 1.5.0 IBM J9 2.3 AIX ppc-32 j9vmap3223-20060504



Supported Database Servers Oracle Database 11g (version: 11.1.0.6, need to install Patch 6800649)

Native Oracle Partition Support for Index Tables (Purging)

Oracle Database 11g client software (for application server)

Oracle Database 10g JDBC driver

Supported Application Servers IBM WebSphere 6.1.0.19

Supported Browsers Internet Explorer 6.0, 7.0

Firefox 2.0

Netscape 8.1.2

Open Source Items The following required open source library binaries are not distributed with the product:

Apache Ant 1.6.5 or higher is required to run the supplied Ant database scripts.

Hibernate 3.1.3 is required for high performance object/relational persistence and query services.

c3p0 0.9.0 is required for JDBC3 connection and statement pooling.


15

This chapter assumes in-depth understanding of and practical experience with system administration responsibilities. Consult your system documentation as necessary.

You do not require root privilege on each server to install and uninstall Oracle Siebel eStatement M Consu stem admi r details of user setup.

UNIX Permissions for Installation

anager components. lt your sy nistrator fo

Operating System Default Example

IBM AIX root:other edxadmin:edxadmin

Installing Oracle Siebel eStatement Manager from the Distribution Medium For your application and database servers, you will also need the owner (user) and group permissions specified during installation.

CAUTION: It is recommend not to administer Oracle Siebel eStatement Manager with the user and group nobody:nobody.

NOTE: Client browsers connecting to Oracle Siebel eStatement Manager must be enabled to run click

For the latest software and hardware requirements, see the release notes that came with your distribution.

Install the DefTool and Composer tools on either a Microsoft Windows computer on your network. Follow the instructions provided in the README file that comes with the distribution.

ling in a distributed environment, be sure that you have installed all Oracle Siebel proceeding to the database configuration chapter

3 g Oracle Siebel eStatement Manager Installin

JavaScript. To check whether JavaScript is enabled for Netscape - Under Edit, then Preferences,Advanced, and make sure Enable JavaScript is checked.

Installing Design Tools

Installing in a Distributed Environment If you are instaleStatement Manager components as follows before for using Ant.

Installing Oracle Siebel eStatement Manager ▪ Oracle Siebel eStatement Manager Directory Structure


er(s)

Tools components on a Microsoft Windows computer (accessible to UNIX servers)

Database client software on application server(s)

If you have installed Oracle Siebel eStatement Manager on a single computer using the Full ing Ant.

ded to create and

when prompted during installation.

iebel eStatement Manager in the same top-level cation server.

h equired Library Files e files must be present in EDX_HOME/lib/AIX_5.3:

so

libIndexer.so

nents eStatement/db contains platform-specific subdirectories for database creation and configuration. Each

tains migration scripts. Be sure to

Components The eStatement/J2EEApps directory contains platform-specific subdirectories for Oracle Siebel eStatement Manager J2EE and Web applications to be deployed to your application server. Be sure to deploy the correct version for your platform.

Database components on database server(s)

Application Server components on application serv

Configuring Your Database

installation option, you can proceed directly to the database configuration section for us

Oracle Siebel eStatement Manager Directory Structure The home directory of Oracle Siebel eStatement Manager contains all the files neeconfigure the production database for Oracle Siebel eStatement Manager. When you install Oracle Siebel eStatement Manager components, you must enter a destination directory. By default, this directory is /eStatement, which has a predefined hierarchical directory structure.

To designate a different destination directory, enter the pathname

TIP: It is recommended that you install Oracle Sdirectory on both the database server and the appli

W ere to Find RTh following library

libdb_cxx-4.1.

libFormatter.so

libxerces-c2_1.so

Where to Find Database Compo

/db subdirectory also contains the directory migration, which conuse the correct version for your platform.

Where to Find Application Server



Where to Find Sample Applications The eStatement /samples directory contains sample J2EE, Web, and applications for use with the Oracle Siebel eStatement Manager. For more information on sample applications, see Deploying and Customizing J2EE Applications for Oracle Siebel eStatement Manager.

Where to Find Input and Output Data The eStatement/AppProfiles directory stores information on each new Oracle Siebel eStatement Manager application created in the Command Center. The eStatement/Input directory is the default input directory used by each Command Center job. The eStatement/Data directory stores data processed by the Command Center. The job output directory is eStatement/Output.

An additional directory, eStatement/Store, appears when the first Command Center job runs. The Store directory holds temporary files created during job run time. When the job completes, Oracle Siebel eStatement Manager automatically cleans up these temporary files.

Where to Find Online Documentation You can access online help in Command Center, DefTool, and Composer.


19

4Configuring Your Database Server

This chapter assumes in-depth understanding of and practical experience with database administration. Consult your database documentation as necessary. For distributed environments, make sure you have any required database client software installed on your application server and any other client computers of your database server.

It is recommended that you install and configure Oracle Siebel eStatement Manager in the same top-level directory structure, first on the database server, then the application server.

This chapter provides instructions for configuring your database server to support a new Oracle Siebel eStatement Manager database. It includes:

UNIX permissions for your database server

Starting and stopping your database server

Using database partitioning with Oracle Siebel eStatement Manager

CAUTION: The installation and configuration examples in this guide use default Oracle Siebel eStatement Manager pathnames, privileges, and permissions. If you choose not to accept the default values, make sure your values are consistent on all servers across your installation of Oracle Siebel eStatement Manager.

UNIX Permissions for Your Database Server Before creating the database for Oracle Siebel eStatement Manager using Ant build scripts, verify that the owner and group permissions (userid:groupid) of the database directory, including all subfolders, are set to the DB Admin user defined during database installation.

This guide uses the example username and password edx_dba:edx as the owner and group for the Oracle Database 11g user. This is the user for your database instance. This guide also uses the example database instance name edx0.

It is recommended that you install Oracle Siebel eStatement Manager database components with the default owner and group for your platform. After installing, change the user and group ownership of Oracle Siebel eStatement Manager database server components to that of the DB Admin user.

Database Database Admin User Database User

Oracle Database 11g Oracle:dba edx_dba:edx

NOTE: The DB Admin user has special privileges on Oracle Database 11g. For details on owner and group permissions for your database server, please consult Oracle Database 11g documentation for your platform.

If your database administrator uses custom user and group permissions, then you can reset these permissions with the chown command.

Configuring Your Database Server ▪ Using Database PartiTtTioning with Oracle Siebel eStatement Manager


To reset user and group permissions for Oracle Database 11g

1 Switch user to root.

su - root

2 Recursively change the user and group permissions of your EDX_HOME directory and all subdirectories to the Oracle Siebel eStatement Manager instance owner.

chown -R edxadmin:edxadmin /opt/eaSuite/eStatement

3 Recursively change the user and group permissions of your EDX_HOME database directory and all subdirectories to the database instance owner.

chown -R oracle11:dba /opt/eaSuite/eStatement/db

TIP: Verify the owner information in any profile files used by the database server owner and application server owner. See your server documentation for details.

Developers and system administrators need to be familiar with how to stop and start a database server and an active Oracle Siebel eStatement Manager database instance for your platform.

For details on starting and stopping your database server and instances, consult the database documentation for your platform.

Using Database Partitioning with Oracle Siebel eStatement Manager Database partitioning (partition splitting) reduces the number of tables the system must scan when indexing your data. You specify the number of partitions when you create a DDN in the Command Center. At the first run of the Indexer job, Oracle Siebel eStatement Manager creates and populates a set of partitioned index tables to maintain your dynamic data.

NOTE: Oracle does not support partitioned views. Native partitioning can be applied to a single index table depending on your Oracle software license. For Oracle Database 11g, it is recommended that you create one index table per DDN, and use the native table partitioning functionality for higher performance. It is recommended that you choose the range partition on the Z_DOC_DATE column.


21

This chapter describes how to configure Oracle Siebel eStatement Manager for Oracle Database 11g.

Preparing to Run the Ant Script to Build the Database You can use Ant build scripts to create and configure the database for Oracle Siebel eStatement Manager. You must follow the steps required to prepare for running Ant.

To prepare to run the Ant script

1 Install and upgrade your database server software as necessary.

2 Make a full backup of your current database.

3 Check the database product Release Notes for disk space requirements and confirm that you have sufficient disk space on your database server.

Insufficient disk space can cause database configuration to fail.

4 Install Apache Ant version 1.6.5 or higher. This software can be downloaded from http://ant.apache.org/. The installation directions can be found on that site as well.

5na

Configuring Oracle Siebel eStatement Ma ger for Oracle

5 Set ANT_HOME and JAVA_HOME environment variables.

6 Configure Ant property files.

Configuring edxadmin.properties This step in setting up the database server is to edit the properties file that controls the Oracle Siebel eStatement Manager production database Ant installation.

CAUTION: When creating an Oracle Database 11g database, limit its name to eight characters. Defining or entering an Oracle SID with more than eight characters causes the configuration to fail.

The following example for EDX_HOME/db/<db>/edxadmin.properties shows sample values that you must replace with the appropriate paths, usernames, passwords, and SID settings:

ORACLE_HOME=/vol1/oracle11/11.1.0.6

ORACLE_BASE=/vol1/oracle11/

Configuring Oracle Siebel eStatement Manager for Oracle Database 11g ▪ Configuring edxadmin.properties


DB_USER=edx_dba

DB_PASSWD=edx

DB_SID=EDX0

SYS_PASSWD=oracle

-- file location of data tablespace

L_DB_EDX_DATA_TB_FILE_LOC=/data/oradata

-- file location of index data tablespace

L_DB_EDX_INDX_TB_FILE_LOC=/data/oradata

-- file location of Application data tablespace

L_DB_APP_DATA_TB_FILE_LOC=/data/oradata

-- file location of Application index data tablespace

L_DB_APP_INDX_TB_FILE_LOC=/data/oradata

-- file location of Detail extractor data tablespace

L_DB_LOAD_DATA_TB_FILE_LOC=/data/oradata

-- file location of Detail extractor index tablespace

L_DB_LOAD_INDX_TB_FILE_LOC=/data/oradata

-- file location of FS data tablespace

L_DB_FS_DATA_TB_FILE_LOC=/data/oradata

-- file location of FS index tablespace

L_DB_FS_INDX_TB_FILE_LOC=/data/oradata

-- file location of Stage data tablespace

L_DB_STG_DATA_TB_FILE_LOC=/data/oradata

-- file location of Stage index tablespace

L_DB_STG_INDX_TB_FILE_LOC=/data/oradata

--- file location of the first control file

DB_CONTROL_FILE_LOCN1=/data/oradata

--- file location of the second control file


--- file location of the third control file


--- file location of Redo-Log file

REDO_LOG_FILE_LOCN=/data/oradata

-- file location of System tablespace

Configuring Oracle Siebel eStatement Manager for Oracle Database 11g ▪ Configuring a New Oracle Siebel eStatement Manager Database


SYSTEM_FILE_LOCN=/data/oradata

-- file location of Temporary tablespace

TEMP_FILE_LOCN=/data/oradata

-- file location of UNDO tablespace

UNDO_FILE_LOCN=/data/oradata

TRACE_FILE_LOCN=/data/oradata

-- file location of backup file

L_BACKUP_FILE=/data/oradata/expedxtest.dmp

-- file location of backup log file

L_LOG_FILE=/data/oradata/expedxtest.log

Configuring a New Oracle Siebel eStatement Manager Database Follow these steps to install on a new Oracle Siebel eStatement Manager database.

To configure a new Oracle Siebel eStatement Manager database

1 Switch user to the database admin user. It is recommended that you use the administrative user to create files. For example.

$ su – oracle11

2 Change directory to your Oracle Siebel eStatement Manager database home directory. For example:

cd <EDX_HOME>/db/oracle

3 Do one of the following:

You can use multiple Ant targets that automate the installation process or install manually. To install manually, skip to Step 9.

If installing on a new instance, use the install-new target, which creates new Oracle Siebel eStatement Manager instances with the SIDs specified in the properties file:

ant install-new

4 If installing on a new instance, check the following log files for errors:

create_db.log

configure_ts.log

setup_user.log



create_tables.log

create_views.log

compile_sproc.log

NOTE: After setting up the database, configure required Oracle services.

5 If installing on an existing schema, use the install-existing target, which creates new Oracle Siebel eStatement Manager schemas on an existing instance with the usernames and passwords specified in the properties file:

ant install-existing

6 If installing on an existing schema, check the following log files for errors:

configure_ts.log

setup_user.log

create_tables.log

create_views.log

compile_sproc.log

7 To run each installation step manually, start the Ant script with the following command:

ant

The main menu appears:

Main:

[echo] [1]. Install eaSuite Database

[echo] [2]. Initial Data Population

[echo] [Q]. Quit

[input] Enter your selection (1, 2, q, Q)

a. Select Option 1, Install eaSuite Database. The Install eaSuite Database menu appears:

CreateInitDatabaseMenu:

[echo] Install eaSuite Database

[echo] [1]. Create Oracle Instance

[echo] [2]. Shutdown Database

[echo] [3]. Startup Database

[echo] [4]. Install Application Database I - Create tablespace/user

[echo] [5]. Install Application Database II - Create tables

[echo] [6]. Install Application Database III - Install PL/SQL Code Base



[echo] [Q]. Quit

[input] Enter your selection (1, 2, 3, 4, 5, 6, q, Q)

b. Select Option 1, Create Oracle Instance.

This step creates a database instance for Oracle Siebel eStatement Manager, and defines a data dictionary and stored procedure for the new database. If this step is successful, the following message appears:

init:

[echo] Creating database instance...please wait

[exec] SQL*Plus: Release 11.1.0.6.0 - Production on Thu Nov 6

17:59:26 2008

[exec] Copyright (c) 1982, 2007, Oracle. All rights reserved.

[exec] Connected to an idle instance.

[exec] ORACLE instance started.

[exec] Total System Global Area 1258291200 bytes

[exec] Fixed Size 1978336 bytes

[exec] Variable Size 318771232 bytes

[exec] Database Buffers 922746880 bytes

[exec] Redo Buffers 14794752 bytes

[exec] SQL> Disconnected from Oracle Database 10g Enterprise

Edition Release

[exec] With the Partitioning, OLAP and Data Mining options

[echo] Initializing database instance...please wait

This option can take more than 30 minutes to complete. Check the create_db.log file for errors.

After creating the database instance, the command prompt reappears.

c. Execute the Ant build script again to display the CreateInitDatabaseMenu menu.

d. Select Option 2, Shutdown Database. If this step is successful, the following message appears:

ShutdownDatabase:

[echo] Shutdown database...please wait

[exec] Database closed.

[exec] Database dismounted.

[exec] ORACLE instance shut down.



e. Select Option 3, Startup Database. If this step is successful, you see the following message:

StartupDatabase:

[echo] Startup database...please wait

[exec] ORACLE instance started.

[exec] Total System Global Area 1258291200 bytes

[exec] Fixed Size 1978336 bytes

[exec] Variable Size 318771232 bytes

[exec] Database Buffers 922746880 bytes

[exec] Redo Buffers 14794752 bytes

[exec] Database mounted.

[exec] Database opened.

f. Select Option 4, Install Application Database I - Create tablespace/user. You see the following message:

[echo] Creating tablespace...please wait

This option creates new Oracle Siebel eStatement Manager database tablespaces, users. Check the configure_ts.log and setup_user.log files for any errors.

g. Select Option 5, Install Application Database II - Create tables. You see the following message:

CreateObjects:

[echo] Creating tables/views...please wait

This option creates database tables, views and indexes. Check the create_tables.log and create_views.log files for errors. You can ignore the following error messages at the start of this log files. These indicate that the table, sequence, and index have been dropped:

ORA-00942: table or view does not exist

ORA-02289: sequence does not exist

ORA-01418: specified index does not exist

h. Select Option 6, Install Application Database III - Install PL/SQL Code Base.

CompileProc:

[echo] Compiling packages...please wait

This option compiles stored procedures to support database processing. Check the compile_sproc.log file for errors.

Configuring Oracle Siebel eStatement Manager for Oracle Database 11g ▪ Migrating an Existing Oracle Siebel eStatement Manager Database


Select Option 2, Initial Data Population, to bring this menu:

OtherOperationsMenu:

[echo] [1]. Import initial data set

[echo] [2]. Export eaSuite database data

[echo] [Q]. Quit

[input] Enter your selection (1, 2, q, Q)

i. Select Option 1, Import initial data set. This option populates the initial data.

j. Select option 2, Export eaSuite database data. This option takes a backup of an Oracle Siebel eaSuite database schema into L_BACKUP_FILE location that is specified in the edxadmin.properties file.

Migrating an Existing Oracle Siebel eStatement Manager Database To migrate an existing Oracle Siebel eStatement Manager database to a new version, run the database setup with Ant build scripts. For details of migration, see Migration Guide for Oracle Siebel eStatement Manager.

Configuring a New Oracle Siebel ePayment Manager Database To configure the new Oracle Siebel ePayment Manager database, you must do the following:

Edit the properties file that controls the Ant installation of the payment production database, payusr.properties.

Configure the new payment database using either the automated Ant target or using the Ant script and running each step manually.

Migrate the Oracle Siebel ePayment Manager database.

Configuring the Properties File You must configure the payusr.properties file for the Oracle Siebel ePayment Manager database.

To configure payusr.properties

Configuring Oracle Siebel eStatement Manager for Oracle Database 11g ▪ Configuring a New Oracle Siebel ePayment Manager Database


Edit the following lines in payusr.properties:

DB_SID=EDX0

DB_USERNAME=edx_dba

DB_PASSWORD=edxy1

where:

EDX0 is the Oracle Database 11g server instance ID.

edx_dba is the database username.

edxy1 is the database password.

Configuring the Oracle Siebel ePayment Manager Database Using the Automated Ant Target These instructions describe how to configure the new Oracle Siebel ePayment Manager database using the automated Ant target.

To configure the new Oracle Siebel ePayment Manager database using the automated Ant target

1 Switch to the DB admin user. (Oracle requires the administrative user for creating files.)

$ su – oracle

2 Change directory to your payment database home directory. For example:

cd PAYMENT_HOME/db/oracle

where:

PAYMENT_HOME is the directory where your Oracle Siebel ePayment Manager database is installed.

3 Run the install-new target to create a new Oracle Siebel ePayment Manager schema on an existing Oracle Siebel eStatement Manager database instance (DB_SID) as specified in the properties file:

ant install-new

4 Check the following log files for errors:

create_objects.log

compile_sproc.log

data_import.log



Configuring the Oracle Siebel ePayment Manager Database Manually Database Using the Ant Script These instructions describe how to manually configure the new Oracle Siebel ePayment Manager database using the automated Ant target.

To configure the new Oracle Siebel ePayment Manager database using the Ant script

1 Run the Ant script with the command:

ant

The main menu appears: main:

[echo] Install payment database

[echo] [1]. Install Application Database I

[echo] [2]. Install Application Database II

[echo] [3]. Initial Data Population

[echo] [Q]. Quit

[input] Enter your selection (1, 2, 3, q, Q)

2 Select Option 1, Install Application Database I. This option creates database tables, views, and indexes.

Create Objects:

[echo] Start drop_payment_objects.sql execution.

[echo] drop_payment_objects.sql execution is completed.

[echo] Start create_payment_objects.sql execution.

[echo] create_payment_objects.sql execution is completed.

3 Check the create_objects.log file for errors. You can ignore the following error messages at the start of this log file:

ORA-00942: table or view does not exist - drop table statement

ORA-02289: sequence does not exist - drop sequence statement

ORA-01418: specified index does not exist - drop index statement



4 Select Option 2, Install Application Database II. This option compiles stored procedures to support database processing.

Compile SP:

[echo] Compiling packages.

5 Check the compile_sproc.log file for errors.

6 Select Option 3, Initial Data Population.

This option allows the user to populate the initial payment module data.

Populate Data:

[echo] Start initial_payment_data.sql execution.

[echo] initial_payment_data.sql execution is completed.

7 Check the data_import.log file for errors.

Migrating the Oracle Siebel ePayment Manager Database This section provides instructions for migrating to the current version of the Oracle Siebel ePayment Manager database.

To migrate your Oracle Siebel ePayment Manager database

1 Back up your existing database before starting migration process.

2 Switch to the DB admin user. Oracle requires the administrative user for creating files.

$ su – oracle

3 Change directory to migration directory. For example:

cd PAYMENT_HOME/db/oracle/migration

where:




4 Edit the migrate.properties file for the following data, which controls the Oracle Siebel ePayment Manager production database migration:

DB_SID=EDX44

DB_USERNAME=edx_dba

DB_PASSWORD=edx

IS_DATA_MIGRATE=N

where:

EDX44 is the Oracle Database 11g server instance ID.

edx_dba is Oracle Siebel ePayment Manager database username.

edx is the Oracle Siebel ePayment Manager database password.

N indicates whether you want to migrate the recurring payment data (Y or N). (If you want to use the recurring payment multi-account feature, also set this property to Y.)

5 Change the directory to your Oracle Siebel ePayment Manager database home directory. For example:


where:


6 Use the Ant target to migrate. The install-migrate target is the payment database schema with the SIDs specified in the properties file. Run the following Ant command:

ant migrate

The following message appears:

get_backup_confirm: [echo] **Warning** [echo] We strongly advise a full backup of your existing [echo] database before applying the migration. [input] Do you have a backup (Y,y,N,n)

7 If a backup database is available, enter Y, else enter N.

The following menu appears:

continue:



[input] still continue with migration...(Y,y,N,n)

8 Select Y to continue the migration process.

The migration menu appears:

main:

[echo] Migration Main Menu

[echo] ------------------

[echo] [1]. Migrate from 4.3.0.0 Migrate to 4.7.0.0

[echo] [Q]. Quit

[input] Enter your selection (1,q,Q)

9 Select Option 1, Migrate from 4.3.0.0 Migrate to 4.7.0.0.

If you want to enable the multi-account feature for recurring payment later, you can use the separate Ant target provided for migrating the required data separately.

To enable multi-account feature for recurring payment

1 Change the directory to your Oracle Siebel ePayment Manager database home directory. For example:


where:


2 Check the migrate.properties file and verify that the SID, user name and passwords are correct.

3 Run the following Ant target:

ant migrate-recurring-pay-data


33

6Using the IBM WebSphere Console to Configure JMS Resources

This chapter assumes in-depth understanding of and practical experience with application server administration. Consult IBM WebSphere 6.1 documentation if necessary.

Accessing the IBM WebSphere Console Follow these instructions to navigate to the IBM WebSphere 6.1 console.

To navigate to the IBM WebSphere 6.1 console

Navigate to the IBM WebSphere 6.1 administration console in the Web browser by giving the proper URL in the following format:

http://[host]:[port]/ibm/console

Example: http://172.20.2.10:9060/ibm/console

TIP: The Administration port number is automatically assigned at installation time and might be different for your installation. If you enable security, you will be prompted for the user name and password that you entered at installation time.

Creating, Starting, and Stopping an IBM WebSphere Application Server Account Follow the instructions in this section to create, start, and stop an IBM WebSphere application server account.

To create an IBM WebSphere account

1 Navigate to WAS_HOME/bin/ProfileManagement/ directory and run pmt.sh file and provide your account details.

Example: /opt/IBM/WebSphere/AppServer/bin/ProfileManagement/pmt.sh

NOTE: If you are working from a remote environment, then set the DISPLAY variable before running the pmt.sh script. Do this in a GUI mode such as X Windows.

# DISPLAY=172.20.2.47.0.0

#export DISPLAY

Using the IBM WebSphere Console to Configure JMS Resources ▪ Setting Classpath and Environment Variables for IBM WebSphere


To start an IBM WebSphere account

1 Navigate to WAS_HOME/profiles/YOUR_ACCOUNT/bin directory and run startServer.sh file with necessary arguments.

Example: /opt/IBM/WebSphere/AppServer/profiles/AppSrv02/bin

2 Run this command at the terminal:

./startServer.sh server1

To stop an IBM WebSphere account

1 Navigate to WAS_HOME/profiles/YOUR_ACCOUNT/bin directory and run stopServer.sh file with the appropriate parameters.

Example: /opt/IBM/WebSphere/AppServer/profiles/AppSrv02/bin

2 Run this command at terminal:

./stopServer.sh server1 -username Account User Name -password Account Password

where:

Account User Name is your account user name.

Account Password is your account password.

Setting Classpath and Environment Variables for IBM WebSphere This section describes how to set the classpath and environment variables for IBM WebSphere.

To set the total transaction lifetime timeout property

1 Navigate to Servers > Application Servers > Server1 > Runtime (tab) > Transaction Service.

2 Set the total transaction lifetime timeout property to 1200.

3 On the Custom Properties page, click New. Type ACCEPT_HEURISTIC_HAZARD in the Name field and type TRUE in the Value field. Click Apply or OK. Click Save to save your changes to the master configuration.

Using the IBM WebSphere Console to Configure JMS Resources ▪ Setting Classpath and Environment Variables for IBM WebSphere


To set the IBM WebSphere variables

1 Navigate to Environment > WebSphere Variables.

2 Set the variable values as indicated in the following table:

IBM WebSphere Variable Name

Value Example

ORACLE_JDBC_DRIVER_PATH Path to the JDBC Driver Installed Directory

/opt/oracle/OraHome_3/jdbc/lib

JAVA_HOME Path to the Java Home Directory

/opt/IBM/WebSphere/AppServer/java

To set Java Virtual Machine settings

1 Navigate to Servers > Application servers > server1.

2 Select Server Infrastructure > Java and Process Management->Process Definition->Java Virtual Machine.

3 Add the following required .jar files and directories to the classpath:

EDX_HOME/lib/ext/edx_system.jar

EDX_HOME/config/

PAYMENT_HOME/jsse.jar

PAYMENT_HOME/jcert.jar

PAYMENT_HOME/jnet.jar

CAUTION: Make sure these files exist in the EDX_HOME/lib directory (where EDX_HOME is your eStatement installation directory), otherwise the configuration will not work properly.

4 Under Custom Properties, add the following name-value pairs as Custom Properties:

Name Value Example

com.edocs.tasks.loader.alias Database Alias Name edx

com.edocs.tasks.loader.password Database Password edx

com.edocs.tasks.loader.user Database User Name edx

java.protocol.handler.pkgs Correct JNDI Name com.edocs.protocol

edx.home eStatement Installed Directory Path

/opt/EDCSbd

Using the IBM WebSphere Console to Configure JMS Resources ▪ Configuring eXtended Middleware Architecture


Configuring eXtended Middleware Architecture You must configure eXtended Middleware Architecture for the notification, Hibernate properties, and the logger.

Configuring eXtended Middleware Architecture for Notification You must follow these steps to configure eXtended Middleware Architecture for the notification feature.

To configure eXtended Middleware Architecture for notification

1 Change the notification-consumer-cfg.xma.xml file, which is located in %EDX_HOME%/xma/config/com/edocs/common/notification/ for proper mail server configuration.

2 Set property smtpHost corresponding to your mail server IP under the following tag:

<bean id="config"> </bean>

Example:

<property

name="smtpHost"><value>172.20.2.34</value></property>

Configuring Hibernate Properties You must follow these steps to configure Hibernate properties.

To configure Hibernate properties

Change the persistence.xma.xml file located in %EDX_HOME%/xma/config/modules/ to set the correct hibernate.dialect key in the <bean id="defaultHibernateProps"></bean> tag for your database type.

Example for Oracle Database 11g:

<prop

key="hibernate.dialect">org.hibernate.dialect.Oracle9Dialect</

prop>



Configuring the Logger The log4j_cc.xml file is located in the %EDX_HOME%/config folder. The default appender for the logger is JMS. (In Apache log4j, an output destination is called an appender.)

This logs the logger data in the database. You can alternately use the File appender and the Console appender. It is not recommended to use the JMS appender when it comes to enabling DEBUG priority, since it will lead to flood the database with lots of data.

Changes to the log4j_cc.xml configuration are picked up dynamically. You do not need to restart the application server or the scheduler.

File Appender Three file appenders are specified in the log4j_cc.xml, namely FILE_ESTATEMENT, FILE_SCHEDULER, and FILE_Thirdparty:

FILE_ESTATEMENT:

<appender name="FILE_ESTATEMENT"

class="org.apache.log4j.RollingFileAppender">

<param name="File" value="log4j_eStatement.log"/>

FILE_SCHEDULER (used for PWC scheduler code):

<appender name="FILE_SCHEDULER"


<param name="File" value="log4j_Scheduler.log"/>

FILE_Thirdparty (used to redirect third party library logs):

<appender name="FILE_ Thirdparty"


<param name="File" value="log4j_Thirdparty.log"/>

The above log files are created in the domain folder of the application server. Additionally, if these files do not need to be created under the domain folder, then you can specify the fully-qualified path.

JMS Appender The JMS appender is used to log the data to the database. It is recommended that you set the Threshold value for the JMS appender as INFO so that it limits only INFO, ERROR, and WARN messages to be logged to the database. Enabling the Threshold for DEBUG floods the database and cause performance issues.



To set the threshold for the JMS appender

Edit the appender values as shown:

<appender name="JMS"

class="com.edocs.fs.logging.appenders.JMSQueueAppender">

<param name="QueueConnectionFactoryBindingName" value="edx/lcf"/>

<param name="QueueBindingName" value="edx/queue/logger"/>

<param name="Threshold" value="INFO"/>

<layout class="org.apache.log4j.PatternLayout">

<param name="ConversionPattern" value="%c %x - %m"/>

</layout>

</appender>

Setting the Categories for Log Information You can get the logging information for specified different package levels and different appender types.

To set categories for logging

Set parameters in tag <category></ category> according to your requirement.

<category name="Package_Name" additivity="false">

<priority value="Priority_Level"/>

<appender-ref ref="Appender_name"/>

</category>

Example:

<category name="com.edocs.pwc.scheduler" additivity="false">

<priority value=" INFO "/>

<appender-ref ref="FILE_SCHEDULER"/>

<appender-ref ref="CONSOLE"/>

<appender-ref ref="JMS"/>

</category>

NOTE: Set the Additivity property to false to avoid replication of data.

Generally, the priority level is set to INFO to avoid the overhead consumed by the application server.

Using the IBM WebSphere Console to Configure JMS Resources ▪ Configuring Java Resources


The logging information not related to the defined package level is placed at the <root></root> appender. The FILE_Thirdparty appender is specified under this so that any errors in third party libraries can be routed to this file.

Specifying Log4j Properties You must specify properties for the log4j files.

To specify Log4j properties

Specify an available path for log4j.appender.logfile.File (For example, log4j.appender.logfile.File=$EDX_HOME/logs/xma.log) in log4j.properties under EDX_HOME/xma/config/modules/xma, otherwise while starting server1 to log in console, you will see the following message:

[11/11/08 19:03:23:966 MST] 0000005b SystemErr R log4j:WARN No appenders

could be found for logger org.apache.struts.action.ActionServlet).

[11/11/08 19:03:23:968 MST] 0000005b SystemErr R log4j:WARN Please

initialize the log4j system properly.

Configuring Java Resources This guide assumes in-depth understanding of and practical experience with application server administration. It is designed for experienced IBM WebSphere administrators and primarily presents only the steps and settings specific to Oracle Siebel eStatement Manager.

See IBM WebSphere documentation for detailed step-by-step instructions on Java resource configuration, performance, and tuning. Consult your application server administrator for settings that may be specific to your configuration.

Configuring the Data Source Start your IBM WebSphere Server instance and bring up the Administrative Console before you begin this chapter.

Data providers and Data Source Configuration procedure are described in Chapter 8 under Configuring Java Resources.

Configuring the JMS Resources Because this example uses IBM WebSphere 6.1 default messaging, this configuration is significantly different from the configuration required for IBM WebSphere application Server Version 6.0. This section describes how to create Bus, Bus member, Bus Destination, and Activation Specifications.



Configuring the Bus

1 Expand Service Integration in the left panel of the administrative console, and click Buses.

2 Under Buses, click New.

3 Enter the name for your new bus, and click Next.

4 In the Confirm Creation of New Bus window, Click Finish to complete bus creation.

Configuring Bus Members

1 Click the Created Bus to cause the configuration window to appear.

2 Click Bus Members under Topology.

3 On the Add a new bus member page, leave the default as Server and click Next.

4 Select the type of message store, for example, File Store, and click Next.

5 In the next window, leave default values for message store properties and click Next.

6 On the confirmation page, click Finish.

Configuring Bus Destinations

1 Click the created Bus then configuration window will appear. From there click Destinations under Destination resources.

2 There are some destinations already defined. Click New to create a new JMS destination.

3 Select the destination type as Queue and click Next.

4 Enter Identifier name (Ex: edocsQueue) for the Identifier and click Next.

5 On the confirmation page, click Finish.

6 Click the Save link at the top of the administrative console. You will see a window prompting you to save to the master configuration.

7 Click the Save button on this page to save the settings to disk.



Configuring the JMS Activation Specification

1 Create JMS Activation Specification with a suitable name and a JNDI name when necessary. Make sure to add the correct destination JNDI name at each time when you create an activation specification.

2 Click Default messaging provider to return to the provider page.

3 Under Additional Properties, click Activation Specification.

4 Click New to create a new activation specification.

5 Enter Name and the JNDI name.

6 Make sure that the Destination type is set to the correct type, and enter the correct Destination JNDI name.

7 For the Bus name, select created bus name and click OK.

8 Click the Save link at the top of the administrative console.

You will see a window prompting you to save to the master configuration.

9 Click Save to save the settings to disk.


43

7Configuring IBM WebSphere A pplication Server for UNIX

This chapter assumes in-depth understanding of and practical experience with WebSphere Enterprise Server. Consult your WebSphere documentation as necessary.

It is recommended that you install and configure Oracle Siebel eStatement Manager in the same top-level directory structure, first on the database server, then the application server.

If you have not already installed database server components and configured the database server for Oracle Siebel eStatement Manager, do so now.

TIP: For distributed environments, ensure that you have any required database client software installed on your application server and any other client computers of your database server.

CAUTION: The installation and configuration examples in this guide use default Oracle Siebel eStatement Manager pathnames, privileges, and permissions. If you choose not to accept the default values, make sure your values are consistent on all servers in your installation of Oracle Siebel eStatement Manager.

UNIX Permissions for IBM WebSphere Application Server Application servers running Oracle Siebel eStatement Manager will not function correctly without access to Oracle Siebel eStatement Manager configuration files, storage directories, and related resources. When installing Oracle Siebel eStatement Manager on IBM WebSphere Server, you were asked to specify the owner and group permissions (userid:groupid) of the application server. If you made a mistake during installation, you must change the owner and group permissions for the directory, including all subfolders, to the application server owner.

This guide uses the example username and password edxadmin:edxadmin as the application server owner and group for the Oracle Siebel eStatement Manager.

Default Example Custom

Specified during installation. edxadmin:edxadmin

For details on owner and group permissions for IBM WebSphere, please consult the documentation for your platform.

If your application server administrator uses custom user and group permissions, you can reset these permissions with the chown command.

To reset user and group permissions

1 Switch user to the default owner of your application server home directory.

Configuring IBM WebSphere Application Server for UNIX ▪ Starting and Stopping IBM WebSphere


2 Recursively change the user and group permissions of the application server installation directory and all subdirectories to the application server owner.

chown –R edxadmin:edxadmin /opt/WebSphere

3 Switch user to your application server owner and configure your application server with your new owner.

TIP: Verify the owner information in any profile files that are used by the database server owner and application server owner. See your server documentation for details.

Starting and Stopping IBM WebSphere Developers and system administrators must be familiar with how to stop and start the IBM WebSphere server and any active Web applications for your platform.

For details on starting and stopping your IBM WebSphere server and for verifying startup, consult the server documentation for your platform.

Starting and Stopping an Active Application Server Improperly starting or stopping an application server in an active Oracle Siebel eStatement Manager production environment can produce unexpected and unintended results. You can create custom startup and shutdown scripts that include all your command parameters, as well as the command used to start or stop the Scheduler.

CAUTION: The default command-line startup shell scripts are fine for an inactive production environment where there are no running jobs.

UNIX Environment Variables for IBM WebSphere Oracle Siebel eStatement Manager installs several configuration files that you use to define your environment.

edx_config: This shell script, $EDX_HOME/bin/edx_config, prompts you to specify environment variables for your application server.

edx_env: This configuration file, $EDX_HOME/config/edx_env, stores the environment variables you specify in edx_config, to pass at application server startup.

edx.config: This script file, $EDX_HOME/config/edx.config, passes the environment data in edx_env to your application server through your startup script.

Configuring IBM WebSphere Application Server for UNIX ▪ UNIX Environment Variables for IBM WebSphere


Setting UNIX Environment Data with edx_config The shell script, edx_config, prompts you to enter values for your Java and database installation, including absolute directory pathnames or user identification information.

NOTE: Run this script any time that you need to modify your Oracle Siebel eStatement Manager environment. Do not modify edx_env directly.

If you have not already done so, verify that the ownership of the $EDX_HOME directory is set to the user and group of the application server owner. If not, change it before running edx_config.

CAUTION: Be sure the time zone (TZ) for your server is set to your system time zone; Oracle Siebel eStatement Manager jobs can fail if Java system time does not match actual system time.

To set environment data with edx_config

1 Switch user to the application server owner, in this example edxadmin.

su - edxadmin

2 Navigate to the bin directory for Oracle Siebel eStatement Manager on your application server, for example

cd $EDX_HOME/bin

3 Run the following script:

./edx_config

4 Enter values as prompted by the script for your database home, database username and password, application server, Java home, and application server profile location.

CAUTION: Make sure that the database values you enter in this session are the same values specified during database configuration. Consult your DBA for any custom settings specific to your platform.

Passing eStatement Environment Data to IBM WebSphere To pass your Oracle Siebel eStatement Manager environment to your application server, you must edit your application server startup script to the following:

Set values for your Oracle Siebel eStatement Manager home, application server home, and Java home directories.

Call and process the configuration script edx.config. This procedure is called sourcing your configuration.

CAUTION: The code examples in the following section are for IBM WebSphere on IBM AIX. Use these procedures with the environment variables for your application server and platform.

To pass your Oracle Siebel eStatement Manager environment to IBM WebSphere

1 Switch user to your application server owner, for example edxadmin.

Configuring IBM WebSphere Application Server for UNIX ▪ UNIX Environment Variables for IBM WebSphere


su - edxadmin

2 Stop your application server. For example:

cd $WAS_HOME/profiles/<profilename>/bin

./stopServer.sh server1

3 Keep a backup copy of the server startup script for your profile. For example:


cp startServer.sh startServer.bak

4 Change directory to the location of your application server startup script and open the file for editing. For example:


vi startServer.sh

CAUTION: Do not modify the main startup script of the IBM WebSphere server located in $WAS_HOME/bin directory. Modify the file in your current profile where Oracle Siebel eStatement Manager is going to be installed.

5 Declare and initialize the variable $EDX_HOME near the beginning of the file with other variable declarations. For example:

#!/bin/sh

WAS_USER_SCRIPT=/opt/IBM/WebSphere/AppServer/profiles/AppSrv02/bin/setupCmdLine

.sh

export WAS_USER_SCRIPT

EDX_HOME=/opt/eaSuite/eStatement

export EDX_HOME

WAS_HOME=/opt/IBM/WebSphere/AppServer

export WAS_HOME

6 In the same file, source edx.config just before the command to start the JVM. The dot and space preceding the pathname are a required part of the syntax. For example:

. $EDX_HOME/config/edx.config

For example:

#!/bin/sh

WAS_USER_SCRIPT=/opt/IBM/WebSphere/AppServer/profiles/AppSrv02/bin/setupCmdLine

.sh

export WAS_USER_SCRIPT

EDX_HOME= /opt/eaSuite/eStatement

Configuring IBM WebSphere Application Server for UNIX ▪ Capturing Your UNIX Environment for Oracle Siebel ePayment Manager


export EDX_HOME

WAS_HOME=/opt/IBM/WebSphere/AppServer

export WAS_HOME

. $EDX_HOME/config/edx.config

/opt/IBM/WebSphere/AppServer/bin/startServer.sh "$@"

7 Save and close the startServer.sh file.

8 Add a file called commons-logging.properties into $WAS_HOME/profiles/$profile/properties. The content of file is:

org.apache.commons.logging.LogFactory=org.apache.commons.logging.impl.LogFactoryImpl

NOTE: You must add the commons-logging.properties file into IBM WebSphere 6.1, or you cannot view the log in command center page.

9 When you have finished the steps to pass your Oracle Siebel eStatement Manager environment to IBM WebSphere, re-start the server. For example:

./startServer.sh server1

Capturing Your UNIX Environment for Oracle Siebel ePayment Manager To capture your UNIX environment for Oracle Siebel ePayment Manager, you must

Update the Oracle Siebel ePayment Manager and Oracle Siebel eStatement Manager configuration files.

Update the Oracle Siebel eStatement Manager EAR file.

Deploy the Oracle Siebel ePayment Manager EAR file.

To update the Oracle Siebel ePayment Manager and Oracle Siebel eStatement Manager configuration files

1 Log on as the IBM WebSphere server owner and change your working directory to PAYMENT_HOME/config

where:

PAYMENT_HOME is the location where Oracle Siebel ePayment Manager configuration files are installed, such as /opt/eaSuite/ePayment/config.

Configuring IBM WebSphere Application Server for UNIX ▪ Capturing Your UNIX Environment for Oracle Siebel ePayment Manager


2 If you are not using the default Oracle Siebel eStatement Manager and Oracle Siebel ePayment Manager directories, edit the edx_payment.config file and correct the entry that defines PAYMENT_HOME.

3 Copy the updated edx_payment.config file to $EDX_HOME/config.

You must update the ear-eStatement.ear file for Oracle Siebel ePayment Manager. Oracle Siebel ePayment Manager installs a file called ear-payment.ear, which you must merge into ear-eStatement.ear.

To update the eStatement EAR file

1 Back up the original ear-eStatement.ear file.

2 Edit PAYMENT_HOME/bin/websphere/merge_payment_ws.sh to update the locations for the home and source directories, if needed. Also set JAVA_HOME in the script or in your shell.

3 Run the edited shell script.

The batch file creates a new ear-eStatement.ear file in the PAYMENT_HOME/J2EEApps/websphere directory.

To deploy the Oracle Siebel ePayment Manager EAR files

1 Redeploy eStatement.ear since it was updated.

2 Deploy a sample payment application. You can deploy either the Simple (single-DDN) or Complex (multiple-DDN) application for testing purposes.

3 Deploy your custom Oracle Siebel ePayment Manager application EAR file.


49

This chapter assumes in-depth understanding of and practical experience with application server administration. It is designed for experienced IBM WebSphere administrators and primarily presents only the steps and settings specific to Oracle Siebel eStatement Manager.

8Configuring Java Resources for WebSphere for UNIX

See IBM WebSphere Server documentation for detailed step-by-step instructions on Java resource configuration, performance, and tuning. You must also consult your application server administrator for settings that may be specific to your configuration.

You must start IBM WebSphere Server and bring up the Administrative Console before you begin this chapter.

NOTE: If you cannot bring up the IBM WebSphere Console/Client, you cannot proceed with configuring the application server for Oracle Siebel eStatement Manager.

Setting Total Transaction Lifetime Timeout Transaction lifetime timeout is a configurable parameter that you must set according to environmental conditions such as number of users, access method, and load. Customize the value accordingly. A good starting value for the JTA option is 60 seconds. Set total transaction lifetime timeout to 1200.

To set transaction lifetime timeout

1 Log in to the console.

2 Navigate to Application servers > server1 > Runtime->Transaction Service.

3 Set Total Transaction lifetime timeout to 1200.

4 Set Maximum transaction timeout to 1200.

Configuring Java Database Connectivity for Oracle Siebel eStatement Manager After you have successfully configured the Oracle Siebel eStatement Manager database, you must configure Java Database Connectivity (JDBC) resources on the application server where you installed Oracle Siebel eStatement Manager application server. JDBC Connections on the application server support data retrieval from relational databases and other data sources.

Configuring Java Resources for WebSphere for UNIX ▪ Configuring Java Database Connectivity for Oracle Siebel eStatement Manager


About JDBC Connections for Oracle Siebel eStatement Manager JDBC connection pools contain named groups of JDBC Connections that are created when the connection pool is registered, usually when starting up your application server. Your application server opens JDBC Connections to the database during startup and adds these connections to the pool. A J2EE Web application borrows a connection from the pool, uses it, and then returns it to the pool by closing it.

JDBC transaction data sources enable JDBC clients to obtain a connection to a Database Management System (DBMS). Each data source points to the value specified for the Name attribute when a JDBC connection pool was configured.

TIP: The edxAdmin connection pools support concurrency for scheduling multiple jobs. Tuning edxAdmin connection capacity and threads can improve Oracle Siebel eStatement Manager email performance.

This chapter provides steps to create and configure JDBC Connections. See your application server documentation for details and more information.

CAUTION: Make sure you are using the correct properties for your application server and database combination.

Configuring JDBC Connections for IBM WebSphere CAUTION: Make sure you set all paths to the appropriate point releases/patches for your application server and JDK, if necessary. Check the Release Notes and your system documentation for updated requirements.

IBM WebSphere Environment Variables

Variable Description IBM AIX

WAS_HOME Application server home /opt/WebSphere/AppServer

APP_OWNER Application server owner edxadmin

APP_GROUP Application server group edxadmin

APP_PORT Application server port 9080

ADMIN_PORT Application server admin port 9060

JAVA_HOME Java home directory $WAS_HOME/java

JMS_HOME MQSeries java client directory /opt/mqm/java

Creating a JDBC Provider Complete these tasks to create a JDBC provider.



To create a JDBC Provider

1 Navigate to Resources > JDBC > JDBC providers.

2 Go to Resources > JDBC > JDBC providers and select the scope from the list.

3 Click New, choose Oracle as the database type, and select Oracle JDBC Driver from the Provider type list.

4 Select Connection pool data source for the implementation type, and click Next.

5 Select Oracle for the database type, Oracle JDBC Driver for the provider type, and Connection pool data source for the implementation type.

6 Click next.

7 Enter a value for Directory Location for the ojdbc14.jar file and click Next.

Example: /opt/oracle/OraHome_3/jdbc/lib

8 On the Summary page, click Finish to complete the JDBC provider configuration.

Establishing Database Connectivity for Oracle Siebel eStatement Manager Create five data sources for user interface application using the following table and the procedure described below.

Data Source Name JNDI Name

edxAdminDataSource edx.databasePool

edxUserDataSource edx.user.databasePool

edxLoggerDataSource edx.logger.databasePool

edxXMADataSource edx/xma/databasePool

edxMessageDataSource edx.messaging.databasePool

To establish data sources

1 Navigate to Resources > JDBC > Data Sources.

CAUTION: Do not click Data Sources (Version 4). They do not support the new EJB specification 2.x.

2 Select the appropriate scope (the same one you selected when creating the JDBC Provider) and click New.

3 Provide a data source name and the corresponding JNDI name and click Next.



4 Choose the Select an existing JDBC provider option to select the JDBC provider that you created earlier and click Next.

5 Enter database-specific properties for the data source such as URL and data store helper class name and click Next.

Property Value Example

URL jdbc:oracle:thin:@<DB_Server>:<Port_Number>:<DB_Alias_Name>

jdbc:oracle:thin:@172.20.2.52:1521:EDX44

Data store helper class name

Select the correct helper class name for the Oracle Database 11g data store.

Oracle11g

6 In the summary page, click Finish to complete data source configuration.

You see the created Data sources.

9 Click each data source and select Custom properties Under Additional Properties. Add two custom properties as user and password.

Property Value

Name user

Value (Oracle Database 11g User Name)

Name password

Value (Oracle Database 11g Password)

10 Click OK.

Configuring Java Resources for WebSphere for UNIX ▪ Configuring JMS Resources for Oracle Siebel eStatement Manager


Testing Data Sources After you have configured data Sources correctly, you can test them in the Administrative Console.

To test the data sources

Select the data sources you created and click Test Connection.

Configuring JMS Resources for Oracle Siebel eStatement Manager Configure JMS resources for event handlers and loggers as described in this section.

Creating Bus and Destination Event Handlers To create bus and destination event handlers

1 Create new Bus without enabling security for the bus, for example edocsServiceBus.

2 Add Bus member and Create Bus Destination as Queue.

3 Give Name for Identifier, for example, edocsQueue, and click Next.

4 Select Scope (the same one you selected when creating the JDBC Provider) and click Next.

5 In the Confirm Queue Creation window, click Finish and Save to save your changes to the Master Configuration.

Creating Connection Factories Create the two connection factories shown in following table. Connection Factory JNDI Name

EventsConnectionFactory edx.qcf

EventsforeignConnectionFactory edx.foreign.qcf

To create connection factories

1 Select scope as the node.



2 Navigate to Resources > JMS > JMS providers > Default Messaging provider > Queue connection factories.

3 Click New.

4 Enter a connection factory name (EventsConnectionFactory) and its JNDI name (edx.qef) under the Administration region.

5 Select a bus name, such as edocsServiceBus.

6 Select the correct provider endpoints under the Connection region:

YOUR APPLICATION SERVER IP:SIB_ENDPOINT_ADDRESS

You can find the SIB_ENDPOINT_ADDRESS number in Servers > Application servers >

server1 > Ports.

Example: 172.20.2.10:7277

6 Click Apply and Save to save your configurations.

7 Follow the same steps to create other connection factories and provide appropriate values.

Creating Queues Create the two queues shown in the following table.

Queue Name JNDI Name

EventsQueue edx.queue.outbound

EventsforeignQueue edx.foreign.queue.outbound

To create the event handler queues

1 Navigate to Go to Resources > JMS > JMS providers > Default Messaging > Queues.

2 Click New.

3 Enter a queue name (EventsQueue) and a corresponding JNDI name (edx.queue.outbound).

4 In the Connection region, select your bus name and queue name that you added under Bus Destination.

5 Click Ok and Save to save your configurations.

6 Follow the same steps to create other queues and provide appropriate values.



Creating Queue Activation Specifications You must create two activation specifications, shown in the table below, for the created two queues with suitable names and the JNDI names.

Queue Activation Name JNDI Name Destination JNDI Name

EventsQueueActivation jms/MessageDispatcher edx.queue.outbound

EventsforeignQueueActivation jms/ForeignMessageDispatcher edx.foreign.queue.outbound

To create queue activation specifications

1 Navigate to Resources > JMS > JMS providers > Default Messaging > Activation Specifications.

2 Click New.

3 Enter the proper queue activation name (EventsQueueActivation) and corresponding JNDI name (jms/MessageDispatcher).

4 In the Destination region, select Queue as the destination type, and enter values for Destination JNDI name (edx.queue.outbound) and Bus name (edocsServiceBus).

5 Click Ok and Save to save your configurations.

6 Follow the same steps to create other queue activation specifications and provide appropriate values.

Creating Logger Modules

To create logger modules

1 Go to Service integration > Buses.

2 Create a new bus without enabling the security for the bus. An example name is edocsLogBus.

3 Click the created bus, and add a bus member.

4 Navigate to Buses > Your Created Bus > Destinations.

5 Create new queue. An example name is LogQueue.

6 Go to Resources > JMS >JMS providers > Default messaging provider > Queue connection factories.

7 Click New.



8 Create a connection factory with the values specified in the following table and save your configurations.

Property Value

Name LoggerConnectionFactory

JNDI name edx/lcf

Bus name <Created_Bus_Name>

Provider endpoints <Your_Application_Serever_IP>:<SIB_ENDPOINT_ADDRESS>

9 Navigate to Resources > JMS > JMS providers > Default messaging providers > Queues.

10 Click New.

11 Create a queue with the values specified in the following table and save your configurations.

Property Value

Name LoggerQueue

JNDI name edx/queue/logger


Queue name <Created_Queue_Name>

12 Navigate to Resources > JMS > JMS providers > Default messaging provider > Activation specifications.

13 Click New.

14 Create activation specifications with suitable values for Name and JNDI name with other values given in following table. In the table, <Created_Bus_Name> is the name of the bus you created, and <Created_Queue_Name> is name of the queue you created. Save your configurations.

Property Value

Name Your_Logger_Activation_Name

JNDI name Your_Logger_Activation_JNDI

Destination type Queue

Destination JNDI name edx/queue/logger


Configuring Java Resources for WebSphere for UNIX ▪ Creating J2C Authentication Aliases


Example of Activation Specifications

Property Value

Name LoggerActivation

JNDI name jms/Logger

Destination type Queue


Bus name edocsLogBus

Creating J2C Authentication Aliases This section describes how to create J2C authentication aliases for the EJB Logger and Event modules.

To create J2C authentication aliases for EJB Logger and Event modules

1 Navigate to Security > Secure administration, application, and infrastructure > Authentication > Java Authentication and Authorization Services > J2C authentication data > New.

2 Create two authentication aliases, Logger_ASAuthAlias and MessageDispatcher_ASAuthAlias, as given in the following table. Do so in the General Properties region within the Configuration tab by assigning values to the three indicated properties.

Property Value

Alias Alias

User ID Your Profile Login User ID

Password Your Profile Login Password

Deploying the Oracle Siebel eStatement Manager Application After your application server is configured successfully, you can proceed to deploy the Oracle Siebel eStatement Manager J2EE applications that power Oracle Siebel eStatement Manager.

To deploy the Oracle Siebel eStatement Manager Web application with IBM WebSphere

1 Navigate to Applications > Install New Application.

Configuring Java Resources for WebSphere for UNIX ▪ Deploying the Oracle Siebel eStatement Manager Application


2 If the application is on your local computer, select Local file system. Otherwise select Remote file system.

3 To apply the properties for message driven bean listener bindings during deployment, select Show me all installation options and parameters.

4 Click Next.

5 Accept default settings up to the Bind listeners for message-driven beans window.

6 At the Bind listeners for message-driven beans window, provide correct Activation Specifications for Logger and MessageDispatcher EJB’s as Binders, as follows:

Activation Specifications for the Logger

Property Value

Activation Specification JNDI Name Your_Logger_Activation_JNDI


Activation Specification alias Node Name/ Logger_Alias

Example of Logger Activation Specifications

Property Value

Activation Specification JNDI Name jms/Logger


Activation Specification alias hesitaNode05/Logger_ASAuthAlias

Activation Specifications for MessageDispatcher

Property Value

Activation Specification JNDI Name Your_MessageDispatcher_Activation_JNDI

Destination JNDI name edx.queue.outbound

Activation Specification alias Node Name/Events_Alias

Example of Activation Specifications for MessageDispatcher

Property Value

Activation Specification JNDI Name jms/MessageDispatcher

Destination JNDI name edx.queue.outbound

Activation Specification alias hesitaNode05/MessageDispatcher_ASAuthAlias

Configuring Java Resources for WebSphere for UNIX ▪ Deploying the Oracle Siebel eStatement Manager Application


NOTE: To set Message Driven Bean Listener Bindings Properties after deployment, select Prompt me only when additional information is required. When you finish the deployment, click on the deployed application and select Message Driven Bean listener bindings under Enterprise Java Bean Properties.

7 Accept default setting for other windows, and at the end save your deployment setting to the master configuration.

The Enterprise Applications window appears.

8 Select the application to be deployed, in this case eStatement, and click Start.

9 Click on the deployed application, click Last participant support extension under Detail Properties, and check Accept heuristic hazard to accept a two-phase transaction that contains a one-phase resource.

10 If you need to use the Oracle Siebel ePayment Manager and report functions, you must deploy the paymentComplex, Sample, and reportSample applications.

Resolving Deployment Issues While deploying an application, you may encounter an error such as the following:

[EJBDeploy] The compiler has run out of memory. Consider using the "-J-mx<number>" command line option to increase the maximum heap size.

An error occurred from the EJBDeploy program: An unexpected exception was thrown. Halting execution. [severity 2]

[EJBDeploy] Error executing deployment: java.lang.OutOfMemoryError. Error is PermGen space.

To correct an error

1 Navigate to WAS_HOME/deploytool/itp/.

2 In the ejbdeploye.sh file, edit the PermSize parameter under the Platform region.

3 Increase the maximum heap size under the $JAVA_CMD region.

Configuring Java Resources for WebSphere for UNIX ▪ Running Oracle Siebel eStatement Manager


Running Oracle Siebel eStatement Manager Follow these instructions to run Oracle Siebel eStatement Manager, Oracle Siebel ePayment Manager, the Sample application, and the Reporting applications.

To run Oracle Siebel eStatement Manager

In a browser type the URL in following format:

http://WS_APP_SVR_IP:PORT_NUMBER/eBilling

where:

WS_APP_SVR_IP is your IBM WebSphere Application Server IP address.

PORT_NUMBER is the WC_defaulthost port number in your server.

Example:

http://172.20.2.58:9082/eBilling/

To run the paymentComplex application

In a browser, type the URL in following format:

http://WS_APP_SVR_IP:PORT_NUMBER/paymentComplex

where:


To run the sample application In a browser, type the URL in following format:

http://WS_APP_SVR_IP:PORT_NUMBER/Sample

where:


To run ReportSample application In a browser, type the URL in following format:

http://WS_APP_SVR_IP:PORT_NUMBER/reportSample

where:

Configuring Java Resources for WebSphere for UNIX ▪ Running Scheduler



Running Scheduler Scheduler enables you to schedule and run jobs in Oracle Siebel eStatement Manager Command Center. If you attempt to run a new job with the Scheduler not running, the job does not run and you see the status is Not yet started.

You do not need to start Scheduler until after you have deployed the EAR file.

To start the Scheduler from the UNIX command line

1 Switch user to the application server owner.

su - edxadmin

2 Change to the bin directory of your Oracle Siebel eStatement Manager installation, $EDX_HOME/bin.

3 Append the properties folder to the end of the classpath in the ws_scheduler file as shown in this example:

CLASSPATH=$CLASSPATH:/vol1/IBM/WebSphere/AppServer/profiles/AppSrv03/properties

4 Run the Scheduler command for your application server, host, and port:

./ws_scheduler -start -url iiop://Computer Name:Port Number

where:

Computer Name is the name of the host computer.

Port Number is the bootstrap port number.

For example:

./ws_scheduler -start -url iiop://64.181.226.17:2809

You can find the JNDI port for your server by opening the IBM WebSphere Administrative Console and navigating though the pages Application Servers > server_name > Configuration tab > Communications > port > BOOTSTRAP_ADDRESS.

TIP: You typically use the default port for the administration server. You can specify another port number if necessary, but it must match the port for the administration server.

5 You can stop the Scheduler by replacing the -start parameter with the -stop parameter.

The com.edocs.pwc.cli.CLIScheduler application is a command line interface for use with Scheduler. For details about this application, see SDK Guide for Oracle Siebel eStatement Manager.

Configuring Java Resources for WebSphere for UNIX ▪ Running Scheduler



63

9 Running Oracle Siebel eStatement Manager

This chapter explains the configuration steps required to run the application client for Oracle Siebel eStatement Manager with default security settings (in a security-enabled environment). To proceed, you must have already created an IBM WebSphere account with security enabled.

NOTE: If you want to use the default IBM WebSphere profile or enable security, then you must configure a user repository. See Appendix A for more information.

Setting the Security Level Complete the following task.

To set the security level

1 Navigate to Security > Secure administration, application, and infrastructure.

2 Select Enable administrative security only.

3 Under User account repository, select Federated repositories as Available realm definition.

4 Under custom properties, add the following value-pair properties:

Name: com.ibm.websphere.security.registry.propagateExceptionsToClient

Value: true

5 Accept default SSL certification and key management settings.

6 The Bus Security is used in disabled mode. For each bus the option, Allow the use of all defined transport channel chain is enabled under the Permitted transports region. This comes under the security section of each bus.

Configuring the sas.client.props File This section describes how to configure the sas.client.props file.

To configure the sas.client.props file

1 Configure the sas.client.props file, which is located in <Your Profile>/properties/, with the following information:

Running Oracle Siebel eStatement Manager ▪ Configuring the sas.client.props File


com.ibm.CORBA.securityServerHost=<Application SVR IP>

com.ibm.CORBA.securityServerPort=<bootstrap port>

com.ibm.CORBA.loginSource=properties

com.ibm.CORBA.loginUserid=<Your Profile User ID>

com.ibm.CORBA.loginPassword=<Your Profile Password>

2 Because this configuration uses defaults that the application server provides for keyStore and trustStore, change the default passwords for keyStore and trustStore.

3 The above configuration settings are also the same for Local operating system, User account registry. In this case, select Local operating system instead of Federated repositories as the Available Realm definition.

4 Click Configure to add Primary administrative user name, User ID, and Password.

5 Change the sas.client.props file accordingly so that it has the correct user ID and password.

6 Click Apply and Set as current.


65

This chapter describes how to package the Hibernate and C3PO third-party libraries.

kaging the Hibernate

u mu er for either of the following applications before

l

nt Manager (includes Oracle Siebel ePayment Manager). See Chapters ebel

st (For details on installing eaAssist, see The SDK and Installation Guide for Oracle l eaAssist.)

Ant 1.6.5 or later

the Hibernate and C3PO

Assure that Ant and Java paths are properly set. Configure the environment for them as follows:

6.5

dk1.5.0_04

E/bin:$ANT_HOME/bin:$PATH

Export PATH

10 the Hibernate and C3PO Libraries Packaging

Prerequisites to Pacand C3PO Libraries Yo st have configured the application servpackaging the Hibernate and C3PO libraries:

At east one of the following components:

Oracle Siebel eStateme6, 7, and 8 in this guide for instructions on configuring the application server for Oracle SieStatement Manager.

eaAssiSiebe

JDK 1.5

Configuring the Environment for PackagingLibraries

ANT_HOME=/opt/apache-ant-1.

JAVA_HOME=/opt/j

export ANT_HOME

export JAVA_HOME

PATH=$JAVA_HOM

Packaging the Hibernate and C3PO Libraries ▪ Downloading and Installing the Third-Party Libraries


Downloading and Installing the Third-Party Libraries Download the following required third-party libraries:

Hibernate 3.1.3

C3PO 0.9.0

The following table shows the library names and installation instructions for the IBM AIX platform:

JAR File Name

(Linked to the download site)

Operating System

File Name After Downloading

Tool or Commands to Install

hibernate-3.1.3.jar

http://sourceforge.net/project/showfiles.php?group_id=40712&package_id=127784&release_id=403223

UNIX (IBM AIX)

hibernate-3.1.3.tar.gz

gzip -d hibernate-3.1.3.tar.gz

tar –xvf hibernate-3.1.3.tar

c3p0-0.9.0.jar

http://sourceforge.net/project/showfiles.php?group_id=25357&package_id=88527&release_id=341215

UNIX (IBM AIX)

c3p0-0.9.0.bin.gz

gzip -d c3p0-0.9.0.bin.gz

tar -xvf c3p0-0.9.0.bin

Install these libraries on a server that Oracle Siebel eStatement Manager 4.7 application server components can access. Set proper permissions to these libraries in order to package them with the Oracle Siebel eStatement Manager product. The next topic describes packaging.

Packaging Oracle Siebel eStatement Manager This section describes how to package Oracle Siebel eStatement Manager.

To package Oracle Siebel eStatement Manager

1 Edit the EDX_HOME/pkgUtil/package.properties property file located in EDX_HOME/ pkgUtil as shown in the following table:

Property Name Value

EDX_HOME C:/eStatement

HIBERNATE_JARFILE_LOC C:/eStatement/hibernate-3.1

Packaging the Hibernate and C3PO Libraries ▪ Failure Recovery


Property Name Value

C3P_JARFILE_LOC C:/eStatement/c3p0-0.9.0/lib

a Set EDX_HOME to the Oracle Siebel eStatement Manager home.

b Set the property value HIBERNATE_JARFILE_LOC to the Hibernate installation location. If you downloaded the Hibernate jar file some other way, then provide up to the folder location where hibernate3.jar resides. For example, to set the location of the hibernate3.jar file, enter the following statement:

HIBERNATE_JARFILE_LOC=C:/hibernate-3.1

c Set the property value C3P_JARFILE_LOC to the location where the c3p0-0.9.0.jar file resides. For example, to set the c3p0-0.9.0.jar file location, enter the following statement:

C3P_JARFILE_LOC=C:/c3p0-0.9.0/lib

2 Navigate to EDX_HOME/pkgUtil and invoke Ant without arguments. For example,

cd /opt/eStatement/pkgUtil

ant

The Ant script completes the repackaging task and displays a message of success.

Failure Recovery Several reasons exist for getting a BUILD FAILED message during Ant execution:

Incorrect package.properties file:

PRODUCT_HOME is incorrect.

For example, for Oracle Siebel ePayment Manager a valid path entry like the following must exist:

PAYMENT_HOME=/opt/ePayment

Setting an invalid path or property name causes an error, as in the following assignment:

EDX_HOME=/opt/ePayment

Either HIBERNATE_JARFILE_LOC or C3P_JARFILE_LOC is incorrect.

Either the property HIBERNATE_JARFILE_LOC or the property C3P_JARFILE_LOC is not defined at all.

Unavailability of JAR files in the specified locations.

Incorrect JAR file names. The expected jar files are hibernate3.jar and c3p0-0.9.0.jar.

NOTE: You may get a BUILD SUCCESSFUL message without causing any repackaging if you remove the PRODUCT_HOME property from the package.prioperties file.

Packaging the Hibernate and C3PO Libraries ▪ Failure Recovery


System crash during the Ant execution

Lack of free disk space

To recover from any of these issues, correct them and re-invoke the Ant target. No manual removal of partially built components or temporary directories is required.


69

ents, EE applications, and Microsoft Windows services. This chapter applies to all platforms.

The uninstaller does not delete any directories that contain files modified since installation. Instead, it lists these items, which must then be manually removed.

Uninstalling Oracle Siebel eStatement Manager Statement Manager components, you must:

.

.

The Uninstaller is located in the Uninstall folder of your Oracle Siebel eStatement Manager home directory.

1 Navigate to the Uninstall folder of your Oracle Siebel eStatement Manager home directory,

2 UNIX users may l ebel eStatement Manager Uninstaller with the following command. red, and there is no space after the slash.

4

5 Change directory to your Oracle Siebel eStatement Manager home directory and manually remove s necessary.

11 Uninstalling Oracle Siebel eStatement Manager

This chapter describes how to uninstall and remove Oracle Siebel eStatement Manager compondeployed J2UNIX users do not need to uninstall Microsoft Windows services unless your system uses both platforms.

Repeat the sequence used to install components: uninstall Oracle Siebel eStatement Manager from the database server first, then the application server.

Before uninstalling Oracle Siebel e

Stop your application server.

Stop your database instance

Stop your database server.

UNIX users must also switch user to root, which is the default owner of the Uninstall directory

To uninstall Oracle Siebel eStatement Manager

$EDX_HOME.

aunch Oracle Si The dot and slash are requi

./Uninstall_eStatement

3 The Uninstall screen appears.

Click Uninstall. A second uninstall screen appears showing Oracle Siebel eStatement Manager components being removed from your computer.

When the uninstaller is finished, a screen appears listing any items that could not be removed.

any remaining files and directories a

6 Click Done to close the uninstaller.

Uninstalling Oracle Siebel eStatement Manager ▪ Failure Recovery


acle Siebel eStatement Manager, you must first undeploy J2EE ploy

el eStatement Manager Web applications, including Oracle Siebel eStatement Manager and samples.

or more information on deployment, see Deploying and Customizing J2EE Applications Guide for Oracle Siebel eStatement Manager.

7 Repeat this procedure on your application server and any other installations.

Undeploying Oracle Siebel eStatement Manager J2EE Applications When migrating to a new version of Orapplications running on your application server. After you have migrated your database, then redethe new versions of each Oracle Sieb

F


71

Appendix A: Configuring a User Repository

This appendix describes how to configure a user repository.

Configuring a User Repository Follow these steps to configure a user repository.

To configure a user repository:

1 Navigate to Go to Security > Secure administration, application, and infrastructure.

2 Click Security Configuration Wizard to bring up the wizard.

3 Specify the extent of protection by selecting, for example, Enable application security, and click Next.

4 Select a user repository, such as Federated repositories, and click Next

5 Configure the user repository by providing Primary administrative user name and Password, and click Next.

6 In the Summary step, click Finish, and save your user repository configuration.

Now your have defined enabling of both administrative security and application security for your application server.

7 Restart the application server to apply the security configuration.

Appendix A: Configuring a User Repository ▪ Failure Recovery



73

Appendix B: Database Server Environment Variables

This appendix lists the server environment variables for Oracle Database 11g.

Oracle Database 11g Server Environment Variables The following table shows the server environment variables for the Oracle Database 11g server environment.

Variable Definition IBM AIX Custom

EDX_HOME opt/eaSuite/eStatementOracle Siebel eStatement home path

ORACLE_BASE Mount point base path apps/oracle

ORACLE_HOME Oracle product directory $ORACLE_BASE/product/11.1.0.6

LD_LIBRARY_PATH Shared Library Path $ORACLE_HOME/lib:/usr/lib:/usr/ucblib

PATH Database Path $ORACLE_HOME/bin:$PATH

ORACLE_DATA Data File Path $ORACLE_HOME/oradata

ORACLE_PASSWD Database edx

ORACLE_SID Database instance name edx0

ORACLE_USER Database user name edx_dba

ORACLE_DBALIAS Database alias edx.db

Appendix B: Database Server Environment Variables ▪ Oracle Database 11g Server Environment Variables



75

A accessing the IBM WebSphere Console, 35 Ant database build script

preparing to run, 21 application servers supported, 13 applications

deploying, 59 running, 62 sample, 17 undeploying, 72

Authentication Aliases (J2C) creating, 59

B browsers supported, 13

C capturing your UNIX environment for Oracle

Siebel ePayment Manager, 49 classpath and environment variable settings for

IBM WebSphere, 36 Command Center, 17 Composer, 17

installing, 15 configuring

a new Oracle Siebel ePayment Manager database, 27

a new Oracle Siebel eStatement Manager database, 23

data source, overview, 41 edxadmin.properties, 21 environment for packaging Hibernate and

C3PO libraries, 67 eXtended Middleware, 38 eXtended Middleware Architecture for

Hibernate, 38 eXtended Middleware Architecture for logger,

39 eXtended Middleware Architecture for

notification, 38 Java Database Connectivity for Oracle Siebel

eStatement Manager, 51 Java resources, 41 JMS resources, 41, 55

Oracle Siebel ePayment Manager database manually using the Ant script, 29

Oracle Siebel ePayment Manager database using the automated Ant target, 28

properties file payusr.properties, 27 sas.client.props file, 65

connectivity, establishing for Oracle Siebel eStatement Manager, 53

creating a JDBC provider, 52 creating J2C Authentication Aliases, 59 creating, starting, and stopping an IBM

WebSphere Application Server account, 35

D data sources, testing, 55 database

configuring a new Oracle Siebel ePayment Manager, 27

configuring a new Oracle Siebel eStatement Manager database, 23

establishing connectivity for Oracle Siebel eStatement Manager, 53

migrating, 27 partitioning with Oracle Siebel eStatement

Manager, 20 servers supported, 13 where to find components, 16

DefTool, 17 installing, 15

deploying the Oracle Siebel eStatement Manager applications, 59

directory structure, 16 distributed environments, 15 documentation, 8

where to find online, 17 downloading and installing the third-party

libraries, 68

E edx_admin.sh, 19 edx_config

setting UNIX environment data with, 47 edxadmin.properties

configuring, 21 environment data on UNIX

passing to your application server, 47

Index

Index ▪ Oracle Database 11g Server Environment Variables


environment variables for Oracle Database 11g server, 75

eXtended Middleware Architecture configuring, 38 configuring for logger, 39 configuring for notification, 38 configuring Hibernate properties, 38

F failure recovery, 69

H hardware requirements, 12 help

where to find online, 17 Hibernate and C3PO libraries

configuring the environment for packaging, 67

prerequisites to packaging, 67 Hibernate, configuring eXtended Middleware

Architecture, 38

I IBM WebSphere Application Server

accessing the console, 35 classpath and environment variable settings

for, 36 creating, starting, and stopping an account,

35 starting and Stopping, 46 UNIX environment variables for, 46 UNIX permissions, 45

input and output data where to find, 17

installation process, 11 installing design tools, 15 installing Oracle Siebel eStatement Manager

from the distribution medium, 15

J JAVA and C++ system requirements, 12 Java Database Connectivity

configuring for Oracle Siebel eStatement Manager, 51

Java resources overview of configuring, 41 overview of configuring data source, 41

JDBC about connections for Oracle Siebel

eStatement Manager, 52 configuring for Oracle Siebel eStatement

Manager, 51

creating provider, 52 JMS resources

configuring for Oracle Siebel eStatement Manager, 55

overview of configuring, 41

L library files

where to find, 16 logger

configuring eXtended Middleware Architecture, 39

M migrating

an existing Oracle Siebel eStatement Manager database, 27

Oracle Siebel ePayment Manager database, 30

N notification

configuring eXtended Middleware Architecture, 38

O open source items required, 13 operating system

requirements, 12 Oracle Database 11g server environment

variables, 75 Oracle Siebel ePayment Manager database

configuring manually using the Ant script, 29 configuring using the automated Ant target,

28 migrating, 30

Oracle Siebel eStatement Manager directory structure, 16 JDBC connections, 52 packaging, 68 running the applications, 62 system requirements, 12 undeploying applications, 72 uninstalling, 71

overview of installation process, 11

P packaging

Oracle Siebel eStatement Manager, 68 prerequisites for the Hibernate and C3PO

libraries, 67

Index ▪ Oracle Database 11g Server Environment Variables


payusr.properties configuring, 27

permissions database server, 19 installation, 15

preparing to run the Ant database build script, 21

prerequisites to packaging the Hibernate and C3PO libraries, 67

properties file payusr.properties configuring, 27

R recovering from failure, 69 running Oracle Siebel eStatement Manager, 62 running Scheduler, 63

S sample applications

where to find, 17 sas.client.props

configuring, 65 Scheduler

running, 63 security level

setting, 65 server components

where to find, 16 setting Total Transaction Lifetime Timeout, 51 setting UNIX environment data with

edx_config, 47

starting and stopping an IBM WebSphere Application Server account, 35

starting and stopping IBM WebSphere, 46 system requirements, 12

T testing data sources, 55 third-party libraries

downloading and installing, 68 tools

installing, 15 Total Transaction Lifetime Timeout

setting, 51

U undeploying Oracle Siebel eStatement Manager

applications, 72 uninstalling Oracle Siebel eStatement Manager,

71 UNIX environment

capturing for Oracle Siebel ePayment Manager, 49

variables for IBM WebSphere, 46 UNIX permissions

for installation, 15 for the IBM WebSphere Application Server,

45 for your database server, 19

using database partitioning with Oracle Siebel eStatement Manager, 20

Installation Guide for Oracle Siebel eStatement Manager

Documents

Transcript of Installation Guide for Oracle Siebel eStatement Manager