User:Dt750/Temp/V+DocBAT.doc

Table of Contents

Document version management3

Introduction4

Server5

AS servers5

Configuration5

File system5

Application user6

SB/DB Server6

File System6

Application user6

Typical installation7

DB_TOOLS7

Target Folder on M1 AS Server7

Actions7

TNP_DDL 7

Target Folder on M1 AS Server7

Actions7

TI Linux7

Target Folder on DB Server7

Actions8

Service Broker Linux8

Target Folder on DB Server8

Actions8

Start SB8

Stop SB 8

Service Broker Initial Load8

Target Folder on DB Server8

Actions8

Vestima Plus 9

Target Folder on M1 AS Server9

Actions9

Installation Step10

Monitoring12

run_diags.sh12

run_diags_hourly.sh12

run_diags_mans_after_DTP.sh12

How to13

Start/Stop Admin Server V+13

Start/Stop Node V+13

Start/Stop Service Broker13

Full load of the GFDM Data13

Creation of a user ADMIN linked to the participant ADMIN 14

Reference data XML file - Manual load14

Prepare the TNP DB for an installation on a production data-capture14Document version management

This table is to be completed each time the document is distributed and someone requires action.

Introduction

This document aims to explain how to use V+ in testing environment: server, file system, environment configuration …

Also this document describes how put in place the monitoring procedure in testing environment.

Server

AS servers

Configuration

V+ uses one or two hosts (2 AS in production). In testing environment, it’s defined in TIIWEB:



The configuration server is defined in the TNP xml configuration file:



 auburn 

 9213 

 10.254.218.9,10.254.218.104 





auburn

…

< /machineM1>



mobile

…

< /machineM2>

File system

Here is the file system structure used by TNP AS (same configuration for 1 or 2 AS) in a testing environment.

root/filesystem

--+ /vestbinfilesystem

+ logs/ filesystem

+ data/TNP MOUNT NFS on

db server

/vestdb/data/TNP

Application user

The application user is tnpmgr

SB/DB Server

V+ used the same host for the DB and the service broker :



File System

Here is the file system structure used by TNP SB/DB in a testing environment.

root/filesystem

--+ /vestdbfilesystem

+ data/TNP filesystem

--+ /vestservinffilesystem

+ TNP filesystem

+ TNP/appl filesystem

+ TNP/data filesystem

+ TNP/logs filesystem

+ TNP/opt filesystem

Application user

The application user is tnpsimgr

Typical installation

The order of the different installation steps in the eepr documentation is the standard order to be followed during a complete installation of Vestima+.

DB_TOOLS

Only on M1 machine

Target Folder on M1 AS Server

/vestbin/deployment/DB_TOOLS 

If this directory not exists, you have to create it

Actions


 * 1) Create a new directory under /vestbin/deployment/DB_TOOLS with a concatenation of the EPR id and the EPR name. e.g. :

/vestbin/deployment/DB_TOOLS/244694--CBLR1160-DB_TOOLS-UNIX-Release_4.00 


 * 1) Untar the EPR under the target directory above

TNP_DDL

Only on M1 machine

Target Folder on M1 AS Server

/vestbin/deployment/TNP_DLL 

If this directory not exists, you have to create it

Actions


 * 1) Create a new directory under /vestbin/deployment/TNP_DDL with a concatenation of the EPR id and the EPR name. e.g. :

/vestbin/deployment/TNP_DDL/252168--CBLR1160-TNP_DDL-UNIX-Release_14.00 


 * 1) Untar the EPR under the target directory above
 * 2) Follow the documentation from the TNP_DDL. Nothing more special here. The installation is a typical installation of DDL.

TI Linux

On TNP_DB / ServiceBroker machine

Target Folder on DB Server

/vestservinf/TNP/appl/ti 

Actions

Simply untar the EPR under the target directory

Service Broker Linux

On TNP_DB / ServiceBroker machine

Target Folder on DB Server

/vestservinf/TNP/appl 

Actions


 * 1) Untar the EPR under the target directory
 * 2) Go to directory :

/vestservinf/TNP/appl/servicebroker/scripts/install 


 * 1) Run the script :

./InstallServiceBroker.pl –env BAT (PROD when production)

Start SB


 * 1) Go to directory :

/vestservinf/TNP/appl/servicebroker/etc 


 * 1) Run the script :

./startServiceBroker.ksh

Stop SB


 * 1) Go to directory :

/vestservinf/TNP/appl/servicebroker/etc 


 * 1) Run the script :

./stopServiceBroker.ksh

Service Broker Initial Load

On TNP_DB / ServiceBroker machine

Target Folder on DB Server

/vestservinf/TNP/appl/SBIDL

Actions


 * 1) Untar the UC4_SCHEDULE EPR under the target directory
 * 2) Go to directory :

/vestservinf/TNP/appl/SBIDL/scripts 


 * 1) Run the script :

./load_SVC.ksh -t /vestservinf/TNP/appl/SBIDL/data/templates/sql -a svcinfr_owner/PASSWD@TNP_DB -e A00 

with the following parameters:


 * PASSWD: the password of the app user svcinfr_owner on the DB TNP. To get this value, here is the command:

get_passwd svcinfr_owner host_TNP_DB 


 * DB: the SID of the DB in the cycle testing. This information is on TiiWeb




 * A00: 00 must be replaced by the value of MF Environment in TiiWeb:



Vestima Plus

Only on M1 machine

Target Folder on M1 AS Server

/vestbin/deployment/VESTIMA_PLUS 

If this directory not exists, you have to create it.

Actions


 * 1) Create a new directory under /vestbin/deployment/VESTIMA_PLUS with a concatenation of the EPR id and the EPR name. e.g. :

/vestbin/deployment/VESTIMA_PLUS/ 252190--CBLR1160-VESTIMA_PLUS-UNIX-Release_1.00 


 * 1) Untar the EPR under the target directory above
 * 2) Untar the second tar file :

vestimatnpPreDelivery.tar 


 * 1) Follow the EPR documentation. Each step with ‘Y’ flag has to be to execute.



Installation Step

Directory structure creation
Creates empty directory structure for Vestima+ runtime. The shell creates the directories for the in/out data storage.

./install/dirstructure.sh 

Database data cut-over
Performs the data cut-over, DB packages installation and run checks. The preparation and check of the DB is done by DBprep.sh script. The script provides following modes:


 * ALL: DDl checks, Create type, Insert QAPI, IDL delta, IDL checks, packages compilation, cutover and cutover checks.

Do not run twice “DBprep.sh ALL” without checking with Development team !


 * PACKAGE: only packages compilations
 * DDL_CHECK: only DDL checks

Only option ALL shall be run as part of the FULL installation process, do NOT use any of the other options if not instructed to.

./install/DBprep.sh ALL

Directory structure creation
Creates empty directory structure for Vestima+ runtime. The shell creates the directories for the in/out data storage.

./install/dirstructure.sh 

Domain creation
Creates the Vestima+ Weblogic domain : the shell creates and installs the Weblogic domain according to the tnpenvconfig.xml. The WLS domain is created from a Weblogic template and then customized by WLST scripts. All this is happening automatically by running following commands:

./install/domain.sh 

Application resources installation
Installs the Vestima+ application : After a Weblogic domain is created the application can be installed. By application is meant server-side (TNPapp.ear) and client-side shell scripts and data.

The application can be installed either on old existing domain in case there is no change in the Weblogic setting or can be installed on newly created domain.

./install/app.sh 

Replication
Only if you have 2 AS servers (M1 and M2)

Full

Replicates the domain+application to the second host To replicate everything including the Weblogic domain run:

./install/ fullreplication.sh 

As a result a fullreplication.tar is created in the tmp folder.

On the second machine, remove the boot.properties file before untar the replication file.

rm /vestbin/appl/TNP/user_projects/domains/TNPcluster/boot.properties 

This tar has to be transferred to the secondary machine (M2) and extracted in the TNP_ROOT directory. (TNP_ROOT is where the application is actually running)

App

Replicates only the application to the second host: In case there is no change on the Weblogic domain settings, there is a possibility to replicate everything apart the Weblogic domain.

To replicate everything apart the Weblogic domain:

./install/ appreplication.sh 

As a result a appreplication.tar is created in the tmp folder.

This tar has to be transferred on to the secondary machine (M2) and extracted in the TNP_ROOT directory. (TNP_ROOT is where the application is actually running)

Monitoring

Some scripts are used in test to simulate patrol monitoring (script -diagnostic mode- and logs) with several features added.

There are several areas to be monitored, which are splitted by periodicity:


 * run_diags.sh : execute manually one or two times per day
 * run_diags_hourly.sh : executed via the cron table, every hour from 8AM to 6PM
 * run_diags_mans_after_DTP.sh : execute manually after the DTP

run_diags.sh


 * Verifying TNP Server, shell and scripts log files for ORA-, Critical, Alert, Emergency, Exception, Error, ...
 * Different monitor scripts :
 * Running monitoring_notifier.sh
 * Running Monitoring of the UC4 waiting job -> wait_job_checker.sh
 * Running Monitoring of the provision rechecking optimizer -> monitoring_pc_events_diag.sh
 * Running Monitoring of the consistency of orders feed back flag -> monitoring_CheckPcFeedBackFlag_diag.sh
 * Running Monitoring of the consistency of orders provision checking quantity: -> monitoring_CheckPcQuantity_diag.sh
 * Running Monitoring of the consistency of provision checking remaining positions -> monitoring_CheckPcRemainingPosition_diag.sh
 * Running Monitoring of the consistency of orders provision checking state -> monitoring_CheckPcStatus_diag.sh
 * Running Monitoring of the consistency of the account from Account Master
 * Running Monitoring of the orders last pending provision computation type or the sum of quantities
 * Running Monitoring of the consistency of the account from Account Master

run_diags_hourly.sh


 * Monitoring on the OAQs
 * Monitoring on the Vestima technical bus
 * Monitoring of the Vestima interfaces
 * Monitoring of the TFax interface
 * Monitoring on the Oracle Notifier
 * Monitoring of the Diskspace
 * Monitoring on the Service Broker

run_diags_mans_after_DTP.sh


 * Verifying in DB if the synchronisation is done correctly after the DTP

How to

Start/Stop Admin Server V+

startADM

or

stopADM

The Admin server is up when, in the Admin log, you have the status “Running” like this :

tail -3000f vestimaTNP.TNPServer_Admin.out.log.111219235961522

 ..  …

Start/Stop Node V+

startS1, startS2, startS3, startS4

or

stopS4, stopS3, stopS2, stopS1

Start/Stop Service Broker

/vestservinf/TNP/appl/servicebroker/etc/startServiceBroker.ksh

or

/vestservinf/TNP/appl/servicebroker/etc/stopServiceBroker.ksh

Full load of the GFDM Data

A special procedure must be applied to load the full data set extracted from GFDM. In this case a parallel load is done.

The following files must be extracted from GFDM:

The files must be stored in the path defined in the ksh variable DATADIR in the script run_parallel_loader.sh described below.

From the Vestima+ root installation directory, go to the directory of “manual” scripts:

cd clientside/bin/manuallytriggered/loader

Run the load:

./run_parallel_loader.sh

The logs of the parallelization process are available in the files “XML file name”.log in the standard log directory (illustration Address.log).

The logs of the load itself are also in the standard log directory, file vestimaTNP.TNPloader.cron.log.$DATE

Creation of a user ADMIN linked to the participant ADMIN

If it is needed to create a user ADMIN linked to the participant ADMIN after the GFDM data load to test the load, please apply the following procedure:

cd clientside/bin/manuallytriggered/cutovers/05TNPPhaseI

$ CONNECT TO THE TNP DB AS TNP_OWNER

SQL>@create_user_admin_for_participant_admin.sql;

SQL>exit;

It will create a user “ADMIN” linked to the participant ADMIN.

The user will have the role Internal System Administrator (ISA)

The user password will be “administrator”

It is a temporary password, so the first time that this user will log on TNP, he will be asked to change its password.

Reference data XML file - Manual load

The run_manual_loader.sh script is located in directory clientside/bin/manuallytriggered/loader.

In order to load some of the reference data that are not available to be set via Contact Manager, run the following command:

./run_manual_loader.sh filename

filename is the complete path of the file you want to load. It can be located wherever you want on the file system.

This script will produce a log file located in the standard log directory. Its filename is vestimaTNP.TNPloader.cron.log.${date}.

If the files are successfully loaded, they are moved to:

“local root”/import/reference_data/arch

In case of errors, they are moved to:

“local root”/import/reference_data/error

(Usually “local root” is /local/tnp)

Prepare the TNP DB for an installation on a production data-capture

To reset the password of the user ADMIN of the participant ADMIN, execute as TNP_OWNER:

UPDATE appl_wks_user

set WKS_PSWD = '200ceb26807d6bf99fd6f4f0d1ca54d4',

TMP_PSWD_FLG = 'Y',

NBR_LOGIN_ATMPT_CNT = 0,

WKS_USER_STATUS_CD = 10,

LST_UPD_TMSTMP = sysdate,

LST_UPD_USER_ID = 'RESET-PASSWORD'

where APPL_WKS_USER_ID =(select u.APPL_WKS_USER_ID

from appl_wks_user u, part_user_relship pu, part_detl p

where u.APPL_WKS_USER_ID = pu.APPL_WKS_USER_ID

and pu.PART_DETL_ID = p.PART_DETL_ID

and PART_NM = 'ADMIN'

AND user_login_val = 'ADMIN');

update APPL_WKS_PSWD_HIST h

set h.ISRT_TMSTMP = sysdate

where APPL_WKS_USER_ID =(select u.APPL_WKS_USER_ID

from appl_wks_user u, part_user_relship pu, part_detl p

where u.APPL_WKS_USER_ID = pu.APPL_WKS_USER_ID

and pu.PART_DETL_ID = p.PART_DETL_ID

and PART_NM = 'ADMIN'

AND user_login_val = 'ADMIN');

COMMIT;

It will reset the password of the user to “administrator” and this password will be set as temporary.