Table of Contents

Search

  1. Preface
  2. Backing Up and Restoring the Data Vault
  3. Configuring Centera as a Remote Data Vault Store
  4. Configuring Data Archive for a Legacy Source Using Legacy Adapters
  5. Data Archive Seamless Access for PeopleSoft
  6. Data Archive Transaction Restore API
  7. Dropping and Truncating Partitions in Data Archive
  8. How to Create Business Rules to Archive and Purge Transactional Data
  9. How to Uninstall Data Archive 5.1
  10. How to Uninstall Data Archive 5.3
  11. How to Use Scripts to Change Database User Passwords in the ILM Repository
  12. IBM DB2 Database Connectivity and Setup for Data Archive
  13. Installing Data Visualization
  14. Integrating Third-Party Schedulers in ILM Engine
  15. Parallel Processing in Data Archive
  16. Seamless Access Configuration for Siebel Applications
  17. Seamless Access Setup for Oracle E-Business Suite
  18. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  19. Using Multiple Engines in an ILM Environment
  20. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  21. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To Guide

Keeping Track of Tomcat Engines

Keeping Track of Tomcat Engines

Keep track of which instance runs each job, in case you later need to view the logs or to troubleshoot or resume a job.
To keep track of the instances, follow these best practices:
  • In ILM 5.3.3 and previous versions, incorporate the instance in the project name to associate the job with the instance. For example, use a project name such as AR_ACME_PROD1 where PROD1 is the instance that the job is running on.
    Effective in ILM 5.3.4, use the informia.appendHostAndPortInLog parameter in the conf.properties file to identify the host name and port number of the instance where the job is running. Edit the conf.properties file for each instance and set the parameter to informia.appendHostAndPortInLog=Y. ILM appends the host name and port number to the timestamps in the logs. The configuration applies to all Data Archive, Data Masking, and Data Subset jobs and all standalone jobs.
  • To see which instance has the least load for a new job, go to each instance and check the Thread Queue Manager. The queue manager can be found at http://URL:port/jsp/tqm.jsp. This page shows you how many threads are running and pending for each instance. You can pick the least active instance to begin the new job.
    The following is an example of the tqm.jsp output:
    Thread Status ThreadId=86 ThreadName=SCHEDULEJOB$86$174_WYETHIDR_IDR_201011 174_WYETHIDR_IDR_201011 Status=Running GroupId=SCHEDULEJOB$86 ParentIds=null Priority=1 ThreadId=148 ThreadName=JOBSTEP$148$Copy To Destination Status=Running GroupId=JOB$86 ParentIds=null Priority=0 ThreadId=33906 ThreadName=33$RES_FACT$FLAT_FILE Status=Running GroupId=STEP$148 ParentIds=null Priority=1 ThreadId=33914 ThreadName=33$SAMP_BRIDGE$FLAT_FILE Status=Running GroupId=STEP$148 ParentIds=null Priority=1
    Each thread that has "status=Running" will count against the total thread count allocated through the amMaxServerThreads parameter. For example, if you have the parameter set to 30, then, for this instance, 27 threads are left for other processes.
    The best instance to start a new job is one where the tqm.jsp returns the following status:
    Thread Status No threads in queue
    Effective in ILM 5.3.4, if you set informia.appendHostAndPortInLog parameter=Y to append the host name and port number to the logs, the job logs in View Current Jobs indicate what instance a job is running on. Using this information, you can open the job log for any process in a running state to see which engine has the heaviest load and which one has the lightest load.