You are on page 1of 22

Collection Installation

Manual
Process Engineering Research Center
Nalanda Institute

Volume 1 of 1
Part no: PSL / Intellect / Intellect-Collection / 9.1.0 / 001

COPYRIGHT NOTICE
Copyright © 2004 Polaris Software Lab (PSL)
All rights reserved.

These materials are confidential and proprietary to PSL and no part of these materials should be reproduced,
published, transmitted or distributed in any form or by any means, electronic, mechanical, photocopying, recording
or otherwise, or stored in any information storage or retrieval system of any nature nor should the materials be
disclosed to third parties without the prior express written authorization of PSL. Information in this document is
subject to change without notice and does not represent a commitment on the part of PSL. The software described
in this document is furnished under a license agreement and nondisclosure agreement.
Installation Manual

CONFIDENTIALITY:
This publication contains proprietary information from Polaris Software Lab Limited. The recipient should not disclose this
information to any third party without the prior written permission of Polaris Software Lab Limited.

DISCLAIMER:
Although Polaris uses its best endeavours to ensure accuracy of the contents, Polaris assumes no responsibility for any
inadvertent error or omission that may appear in this document.

TRADEMARKS:
The trademarks mentioned below belong to Polaris Software Lab Limited.

Trademark of Polaris Software Lab Limited.


Registered Office: Polaris House, 244, Anna Salai, Chennai – 600 006, India

Trademark of Polaris Software Lab Limited.


Registered Office: Polaris House, 244, Anna Salai, Chennai – 600 006, India

DOCUMENT INFORMATION:
Version no: 9.1.0
th
Version date: 13 October 2004
No. of volumes: 1
Volume no. of this document: 1
Part no: PSL / Intellect / Intellect-Collection / 9.1.0 / 001

CONTACT PERSON:
Tarachand Dethe
Polaris Software Lab Limited
Ridge Business Center, First Floor, B-Wing,
Mahindra Towers, Worli
Mumbai 400 018 , INDIA

Tel: +91.22.5662 8383


Fax: +91.22.2494 1311
Visit us at: www.polaris.co.in

Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 /August 2004 i
Installation Manual

Table of Contents

1 INSTALLATION INSTRUCTIONS FOR COLLECTION 1

1.1 Introduction 1

1.2 Pre-Installation Activities 1

1.3 Intellect Collection Installation 2

1.4 Configuring ARMOR Client components 16

ii Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 /August 2004
Installation Manual

1 Installation instructions for Collection

1.1 Introduction

The system engineers and program managers/supervisors need to use this manual
to enable them to install the Intellect-Collections system.

This document gives the detailed installation instructions for Collection.

Requirements
• Weblogic 6.1 Service Pack 4
• Oracle 8.1.7 and above
• Windows NT/2000 or Unix environment
• Apache Ant 1.6.1

1.2 Pre-Installation Activities

a) For Intellect Collection’s data base installation, it is assumed that cashcore,


reports and charges database already exists. If not, then please install before
proceeding further.
b) For Installing Intellect Collections Application , Please complete following
steps before procedding further
• If you are installing the application with armor version then read
armor installation guide to modify armor related files for collections.

c) Make sure that Ant 1.6.1 is installed.

d) Edit the following properties files as per instruction given in the respective
files. Please edit the fields in these files very carefully, all entries should be as per
comments in the properties file.

InstallCollection.properties
RDBMS.properties
InstallCollection.sh/InstallCollection.bat

Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 / August 2004 1
Installation Manual

1.3 Intellect Collection Installation


Once step 1.2 is completed then run InstallCollection.sh/
InstallCollection.bat as per your Operating system. If it’s a Windows system, run
InstallCollection.bat, and if it’s a Sun Solaris system, run InstallCollection.sh.

There will be different options in the command prompt, Choose the


appropriate option as applicable and press <Enter>. The options supported are:

1. Create Intellect Collections Enterprise Archive.


2. Create Intellect Collections Database.
3. Create both 1 & 2.
4. Exit.

After successful completion (choosing options 1, 2, 3), all the files will be copied
to the area (now onwards we will refer this as output area) which you have
specified in the field

“Collection.App.home” of InstallCollection.properties

1.3.1 For Database Installation

Once The Database is installed run the below mentioned script in sqlplus
prompt given with the Release.

• ReportsStaticUnloads.sql
Replace @REPORT_SCHEMA@ in the sql with report schema and run this
from reports schema.

(Command Usage: @ ReportsStaticUnloads.sql in sqlplus. This should be run


on the reports schema)
• Snap_Acctents.sql (Run this from COLL_SCHEMA)

After Intellect Collection database is installed, please login to COLL_SCHEMA/


REPORT_SCHEMA/CHARGES_SCHEMA database and compile all the uncompiled
pl/sql programs. For information purpose all the script which has been run to create
collections database is placed in output area/database.

2 Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 /August 2004
Installation Manual

If you found any error then please check the log which is placed in
/orbicoll/temp/Product/Log. Possible cause could be wrong entries in
properties files. If you wish to modify any value in the properties files then
update the properties files, logout from the collections database and run
InstallCollection.sh/InstallCollection.bat. Choose option 2 to install database
only. Database scripts will be copied to the output area/database area .

1.3.2 For Application server installation

All required files has been copied in the following folders of output area

Ear contains collections.ear which needs to be deployed in the weblogic


Lib contains the required libraries for collections application.
ksh contains the executable files for report.
If you do not find the above files then please check the log which is
present in /orbicoll/temp/Product/Log/logfile.log.

Please follow the below mentioned activity to perform weblogic settings.

Please make sure that Weblogic 6.1 SP4(Service Pack 4) is installed before
proceeding further. Once installed, please follow the below steps carefully for
installing collections and enter the same information as you have given in
properties file.

Bring up the weblogic server and login to the weblogic console. On the console,
under the domain node, go to Services JDBC. Configure the database
connections under JDBC node as mentioned below:

JDBC Settings:

1. Create Database Connection Pools:


Create two pools as below (the actual pool name can be changed during
installation):-
oraclePool : Pointing to collection schema
rhPool : Pointing to report schema
Step 1: In General tab,
Name= <pool name>
(Pointing to collection/report schema)
URL= jdbc:oracle:thin:@<IP Where oracle is installed>:<Port
Number of the Database>:<Oracle SID>

Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 / August 2004 3
Installation Manual

Driver Class Name=oracle.jdbc.driver.OracleDriver


Properties
user=<user id of the corresponding schema >
password=<password of the above user>

Fig 1.0
Step 2: Then click Connection Tab and fill the textboxes as shown in the
window below (values given below are sample values)
Initial Capacity=10
Maximum Capacity=40
Capacity Increment=1
Login Delay Seconds=1
Refresh Period=10
Check “Allow Shrinking” box
Shrink Period=15

4 Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 /August 2004
Installation Manual

Fig 1.1
Step 3:- Click Targets Tab and select target server Available Chosen (myserver
Here). Then click Apply button.

Fig 1.2

Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 / August 2004 5
Installation Manual

2. Creating DataSource:
Step 1 Now click on Data Sources under JDBC on left hand side, fill the
entries as per the screen below pointing to collection pool (oraclePool).
(The jndi name must be same as the data source name, and the value must
be the same as given in the properties file InstallCollection.properties for the key
“weblogic.datasource.name”)

Step 2: Click Targets Tab and select target server Available Chosen
(here myserver). Then click Apply button.

Refer Fig 1.2 Above

3. Creating TXDataSource:
Pointing to collection pool (oraclepool) Follow the same step of
Creating DataSource to create transaction DataSource.
(The jndi name must be same as the Transaction data source name, and
must be the same as the value entered for the key “weblogic.Txndatasource.name” in
InstallCollection.properties)

6 Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 /August 2004
Installation Manual

JMS Connections

On the console, under the domain node, go to Services-> JMS. Configure


the JMS connections under JMS node as mentioned below:

1.Create JMS Connection Factory in weblogic:

Step 1: Give name =CollectionsConnectionFactory


Give the JNDI name for the connection factory as follows,
com.orbitech.cash.collections.jms.CollectionsConnectionFactory
Keep default delivery mode as non-persistent

Step 2 Click Targets Tab and select target server Available Chosen (here
myserver). Then click Apply button.
Refer Fig 1.2

Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 / August 2004 7
Installation Manual

2 Create JMS Server: CollectionJmsServer


Step 1: Create the Destinations for CollectionJmsServer as in the screen below.

Step 2 : Click Targets Tab and select target server Available Chosen (here
myserver). Then click Apply button.

8 Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 /August 2004
Installation Manual

Create JMS queue and JMS topic as below (by clicking on domain name->services-
>JMS->Servers->CollectionJMSServer->Destinations)

Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 / August 2004 9
Installation Manual

Create JMS Queue as below:


Name: DispatchJMSQueue
JNDI NAME: DispatchJMSQueue

Name: StatusServerIN
JNDI NAME: com.orbitech.cash.collections.statusserver.StatusServerIN

Name: DDBillPaymentsJMSQueue
JNDI NAME: DDBillPaymentsJMSQueue

Name: StatusServerOUT
JNDI NAME: com.orbitech.cash.collections.statusserver.StatusServerOUT

Name: WatchdogCommandQueueOUT
JNDI NAME:
com.orbitech.cash.collections.watchdog.WatchdogCommandQueueOUT

10 Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 /August 2004
Installation Manual

Create the JMS Topics as follows,


JMS TOPIC: WatchdogCommandTopic
JNDI NAME:
com.orbitech.cash.collections.watchdog.WatchdogCommandTopic

JMS TOPIC: WatchdogStatusTopic


JNDI NAME: com.orbitech.cash.collections.watchdog.WatchdogStatusTopic

After completing weblogic settings, Enter the path for weblogic home and output
area in the below mentioned fields then append the following entries in weblogic
start.sh/ weblogic start.bat file.The CoreClient.jar specified in the start script has
to be taken from charges official release.

In Case Windows BAT File :


The CoreClient.jar specified in the Classpath should be taken from Charges
Official Release.
set WL_HOME= <Enter weblogic home path> # e.g. c:\bea\wlserver6.1
Set COLL_HOME=<Enter output area>

set
COMMON_CLASSPATH=%COLL_HOME%\lib\Armor.jar;%COLL_HOME%\
lib\ commons-logging.jar;%COLL_HOME%\lib\log4j-1.2.6.jar;

set
COLL_CLASSPATH=%COLL_HOME%\lib\properties.jar;%COLL_HOME%\li
b\ picklist.jar;CoreClient.jar;

set
WL_CLASSPATH=%WL_HOME%;%WL_HOME%\lib\weblogic_sp.jar;%WL
_ HOME%\lib\weblogic.jar

set
CLASSPATH=%CLASSPATH%;%COMMON_CLASSPATH%;%WL_CLASS
PATH%;%COLL_CLASSPATH%

echo %CLASSPATH%

In Case Unix sh File :

WL_HOME= <Enter weblogic home path> # e.g. /bea/wlserver6.1

Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 / August 2004 11
Installation Manual

COLL_HOME=<Enter output area>

COMMON_CLASSPATH=$COLL_HOME/lib/Armor.jar:$COLL_HOME/lib/co
mmons-logging.jar:$COLL_HOME/lib/log4j-1.2.6.jar:

COLL_CLASSPATH=$COLL_HOME/lib/properties.jar:$COLL_HOME/lib/pic
klist.jar:CoreClient.jar;

WL_CLASSPATH=$WL_HOME:$WL_HOME/lib/weblogic_sp.jar:$WL_HOM
E/lib/weblogic.jar

CLASSPATH=$CLASSPATH:$COMMON_CLASSPATH:$WL_CLASSPATH:
$COLL_CLASSPATH

echo $CLASSPATH

After updating the weblogic server startup script start the weblogic server.
i) Login into the weblogic console.
ii) In the menu navigate to <domainname> Deployment
Applications.
iii) Click on Install a new Application... (If it’s a Unix environment, click on
“Configure a new Application”, and enter name as “collections” and path as
<output area>/collections.ear
iv) In the resulting screen (as shown below) click on Browse… and navigate
to the output area/ear and select collections.ear.

12 Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 /August 2004
Installation Manual

v) Now click on Upload.


vi) After uploading, in the same page, under Application files currently installed:
one more entry would have been added as ,
.\config\<domainname>\applications\collections.ear

vii) Again navigate to <domainname> Deployment Applications from the


menu. The following entry should be present.

Name collections
JNDI Name .\config\<domainname>\applications\collections.ear
Deployed True
Components 2

viii) Navigate to <domainname> Deployment Applications collections


collections from the menu.

Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 / August 2004 13
Installation Manual

a) In the resulting screen, click on Monitor Monitor all Stateless EJBRuntimes…

Check that ,

SSBAcctEntryListener
SSBStatusServer
RequestSessionFlexibleBOIImpl
com.orbitech.cash.collections.statelessbean.operatorid.OperatorIdHome
ConsolidationServer
SSBCacheController
LineBooking
DateRecalculation
DispatchServer
ChargeTxnManager
keyGen
EventDecisionEngine
RequestSession
EventManager
CL410SP
CRGetDetails

14 Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 /August 2004
Installation Manual

LockManager
EntityCreationServer
SSBWatchdogHelper
SSBValidationServer
CCEntityManager
IFTEntityManager
DDBillPresentmentManager
DDChargeTxnManager
DDEnrollmentManagerBean
DDTransactionManagerBean
DDPaymentManager
CollSynchronizer
CollRcvEntityManagerBean
OrbiRecvHelper
are present in the ensuing list.

b) In the resulting screen, click on Monitor Monitor all State full


EJBRuntimes…

SSBCacheManager

c) In the resulting screen, click on Monitor Monitor all Message Driven


Beans…
WatchdogMDB
StatusServerMDB
DispatchMDBean
DDBillPaymentMDB

ix) Navigate to <domainname> Deployment Applications collections


collections from the menu.
x) In the resulting screen, click on Monitor Monitor all Servlet Runtimes…

Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 / August 2004 15
Installation Manual

xii) Check that /LL & /RefreshConfigFiles Servlet are present in the above screen.

Now Collections application has been installed. Restart the weblogic server and login
to application & verify.

If you find any error then Please check the values you have entered in all the
properties files. If you found any values are wrong then change the value and re run
InstallCollection.sh/InstallCollection.bat. Now you can choose option 1 to install
application only and login to weblogic console and update the ear from output
area/ear.

16 Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 /August 2004
Installation Manual

1.4 Configuring ARMOR Client components

1. Deploy all of ARMOR client components as per the ARMOR client deployment
guide.

Update the CLASSPATH in the weblogic startup script with the path of
the following jar files along with the file names. Also update the CLASSPATH
with the path of the directory in which the INI files are kept. These entries must
be prefixed to the existing CLASSPATH.

• Armor.jar

• ArmorALLCrypto.jar

• ArmorCommon.jar

• ArmorSSO.jar

• ArmorTktStub.jar

• ArmorTktVal.jar

Also update the following configuration files in the above tar file.
a) NSECAuthenticationInfo.INI
Update the USERID to the Armor super user
b) NSECConnectionParam.INI
URL=<host name of the server where Armor is installed>:<port number>
c) NSECConstants.INI
SERVER_NAME =<host name of the server where Armor is installed>
SMSPATH=/usr1/sms/data
DOMAIN_NAME=<domain name>
LOGPATH=<path where the logs are to be generated>
SOCKET_TIMEOUT_INTERVAL=180000
d) NSECTrustedCredentials.INI

Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 / August 2004 17
Installation Manual

IP=< host name of the server where Armor is installed>


(Before accessing the application through armor, confirm that the internet
proxy is disabled and host name of the armor server and application server is
entered along with their IP in the “hosts” file. For accessing the hosts file,
click on start-> Run. Type “drivers” and browse to etc->hosts. )

***************************************************

18 Copyright © 2004, Polaris Software Lab Limited / Version 9.1.0 /August 2004

You might also like