Preface
Installation Overview
- Introduction
- Data Archive Installation
- Data Vault Installation
- Component Selection
- Application Accelerator Installation
- Dynamic Data Masking Installation
  - Enabling Dynamic Data Masking
Before You Install
- License Key
- X Window Server
- Data Archive Requirements for the ILM Repository
  - ILM Repository User
- Data Archive Requirements for the ILM Engine
- Data Vault Requirements
Data Archive Installation
- Data Archive Installation Overview
  - Installation Package
- Installing Data Archive Components
- Graphical Mode Installation
- Console Mode Installation
- Silent Mode Installation
  - Silent Mode Installation Properties
  - Installing in Silent Mode
- Informatica Data Archive Profiling Installation
Data Vault Installation
- Data Vault Installation Overview
- Graphical Mode Installation
- Console Mode Installation
- Silent Mode Installation
  - Step 1. Create the Properties File
  - Step 2. Run the Silent Installer
Application Accelerator Installation
- Application Accelerator Installation Overview
- Installing the Application Accelerators in Graphical Mode
- Installing the Application Accelerators in Console Mode
Application Retirement for Healthcare Accelerator Installation
- Application Retirement for Healthcare Accelerator Installation Overview
- Prerequisites
- Installing the Accelerator in Graphical Mode
- Installing the Accelerator in Console Mode
- After You Install
MongoDB Accelerator Installation
- MongoDB Accelerator Installation Overview
- Installing the MongoDB Accelerator in Graphical Mode
- Installing the MongoDB Accelerator in Console Mode
- After You Install
Salesforce Accelerator Installation
- Salesforce Accelerator Installation Overview
- Installing the Accelerator in Graphical Mode
- Installing the Accelerator in Console Mode
- After You Install
After You Install
- Client Machine Requirements
- Starting the ILM Application Server
  - Logging In to Data Archive
- Starting the Data Vault Components
- Configuring Memory Settings on a 64-bit Computer
- Configuring Embedded Tomcat for HTTPS
- Registering Services as Windows Services
  - Registering the Archive Service
  - Registering the Data Vault Service for External Attachments
- Configuring Data Archive
- Setting up SAP Retirement
Data Archive Upgrade
- Data Archive Upgrade Overview
- Before You Upgrade
- Upgrading Data Archive in Graphical Mode
- Upgrading Data Archive in Console Mode
- Upgrading Data Archive in Silent Mode
- After You Upgrade Data Archive
- Reverting to a Previous Version
Data Vault Upgrade
- Data Vault Upgrade Overview
- Before You Upgrade a Data Vault Component
- Upgrading in Graphical Mode
- Upgrading in Console Mode
- Upgrading in Silent Mode
  - Step 1. Create the Properties File
  - Step 2. Run the Silent Installer
- Troubleshooting Data Vault Upgrade
- After You Upgrade
- Reverting an Upgrade
Upgrading Oracle History Data
- Upgrading Oracle History Data Overview
- Upgrading Oracle History Data Prerequisites
- Steps to Upgrade the History Data
- Step 1. Run the History Upgrade Scripts
  - History Upgrade Scripts Parameters
  - Running the History Upgrade Scripts
- Step 2. Run the Create History Table Job with the Original Source
  - Running the Create History Table Job
- Step 3. Update the Application Version for Source and Target Connections
  - Updating the Application Version for Source and Target Connections
- Step 4. Run the Create History Table Job with the Updated Source
  - Running the Create History Table Job
- Step 5. Run the Seamless Data Access Job for the Updated Source
  - Running the Seamless Data Access Job
- Step 6. Run the Create Indexes Job
  - Running the Create Indexes Job
- Step 7. Gather Database Statistics
Upgrading PeopleSoft History Data
- Upgrading PeopleSoft History Data Overview
- Upgrading PeopleSoft History Data Prerequisites
- Steps to Upgrade the History Data
- Step 1. Run the History Upgrade Scripts
  - Running the History Upgrade Scripts
    - Original Application Changes Script Example
    - Updated Application Changes Script Example
- Step 2. Run the Create History Table Job with the Original Source
  - Running the Create History Table Job
- Step 3. Update the Application Version for Source and Target Connections
  - Updating the Application Version for Source and Target Connections
- Step 4. Run the Create History Table Job with the Updated Source
  - Running the Create History Table Job
- Step 5. Run the Seamless Data Access Job for the Updated Source
  - Running the Seamless Data Access Job
- Step 6. Run the Create Indexes Job
  - Running the Create Indexes Job
- Step 7. Gather Database Statistics
ILM Data Validation Option Setup
- ILM Data Validation Option Setup Overview
- Before You Set Up the ILM Data Validation Option
- Install the Data Vault Service ODBC Driver
  - Installing the Data Vault ODBC Driver in Graphical Mode
  - Installing the Data Vault ODBC Driver in Console Mode
- Create a Data Vault Service ODBC Data Source
  - Creating an ODBC Data Source on Windows
    - Using the Windows ODBC Data Source Administrator to Create a Data Source
    - Data Vault ODBC Data Source Parameters
  - Creating an ODBC Data Source on UNIX
- Create a PowerCenter Connection Object
- After You Set Up the ILM Data Validation Option
Data Archive Source and Target Database Requirements
- Source Database Requirements
- Target Database Requirements
Data Archive Connectivity
- Data Archive Connectivity Overview
- Native Connectivity
- DataDirect Connect JDBC Connectivity
- PowerExchange Connectivity
- Third-Party JDBC Connectivity
Data Archive Uninstallation
- Data Archive Uninstallation Overview
- Restore Archived Data
- Dropping Database Users and Links
- Dropping the ILM Repository
- Deleting the ILM Application Server Directory
- Uninstalling the Data Vault
- Uninstalling Source Adapters
- Deleting Remaining ILM Files
SAP Application Retirement
- SAP Application Retirement Overview
- SAP Application Retirement Architecture Options
- Setting Up SAP Application Retirement
- Step 1. Install the SAP Java Connector
- Step 2. Apply the SAP Transports
- Step 3. Assign Roles
- Step 4. Configure Conf.Properties
- Step 5: Set up the FTP or NFS Connection
  - Creating the FTP Connection
  - Creating the NFS Mount
Database Users and Privileges
- Database Users and Privileges Overview
- Administration User
- Production Application User
- Staging User
- History Read-Only User
- History Application User
- Combined User and Archive User for Seamless Access
- System User (Smart Partitioning)
- IBM DB2 Privileges
  - Bind Packages Privileges
  - Login User Privileges
- SAP Application Retirement Privileges
  - ZINFA_RETIREMENT_PREPARATION Role
Data Visualization Designer Installation
- Data Visualization Designer System Requirements
- Installing Data Visualization Designer
Data Archive Installation Requirements Checklist and Architecture Options
- Pre-Installation Requirements Overview
- Archive to a Database Checklists
- Archive or Retire to Data Vault Checklists
- Smart Partitioning Source Data Checklists
- Data Archive Options Installation Checklist
  - SAP Retirement Installation Checklist
- Data Archive Architecture Recommendations

Installation and Upgrade Guide

6.5 HotFix 1
- 6.5.1
- 6.5

Back Next

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.

Rename Saved Search

Table of Contents

Installation and Upgrade Guide

Installation and Upgrade Guide

Startup Configuration Parameters

Startup Configuration Parameters