Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Archive 6.5.1
  • All Products

Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Before You Install
  4. Data Archive Installation
  5. Data Vault Installation
  6. Application Accelerator Installation
  7. Application Retirement for Healthcare Accelerator Installation
  8. MongoDB Accelerator Installation
  9. Salesforce Accelerator Installation
  10. After You Install
  11. Data Archive Upgrade
  12. Data Vault Upgrade
  13. ILM Data Validation Option Setup
  14. Data Archive Source and Target Database Requirements
  15. Data Archive Connectivity
  16. Data Archive Uninstallation
  17. SAP Application Retirement
  18. Appendix A: Database Users and Privileges
  19. Appendix B: Data Visualization Designer Installation
  20. Appendix C: Data Archive Installation Requirements Checklist and Architecture Options

Installation and Upgrade Guide

Installation and Upgrade Guide

Back Next

Startup Configuration Parameters

Startup Configuration Parameters

The ssa_starter startup program uses configuration settings in the [STARTER] section of the ssa.ini file.
The following table describes the parameters used by the startup service:
Parameter
Description
SERVER_CMD
The command to start the Data Vault Service. Default is ssaserver.
AGENT_CMD
The command to start the Data Vault Agent. Default is ssaagent. Do not include the -u parameter to specify a numeric ID for the agent process. The startup service assigns an agent ID.
AGENT_COUNT
The number of Data Vault Agents processes to start. Default is 2.
LOGDIR
The directory where the log files will be written. On UNIX, the daemon log is named ssa_starter. On Windows the service activities are logged by the operating system, which can be viewed through the Event Viewer.
AGENT_CONTROL
Enables (1) or disables (0) automatic restart if the Data Vault Agent fails. Default is 1.
SERVER_CONTROL
Enables (1) or disables (0) automatic restart if the Data Vault Service fails. Default is 1.
USER
UNIX only. The user ID under which all processes will be started by the ssa_starter daemon. It is usually important to set this parameter, since the default is the root user, which can cause problems. For example, if a process running as root creates a file, only another root process can access that file.
This parameter can also be set using the SSA_STARTER_USER environment variable. If both the ssa.ini file and the environment variable define the user ID, the environment variable takes precedence.
VERBOSE
The level of detail for the messages written to the log files. The following are the possible options:
  • 0 : Includes all error messages and the most important messages
  • 1 : Level 0 plus more detailed messages
  • 2 : Level 1 plus system trace information
Default is 2.
EXE[0-9]
These 10 optional parameters (EXE0, EXE1, EXE2, ..., EXE9) refer to custom commands, scripts, or executables that will run in conjunction with Data Vault Service on startup. Note that the numbering of the parameters has no relationship to the order in which they are processed. These parameters are run asynchronously, so there is no guarantee about the execution order.
The ssa_starter program reads the [STARTER] section in the ssa.ini file to determine the settings at initialization. The [STARTER] section in the ssa.ini file must specify at least the following parameters:
  • SERVER_CMD. Contains the command to start the Data Vault Service.
  • AGENT_CMD. Contains the command to start the Data Vault Agent.
The AGENT_COUNT parameter indicates the number of agents to start and must be set to a value of 1 or higher, otherwise no agent will be started.
The AUTOSTARTUP parameter must be set to 1 (enabled) in the [META] section of the ssa.ini file so that the startup service or daemon works properly. This allows the startup service to start the Data Vault repository database before the Data Vault Service. A related parameter, STARTUPCOMMAND, which defines the command line for starting the Data Vault repository database, must also be configured in the same section of the ssa.ini file. If the Data Vault repository database is not on the local machine, the STARTUPHOST parameter must specify the name of the remote computer where the Data Vault repository database is located.
If the Data Vault server shuts down unexpectedly, enabling AUTOSTARTUP might prevent it from restarting. This is because after a server shuts down unexpectedly, the child metadata process remains running, so that the port is busy.
To prevent this behavior, you can also manage the metadata server with ssa_starter and the EXE commands. If you do not enable AUTOSTARTUP, you must add the following EXE parameters in the [STARTER] section of the ssa.ini file:
For UNIX:
EXE0=fb_inet_server -m
EXE0_CONTROL=1
For Microsoft Windows:
EXE0=fb_inet_server -a
EXE0_CONTROL=1
These parameters allow ssa_starter to manage the metadata server process when the AUTOSTARTUP option is set to 0. The name of the metadata server process is
fb_inet_server.exe
. Formerly, this process, which runs on the application server, was called
ssaeng.exe
 on Microsoft Windows and
ssaeng
on Linux.
On UNIX, if any changes are made in the ssa.ini file to parameters related to the Data Vault Service daemon, ssa_starter can be made to read the changes in the ssa.ini file using the ssa_starter -s command. On Windows, the service can be made to re-read the configuration by stopping, then restarting the service.
0 COMMENTS
We’d like to hear from you!