W742 2011oct28 SOD CHG

ImageMark ECPIX 4.
Clearing House Gateway- Start and End of Day Operations
B004-0000-0742 October 2011
The product described in this book is a licensed product of NCR Corporation. Other brand and product names appearing in this publication are the trademarks or registered trademarks of their respective holders. It is the policy of NCR Corporation (NCR) to improve products as new technology, components, software, and firmware become available. NCR, therefore, reserves the right to change specifications without prior notice. All features, functions, and operations described herein may not be marketed by NCR in all parts of the world. In some instances, photographs are of equipment prototypes. Therefore, before using this document, consult with your NCR representative or NCR office for information that is applicable and current. To maintain the quality of our publications, we need your comments on the accuracy, clarity, organization, and value of this book. Address correspondence to: NCR Waterloo Attention: Information Engineering 580 Weber Street North P.O. Box 1611 Waterloo, Ontario, Canada N2J 4G5 Copyright 2011 By NCR Corporation Duluth, Georgia U.S.A. All Rights Reserved
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5 5 6
Revision Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Chapter 1: Start-of-Day Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Check Status of Daily Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Run the Check_Backup_Status.bat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitor Free Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clean Physical Backup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check the Status of Cleanup Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify the Size of Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JRUN Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ECPIX Diag Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Oracle Listener Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Oracle Alert Log and Trace Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NRCryptoAPI Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check Status of EBS, Oracle, JRun, Syslog and Media Manager Services . . . . . . . . . . . . . . . . . Start Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stop Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restart EBS and Macromedia JRun Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restart IBM Websphere Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communicate Errors to Support Personnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ensure Network and FTP Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check Version of CHT and WCS Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check Version of CHT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check Version of WCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check Index Rebuild Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check Status of the Backup Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check Status of the Restore Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 14 16 17 19 20 20 22 23 24 25 26 27 28 29 30 34 35 37 37 39 40 40 40
Chapter 2: End-of-Day Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Check Successful Generation of PXF, RF, EF, and .eos Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
ImageMark ECPIX 4.4 - Clearing House Gateway - Start and End of Day Operations
Contents
Verify Generation of Posting Files and Return Files on Application Screen . . . . . . . . . . . . . . Verify Generation of PXF, RF and EF on Hard Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify Generation of .eos File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Confirm Receipt of OACK and Response Files at the Capture System . . . . . . . . . . . . . . . . . . . . . Check Bundle Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify Session and Daily Reports are Generated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify Session Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify Daily Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generate Audit Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check Available Disk Space for Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Respond to System Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communicate with the Clearing House . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify the Count of Sub Jobs for System.CleanupA Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44 45 45 46 47 48 48 50 51 53 54 55 56
Appendix A: Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
LEVEL 0/LEVEL 1 Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LEVEL 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LEVEL 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RMAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 58 59 60
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Preface
About This Book
This book provides a checklist to perform daily start and end of day operations.It describes features and functions, including reports, supported by the ECPIX system. Some of these features or functions may not be implemented in or applicable to your environment. This document is provided for informational purposes and is subject to change without notice.
Audience
This book is intended for the following ECPIX personnel:
Clearing House Gateway (CHG) Operations Personnel
Pre-requisites

ImageMark ECPIX 4.0: Product Overview (B004-0000-0414) ImageMark ECPIX 4.0: Clearing House Gateway Operations (B004-0000-0415) ImageMark ECPIX 4.0: Clearing House Gateway Administration (B004-0000-0416) Basic computer knowledge Basic understanding of Clearing House rules, and the cheque clearing environment and related procedures
Preface
Conventions
Within the procedures described in this book, conventions help you to identify different types of information.
Bold
Bold identifies anything you must select, choose, run, press, or type. For example: Type XYZ, and press Enter.
Chevrons
Chevrons (>) indicate a series of menu selections. For example: Choose File > Import > Formats.
Italics
Italics identify a placeholder that must be replaced with your own specific information. For example: device=c:\path\7780mint.sys type=H. Italics are also used for emphasis.
Notes, Tips, Important, Cautions, Warnings

Notes, cautions, and warnings alert you to important or critical information. Each is displayed in a different way:
Note: Notes contain information that has special importance.
Tip: Tips contains useful advice for the user on tasks or procedures.
Important: Important text contains information to which the reader should pay close attention.
Caution: Cautions alert you to procedures or conditions that could damage equipment or data.
Warning: Warnings alert you to procedures or conditions that could cause personal injury.
Revision Record
October 2011 Section Start-ofDay Operations Revision Added the following sections:

Check Status of the Backup Process Check Status of the Restore Process
September 2011 Section Start-ofDay Operations Revision Added the Check Index Rebuild Status section.
June 2011 Section Start-ofDay Operations Revision Added a section Restart IBM Websphere Services.
March 2011 Section Start-ofDay Operations Revision Added a section NRCryptoAPI Log.
Revision Record
September 2008 Section Start-ofDay Operations Section Start-ofDay Operations Section End-of-Day Operations Revision Added information on IN_PROGRESS jobs in the section Restart EBS and Macromedia JRun Services.
Revision Added a section containing information on checking the status of cleanup job that is scheduled the previous night.
Revision Added a section to verify the number of sub jobs for System.CleanupA job.
June 2008 Section Start-ofDay Operations Revision Added a new section to restart EBS and Macromedia JRun Default services as a part of daily start-of-day operations.
February 2008 Section Start-ofDay Operations Section Start-ofDay Operations Section Start-ofDay Operations Revision Added information on how to run Check_Backup_Status.bat batch file to check status of daily backup.
Revision Added a section on cleanup of the backup files.
Revision Updated information on Diag, Oracle Listener and Oracle Alert log files.
Revision Record
Section End-of-Day Operations
Revision Audit Reports can be generated through the Manual Reports screen and the Audit Report Generator utility will not be used henceforth.
January 2008 Section All Revision New publication
Revision Record
10
1
Start-of-Day Operations
At the start of each working day, you have to ensure that the system is in a good working state. This chapter details the activities and related procedures you have to perform at the beginning of the processing day for successful functioning of the system. Daily start-of-day operations include checking the following:

Status of backups Free space available on drives Size of log files Status of EBS, ORACLE, JRUN, Syslog and Media Manager services Restart of EBS and Macromedia JRun Default services Restart IBM Websphere Services Network and FTP connectivity Version of CHT and WCS file Status of Index Rebuild Status of the Backup Process Status of the Restore Process
11
Chapter 1: Start-of-Day Operations
Start-of-Day Operations
Verify size of log files Check status of EBS, ORACLE and JRUN, Syslog and Media M anager services
Start-ofDay Operations
Ensure available disk space
Check network and FTP connectivity
Verify status of backups
Check version of CHT and W CS file
12
Chapter 1: Start-of-Day Operations Check Status of Daily Backups
Check Status of Daily Backups

Check if the daily backup of the Oracle database has completed successfully. Transfer the backup from the disk to media or any other network storage. Check LEVEL 0/LEVEL 1 log files stored in C:\NCR\RMAN\log on the CHG server. Run the Check_Backup_Status.bat file.
To find the status of the last backup taken:
or
Note: Go to the next page to read the steps for executing Check_Backup_Status.bat file.
Check Daily Backups
S tart of d ay operation
C heck backup com pletio n
C heck L E V E L 0/ LEVEL 1 log file
R un C heck_B ackup_S tatus.bat
R etrieve backup status
Tip: To know more about LEVEL 0/ LEVEL 1 log files, refer to the Appendix section.
13
Run the Check_Backup_Status.bat

To run the batch file:
1
Go to your Desktop and check for the shortcut of Check_Backup_Status.bat file.
Check_Backup_Status.bat Shortcut
Double-click the Shortcut to Check_Backup_Status.bat icon.
14
Check for the status of backup in the html file that is displayed as the one shown below.
Backup Status
A Completed status indicates that the backup was completed successfully and Failed status indicates that the backup was unsuccessful.
Important: In case the backup has failed, contact your local support personnel.
15
Chapter 1: Start-of-Day Operations Monitor Free Space
Monitor Free Space

Verify that adequate free space is available on drives at application and database servers. Use the operating system utilities to monitor the system resources on the server.
1 2
Select Start > Settings > Control Panel > Administrative Tools. Check the amount of disk space available on each drive:
a b
Select Computer Management > Storage > Disk Management Select each drive in turn, and note the amount of free space on each drive.
Ensure that at least 3040 per cent free space is available on drives at application and database servers.
Monitor Disk Space
16
Chapter 1: Start-of-Day Operations Clean Physical Backup Files
Clean Physical Backup Files

Monitor the disk space on the drive for storing backup files. Everyday the backup files have to be moved to an alternate media and/or alternate location to free up the disc space.
Caution: If the disk space is full, the backup fails.
All backup files are stored at the following location: ..\bk01\<hostname>\ECPIX\LEVEL 0 or LEVEL 1 where hostname is a configurable parameter.
Backup Files
Cleanup of backup files is an automatic process and is performed daily at a pre-defined time. During cleanup, the previous day's backup files are deleted. Only LEVEL 0 backup is retained along with LEVEL 1 backup of Saturday.
17
The Cleanup matrix for backup files shown below outlines the timeline and the backup set required for system recovery (in case of failure).
Table 1-1: Cleanup Matrix for Backup Files
Days Sunday (D1) Monday (D2) Tuesday (D3) Wednesday (D4) Thursday (D5) Friday (D6) Saturday (D7)
Backup LEVEL 0 LEVEL 1 LEVEL 1 LEVEL 1 LEVEL 1 LEVEL 1 LEVEL 1
Backup Set to be Deleted NA Delete D2 Delete D3 Delete D4 Delete D5 -
Backup Set required to Recover the System LEVEL 0 D1 + D2 = A A + D3 = B B + D4 = C C + D5 = D D + D6 = E E + D7
As shown in this example:

LEVEL 1 backup files created on Tuesday until Friday are deleted. LEVEL 0 backup created on Sunday and incremental LEVEL 1 backup created on Saturday are retained.
Note: A new LEVEL 0 backup is taken on every Sunday.
18
Check the Status of Cleanup Jobs

The cleanup of the backup files is scheduled everyday at a pre-configured time. The data contained in each of these files is also deleted. System.CleanupA job carries out the cleanup activities. To view the status of the System.CleanupA job, go to the Job Monitor screen in your application. From the Go to drop-down menu, select Job Monitor.
Job Monitor screen
From the Job Monitor screen, ensure that the Job State of System.CleanupA job is DONE. The Job State as DONE indicates that the job has been performed successfully. This indicates that the cleanup activity scheduled for the previous night is successful.
Tip: Click the Refresh button to view the change in the Job Status of the existing jobs.
19
Chapter 1: Start-of-Day Operations Verify the Size of Log Files
Verify the Size of Log Files

You need to check for the excessive size of the following log files:

JRUN logs ECPIX Diag log Oracle Listener log Oracle Alert log and Trace files
JRUN Logs
Check for excessive size of default-out log in the JRun directory. If the size exceeds 50 MB:
1 2 3 4
Stop the JRun services. Rename the log based on date. Delete old logs in the directory which are older than two days from the current date. Start the JRun services.
Tip: Refer to the sections Stop Service and Start Service in this chapter to know how to stop and start JRun services.
Location of JRun logs: C:\JRun\logs (configurable parameter) Description: Contains information about the activities of JRun administration server, including a description and probable cause of error Format: Unformatted text messages that can be read using Notepad or another text editor
20
JRun Logs
21
ECPIX Diag Log

Check for excessive size of Diag log in the diag directory. If the size exceeds 25 MB:
Delete the old logs in the directory.
Location: D:\Program Files\NCR\ECPIX\diag (configurable parameter) Description: Contains information and the errors about the database connections, HTTP messages Format: Unformatted text messages that can be read using Notepad or another text editor
Diag Logs
Note: Delete the diag logs that are older than two days from the current date.
22
Oracle Listener Log

Check for excessive size of listener log in the log directory. If the size exceeds 10 MB, stop the TNSListener service.
Tip: Refer to the section Stop Service to read more on how to stop a service.
After stopping the TNSListener service, you can either rename the logs or delete them.
1
Rename the log based on date.

a b
Place the renamed file to some other directory. Start the TNSListener service which creates a new listener log file. Start the TNSListener service which creates a new listener log file.
Delete old logs in the directory based on the date.

a
Important: If the renamed log file is placed in the same location, Oracle continues to write to the same renamed file.
Location: D:\Oracle\Ora10g\NETWORK\log (configurable parameter) Description: Contains information about the activities of the listener service Format: Unformatted text messages that can be read using Notepad or another text editor
Listener Log
23
Oracle Alert Log and Trace Files

Check for excessive size of alert_ecpix log in the bdump directory. Check for excessive size of Trace files in udump, bdump, and cdump directories. Rename the log based on date. Delete old logs in the directory based on the date.
If the size of alert_ecpix exceeds 10 MB:

Important: When the alert log file is renamed, a new log file is created with the default alert log name. Oracle then writes any entry to this new log file.
Location: D:\Oracle\admin\ECPIX (configurable parameter) Description: Contains information about the activities of Oracle server, including a description and probable cause of error Format: Unformatted text messages that can be read using Notepad or another text editor
Oracle Alert Log
24
NRCryptoAPI Log
Check for excessive size of NRCryptoAPI log in the log directory. If the size of the NRCryptoAPI log exceeds 10 MB, stop the EBS service. For more information about starting and stopping a service, see the Appendix. After stopping the EBS service, you can either rename the logs or delete them.
Rename the log based on date.

a b Place the renamed file to some other directory. Start the EBS service which creates a new log file.
Delete old logs in the directory based on the date.
Start the EBS service which creates a new log file.
Important: If the renamed log file is placed in the same location, Oracle continues to write to the same renamed file.
25
Chapter 1: Start-of-Day Operations Check Status of EBS, Oracle, JRun, Syslog and Media Manager Services
Check Status of EBS, Oracle, JRun, Syslog and Media Manager Services
Check whether EBS, JRun, ECPIXMediaWriter and Syslog services are running on the application server. Check whether the various Oracle services are running on the database server. Macromedia JRun Admin Server Macromedia JRun Default Server EBS Oracle Services

You have to check the following services:

OracleServiceECPIX OracleOraHomeTNSListener
Syslog Service ECPIXMediaWriter
If you have RAC environment configured, then you need to check for the following services also.

OracleDBConsoleECPIX1 Oracle ProcessManager OracleObjectService OracleClusterVolumeService OracleCRService OracleJobSchedulerECPIX1
If the application and database reside on a single server, all the above services are located on the same server.
26
Start Service
To start a service:
1 2 3
Select Start > Settings > Control Panel > Administrative Tools > Services. Locate the service you wish to start in the list of services. Click the Start link shown on the top left corner of the screen.
Services
Contact your local support personnel if any of the services fail to start.
27
Stop Service
To stop a service:
1 2 3 4
Select Start > Settings > Control Panel > Administrative Tools > Services. Locate the service you wish to start in the list of services. Click the Stop link shown on the top left corner of the screen. Contact your support personnel if any of the services fail to stop.
Services
28
Chapter 1: Start-of-Day Operations Restart EBS and Macromedia JRun Services
Restart EBS and Macromedia JRun Services

Restart EBS and Macromedia JRun Default services on the application server. Follow the sequence listed below to restart these two services on all the application servers:
1 2 3 4
Stop EBS service. Stop Macromedia JRun Default Server service. Start Macromedia JRun Default Server service. Start EBS service.
Tip: Refer to the previous section to stop and start these services.
Restarting these services frees up memory resources. On restart, the EBS service also executes any previous jobs stuck in IN_PROGRESS state in the database. You can monitor the jobs which are in IN_PROGRESS state from the Job Monitor screen in your application. From the Go to drop-down menu, select Job Monitor.
Warning: Ensure that there are no jobs with the Job State as IN_PROGRESS, else contact your local support personnel.
29
Chapter 1: Start-of-Day Operations Restart IBM Websphere Services
Restart IBM Websphere Services

You must restart the IBM Websphere services on the application servers. To do this:
1
On the application server, click Start > All Programs > IBM Websphere > Application Server - Express v6.1 > Profiles > Name of Application Server profile > First Steps.
The system displays the Websphere Application Server - First steps dialog.
Click the Stop the server link on the First steps dialog.
First Steps dialog
The system stops the server and its related applications and displays the following output.
30
Stop IBM Services Output
The Websphere Application Server - First steps dialog now displays the Start the server link. 3
Click the Start the server link.
31
First steps dialog
The system starts the server and its related applications and displays the following output.
32
Start IBM Services Output
33
Chapter 1: Start-of-Day Operations Communicate Errors to Support Personnel
Communicate Errors to Support Personnel

Check for errors on System Monitor screen and address each error. These are system generated alerts, represented by a notification icon, and which require immediate action. Contact the CTS Helpdesk for any application errors such as:

ECPIX application cannot be accessed from the browser Recurring system errors on the System Monitor screen
For any other type of error, contact your local support personnel.
34
Chapter 1: Start-of-Day Operations Ensure Network and FTP Connectivity
Ensure Network and FTP Connectivity

Check for the FTP connectivity with the Clearing House and the capture system. If network connectivity with the capture system is not available, prepare to send/receive files to/from capture system via media. To check the network connectivity with the Clearing House:

Navigate to the Clearing House Processing Monitor screen. If the page is not displayed it indicates network failure with the Clearing House.
Network Failure screen
To check for the FTP connectivity with the Clearing House:
Connect to the CTS support FTP account using Ipswitch WS_FTP Professional software. Enter the server address of Clearing House. Enter your username and password to connect to it.
Note: To connect to the already configured FTP server, click the Connect button of the Ipswitch WS_FTP Professional software.
35
Chapter 1: Start-of-Day Operations Ensure Network and FTP Connectivity
Connection Wizard
Note: If FTP or network connectivity with the Clearing House is not available, coordinate with the Clearing House operations personnel for operating the CHG in Media mode.
36
Chapter 1: Start-of-Day Operations Check Version of CHT and WCS Files
Check Version of CHT and WCS Files

Check whether the version of the CHT and WCS files loaded at the CHG matches with the version available at the Clearing House.
Check Version of CHT

To check CHT file version:
1 2
Navigate to the Clearing Table screen. Verify that the version details mentioned for CHG at the top corner of the screen match with the Clearing House version. The version of the CHT file available at the Clearing House is displayed in the table. Compare the dates of your last retrieved version and current Clearing House version of the CHT file.
Clearing Table screen
4 5
To retrieve the current Clearing House version of the CHT file, click the Retrieve link. Navigate to the System Monitor screen and check for any errors related to the loading of the CHT file.
37
Contact your CTS support personnel, if required.
Important: If the Clearing House has issued a new CHT file, confirm that its corresponding CHM file has been created and shared with the capture system.
38
Check Version of WCS

To check WCS file version:
1 2
Navigate to the Working Certificate Set Management screen. Verify that the version details mentioned for CHG at the top corner of the screen match with the Clearing House version. The version of the WCS file available at the Clearing House is displayed in the table. Compare the dates of your last retrieved version and current Clearing House version of the WCS file.
Working Certificate Set Management screen
4 5 6
To retrieve the current Clearing House version of the WCS file, click the Retrieve link. Navigate to the System Monitor screen and check for any errors related to the loading of the WCS file. Contact your CTS support personnel, if required.
39
Chapter 1: Start-of-Day Operations Check Index Rebuild Status
Check Index Rebuild Status

To check if the index has been rebuild successfully on the ECPIX tables:
1
Browse to the D:\Program Files\NCR\ECPIX\Bin\AdminUtilities\INDEX_REBUILD_STATUS folder, where D:\ indicates the drive where the ECPIX application has been installed. Double-click the create.bat file.
The system generates the index.html file. This file displays the MAX_DATE and MIN_DATE of the index rebuild.
Verify that the MAX_DATE and MIN_DATE reflects the current date.
The following image displays a sample output of the index.html file.
If the MAX_DATE and MIN_DATE does not reflect the current date, you must perform the index rebuild process again.
Check Status of the Backup Process

The status of the backup process can be seen in the info_yyyy_mm_dd.log file present in the C:\DRData\Logs folder. yyyy_mm_dd indicates the date when the process was last executed. To check if the backup process has completed successfully, verify that text similar to the following exists in the file.
Information |7/8/2011 5:24:50 AM |Backup completed successfully. |DRBackup |SEP03VVM-900
Check Status of the Restore Process

The status of the restore process can be seen in the info_yyyy_mm_dd.log file present in the C:\DRData\Logs folder. yyyy_mm_dd indicates the date when the process was last executed. To check if the restore process has completed successfully, verify that text similar to the following exists in the file.
Information |10/19/2011 12:20:38 AM |Restore Successful |StartRestore |SEP03VVM-900-2
40
2
End-of-Day Operations
At the end of each processing day, you have to ensure that the days processing was successfully executed. This chapter details the activities and related procedures you have to perform each night for successful functioning of the system. Daily End-of-day operations include checking the following:
Successful generation of Posting files, Return files, Extension files, and End of Session files Receipt of OACK (Outward Acknowledgement) and Response files at the capture system Status of bundled items Successful generation of reports and its distribution to member banks, if applicable Sufficient disk space available for backup Any system errors Verify the count of sub jobs for System.CleanupA job
You also have to coordinate with the members of the Clearing House for any changes to be done to the Clearing Tables or to change the transmission status of the CHG.
41
Chapter 2: End-of-Day Operations
End-of-Day Operations
V e r ify g e n e r a tio n o f p o s tin g , r e tu r n , e x te n s io n a n d e n d o f s e s s io n file s V e r ify r e c e ip t o f o u tw a r d a c k n o w le d g e m e n t a n d r e s p o n s e file s
ID C
C a p tu r e S y s te m
E n d - o fDay O p e r a tio n s
E n s u r e a v a ila b le d is k s p a c e
C h e c k fo r S y s te m e r r o r s
P a y to
S y s te m .C le a n u p A jo b
V e r ify g e n e r a tio n o f r e p o r ts
V e r ify c o u n t o f s u b jo b s
C h e c k s ta tu s o f b u n d le d ite m s
42
Chapter 2: End-of-Day Operations Check Successful Generation of PXF, RF, EF, and .eos Files
Check Successful Generation of PXF, RF, EF, and .eos Files

Verify that Posting files (PXF), Return files (RF), Extension files (EF), and End of Session files (.eos) have been generated for all your member banks for all sessions for the day. If any file has not been generated:
1
Navigate to the System Monitor screen.

a b
Check for any related errors. Respond to errors as required.
System Monitor screen
Contact your support personnel.
43
Verify Generation of Posting Files and Return Files on Application Screen

To verify the generation of posting files:
1 2
Navigate to the Inward Exchange Files screen. Verify that the number of files under Total Files column match the number under the Complete status of File Status Summary column.
Inward Exchange Files screen
Note: Only the status of Posting Files generated are viewable from the application screen. Other files like EF and .eos can be viewed from their respective directories on the hard disk.
44
Verify Generation of PXF, RF and EF on Hard Disk

You can also access the physical posting, return, and extension files from a pre-defined directory where they are stored after being successfully generated. This directory is accessible to both the ECPIX CHG as well as the Inclearing systems.
Table 2-1: Location of Posting, Return and Extension Files
Type of File Master Posting Files (MPXF) Master Return Files (MRF) Master Extension Files (MEF) Bank Posting Files (BPXF) Bank Return Files (BRF) Bank Extension Files (BEF) Branch Posting Files (BrPXF) Branch Return Files (BrRF) Branch Extension Files (BrEF)
Location ...\FTPRoot\CHG Routing Number
...\FTPRoot\CHG Routing Number\Bank Routing Number
...\FTPRoot\CHG Routing Number\Bank Routing Number\Branch Routing Number
Important: FTPRoot folder can be located on any of the drives. The location is a configurable parameter.
Verify Generation of .eos File

.eos files are created for every session in the same folder location as the PXFs and RFs. The presence of this files indicates that the CHG has created all inward files for a session.
45
Chapter 2: End-of-Day Operations Confirm Receipt of OACK and Response Files at the Capture System
Confirm Receipt of OACK and Response Files at the Capture System

Verify that your banks capture system has received Response file and OACK files for all Capture files (CXF) and Return Request Files (RRF) presented for the day. If no response file or OACK file is generated for any CXF or RRF submitted by the banks capture system:
1
Navigate to the System Monitor screen.

a b
Check for any related errors. Respond to errors as required. Check for any bundles (originally to be sent to the Clearing House for the ended session) are still in an Awaiting Session status.
Navigate to the Bundle Monitor screen.

a
Contact your support personnel, if required.
46
Chapter 2: End-of-Day Operations Check Bundle Status
Check Bundle Status

Navigate to the Bundle Monitor screen. Verify that all bundles have been attached to a session. If any bundle is awaiting session, based on your business requirement, you can either keep it in this mode, or reject it back to the capture system. To reject a bundle:
1 2 3
Navigate to the Bundle Monitor screen. Select the bundles having Awaiting Session status. Click the Delete button.
The bundles are removed from this screen, and response files are created per bundles per CXF, and sent to the capture system.
Note: Bundles having Awaiting Session status are automatically attached to a relevant open session on the next business day.
47
Chapter 2: End-of-Day Operations Verify Session and Daily Reports are Generated
Verify Session and Daily Reports are Generated

Navigate to the Reports screen. Verify that all session and daily reports for the day are successfully generated.
Verify Session Reports

To view reports for a session:
1 2 3 4 5
Navigate to the Reports screen. Select Session option under Report Type. Select the Session No. for which you want to view the reports. Select the Session Date. Click the GO button.
Session Reports screen
48
6 7 8 9
Ensure that all reports for this session are in Generated status. Download these reports and store at an appropriate location or copy on media. Click the Refresh button to refresh the status of reports still In Progress. Repeat Steps 3 to 5 for viewing the reports status of other sessions of the day.
49
Verify Daily Reports

To view daily reports:
1 2 3
Navigate to the Reports screen. Select Daily option under Report Type. Select the institution and click the GO button.
Daily Reports screen
4 5 6
Ensure that all daily reports are in Generated status. Download these reports and store at an appropriate location or copy on media. For any reports having Generation Error, click View Error Details link, and take appropriate action.
!
*
Important: Distribute the daily and session reports to your indirect or sub-member banks. Tip: Refer to the book B004-0000-0415: Clearing House Gateway Operations to view the complete list of Session and Daily reports.
50
Chapter 2: End-of-Day Operations Generate Audit Reports
Generate Audit Reports

Your end-of-day maintenance also includes generating the audit reports through the Manual Reports screen. Audit reports are generated based on certain key parameters selected from the Manual reports screen. For example, a report can be generated for a specific period based on your business requirements. You can create four audit reports that provide audit trials of system events. To generate audit reports:
1 2 3
Navigate to the Reports screen from the Go to drop-down menu. Select Manual option under Report Type on the Reports screen. Specify the appropriate report parameters for generating the particular audit report.
Manual Reports screen
51
Chapter 2: End-of-Day Operations Generate Audit Reports
4 5
Click the Generate Report button on the Report Parameter screen. Repeat this procedure for each audit report you wish to generate.
Tip: Refer to the book B004-0000-0415: Clearing House Gateway Operations to get detailed information on the various Audit Reports.
52
Chapter 2: End-of-Day Operations Check Available Disk Space for Backup
Check Available Disk Space for Backup

Verify that the disk for taking backup has sufficient space available so that scheduled backup for the day can run successfully. In case of weekends, verify that there is sufficient space to hold Level 0 backup for Sunday and Level 1 backup for Monday. Ensure that at least 3040 per cent free space is available on drives at application and database servers.
53
Chapter 2: End-of-Day Operations Respond to System Errors
Respond to System Errors

Check for errors on System Monitor screen and address each error. These are system generated alerts, represented by a notification icon, and which require immediate action. To respond to system errors:
1
Double click the notification icon.
The System Monitor screen is displayed listing the descriptions of all exceptions raised by the system.
System Monitor screen
2 3 4
To view details of a particular exception raised by the system, click the View link in the Action Required column. After viewing the details, perform the necessary action to rectify the exception. Contact the CTS Helpdesk in case of any recurring errors.
54
Chapter 2: End-of-Day Operations Communicate with the Clearing House
Communicate with the Clearing House

You will have to coordinate with the members of the Clearing House to execute any of the following:

Change mode of file transmission Block Bank or a Branch Generate Extension for an Item Any changes to be done in the Clearing Tables
Inform the Clearing House Operations personnel for any changes such as new branch additions etc. to be done in the Clearing Table for banks operating under your CHG. Coordinate with the Clearing House Operations personnel to change the file transmission type from Media to Electronic Transmission or vice-versa if you have a business requirement for the subsequent working day. If inward items are not processed by the capture system, you may have to communicate to the Clearing House Operations personnel to block the bank or branch, or generate extensions if required.
55
Chapter 2: End-of-Day Operations Verify the Count of Sub Jobs for System.CleanupA Job
Verify the Count of Sub Jobs for System.CleanupA Job

To verify the job count of System.CleanupA job, from the Go to drop-down menu, select Job Monitor.
Job Monitor screen
The Job Monitor screen lists the current jobs that are being performed alongwith their statuses. Verify that the number under Count column is 18 for System.CleanupA job. The Count column displays the number of sub-jobs for a job. Click the link under Count column to view the details of the sub-jobs.
56
A
Appendix
This appendix covers technical terms and details out certain procedures mentioned throughout the document.
ImageMark ECPIX 4.4 - Clearing House - Start and End of Day Operations
57
Appendix A: Appendix LEVEL 0/LEVEL 1 Log Files
LEVEL 0/LEVEL 1 Log Files

LEVEL 0 and LEVEL 1 log files contain information about the database backup as well as
remote file transfer information. They are placed in the ..NCR\RMAN\LOG directory. For each of the log file, two types of log files are generated:

Information log file Error log file
In LEVEL 0 backup, RMAN takes full database backup. It is used as a parent backup for LEVEL 1 backup and must be available before starting higher level backup. In LEVEL 1 backup, RMAN takes only the effected changes (incremental changes) after parent backup.
LEVEL 0
LEVEL 0 means full database backup, which runs every Sunday as per schedule. It
generates two different log filesLEVEL0.log and LEVEL0.err.log.
LEVEL0.logcontains information for successful completion of backup. It stores information like backup completion time and list of all data files whose backup is taken. LEVEL0.err.logcontains information for any backup error.
58
Appendix A: Appendix LEVEL 0/LEVEL 1 Log Files
LEVEL 1
LEVEL 1 means incremental database backup which runs everyday as per schedule. It
generates two different log filesLEVEL1.log and LEVEL1.err.log.
LEVEL1.logstores information like backup completion time, list of all data files whose backup is taken. LEVEL1.err.logstores information if the backup or the upload of the files fail.
LEVEL 0 and LEVEL 1 Files
59
Appendix A: Appendix RMAN
RMAN
RMAN (Recovery Manager) is a utility provided by Oracle that manages the entire database backup and recovery activities. The RMAN processes are background processes that are started on the server and communicates between RMAN and the database. The biggest advantage of RMAN is that it will only backup used space in the database.
60
Index
Symbols
.eos file 45
F
Free space 16
A
Appendix 57, 60 Audit Report Generate Audit Reports 51
I
Ipswitch WS_FTP Professional software 35
L B
Backups 13, 53 Check_Backup_Status.bat 1314 Clean Physical Backup Files 17 LEVEL 0 13, 1718 LEVEL 1 13, 1718 log files 20 Diag Log 22 JRUN Logs 20 Level 0 58 Level 1 59 Oracle Listener Log 23 Oracle Trace files and Alert Log 24
C
Check generation of PXF, RF, EF, and .eos Files 43 CHT file 37 Clearing House Operations personnel 55
N
Network and FTP connectivity 35
O E
End-of-day operations 41 OACK and Response files 46
61
Index
R
Reports 48 Daily Reports 50 Session Reports 48 RMAN 60
S
Services 26 Start a Service 27 services Stop 60 Start-of-Day Operations 11 Support Personnel 34, 3839, 43 System Errors 54
W
WCS file 11, 37, 39
62
B004-0000-0742
October 28, 2011

W742 2011oct28 SOD CHG

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

W742 2011oct28 SOD CHG

Încărcat de

Drepturi de autor:

Formate disponibile

ImageMark ECPIX 4.

Clearing House Gateway- Start and End of Day Operations

B004-0000-0742 October 2011

Revision Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Chapter 1: Start-of-Day Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2: End-of-Day Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Clearing House Gateway (CHG) Operations Personnel

Notes, Tips, Important, Cautions, Warnings

Revision Added a section on cleanup of the backup files.

Section End-of-Day Operations

January 2008 Section All Revision New publication

Chapter 1: Start-of-Day Operations

Ensure available disk space

Check network and FTP connectivity

Verify status of backups

Check version of CHT and W CS file

Chapter 1: Start-of-Day Operations Check Status of Daily Backups

Check Status of Daily Backups

To find the status of the last backup taken:

C heck backup com pletio n

C heck L E V E L 0/ LEVEL 1 log file

R un C heck_B ackup_S tatus.bat

R etrieve backup status

Chapter 1: Start-of-Day Operations Check Status of Daily Backups

Run the Check_Backup_Status.bat

Go to your Desktop and check for the shortcut of Check_Backup_Status.bat file.

Double-click the Shortcut to Check_Backup_Status.bat icon.

Chapter 1: Start-of-Day Operations Check Status of Daily Backups

Chapter 1: Start-of-Day Operations Monitor Free Space

Monitor Free Space

Chapter 1: Start-of-Day Operations Clean Physical Backup Files

Clean Physical Backup Files

Chapter 1: Start-of-Day Operations Clean Physical Backup Files

Backup LEVEL 0 LEVEL 1 LEVEL 1 LEVEL 1 LEVEL 1 LEVEL 1 LEVEL 1

Backup Set to be Deleted NA Delete D2 Delete D3 Delete D4 Delete D5 -

Backup Set required to Recover the System LEVEL 0 D1 + D2 = A A + D3 = B B + D4 = C C + D5 = D D + D6 = E E + D7

As shown in this example:

Note: A new LEVEL 0 backup is taken on every Sunday.

Chapter 1: Start-of-Day Operations Clean Physical Backup Files

Check the Status of Cleanup Jobs

Chapter 1: Start-of-Day Operations Verify the Size of Log Files

Verify the Size of Log Files

Chapter 1: Start-of-Day Operations Verify the Size of Log Files

Chapter 1: Start-of-Day Operations Verify the Size of Log Files

ECPIX Diag Log

Delete the old logs in the directory.

Chapter 1: Start-of-Day Operations Verify the Size of Log Files

Oracle Listener Log

Rename the log based on date.

Delete old logs in the directory based on the date.

Chapter 1: Start-of-Day Operations Verify the Size of Log Files

Oracle Alert Log and Trace Files

If the size of alert_ecpix exceeds 10 MB:

Chapter 1: Start-of-Day Operations Verify the Size of Log Files

Rename the log based on date.

Delete old logs in the directory based on the date.

Start the EBS service which creates a new log file.

You have to check the following services:

Syslog Service ECPIXMediaWriter

OracleDBConsoleECPIX1 Oracle ProcessManager OracleObjectService OracleClusterVolumeService OracleCRService OracleJobSchedulerECPIX1

Chapter 1: Start-of-Day Operations Restart EBS and Macromedia JRun Services

Restart EBS and Macromedia JRun Services

Chapter 1: Start-of-Day Operations Restart IBM Websphere Services