Table of Contents

Search

  1. Preface
  2. Data Replication Overview
  3. Understanding Data Replication
  4. Sources - Preparation and Replication Considerations
  5. Targets - Preparation and Replication Considerations
  6. Starting the Server Manager
  7. Getting Started with the Data Replication Console
  8. Defining and Managing Server Manager Main Servers and Subservers
  9. Creating and Managing User Accounts
  10. Creating and Managing Connections
  11. Creating Replication Configurations
  12. Materializing Targets with InitialSync
  13. Scheduling and Running Replication Tasks
  14. Implementing Advanced Replication Topologies
  15. Monitoring Data Replication
  16. Managing Replication Configurations
  17. Handling Replication Environment Changes and Failures
  18. Troubleshooting
  19. Data Replication Files and Subdirectories
  20. Data Replication Runtime Parameters
  21. Command Line Parameters for Data Replication Components
  22. Updating Configurations in the Replication Configuration CLI
  23. DDL Statements for Manually Creating Recovery Tables
  24. Sample Scripts for Enabling or Disabling SQL Server Change Data Capture
  25. Glossary

Command Line Parameters for the Server Manager

Command Line Parameters for the Server Manager

You can run the Server Manager executable or script from the command line with the following optional parameters:
CLEAN
Deletes all data from the Server Manager SQLite repository, SM.db3, including server properties, connections, schedules, tasks, and other server settings.
Do not use the
clean
parameter in combination with other parameters.
DBFILE="
file_name
"
Overrides the name of the internal SQLite repository file that the Server Manager uses for storing configuration file and internal service information.
DBSYNC_HOME=
path
Overrides the DBSYNC_HOME environment variable value for a Server Manager instance. Use this option for debugging purposes or when you run multiple Server Manager instances from different DBSYNC_HOME locations on the same system.
DEBUG
Runs the Server Manager in debug mode. Use this parameter only at the request of Informatica Global Customer Support.
DESC="
service_description
"
If you run the Server Manager as a service on Windows, optionally specify a description for the Server Manager service. Also see the RUN_AS_SERVICE parameter.
HELP
Displays a list of Server Manager parameters on screen.
Do not use the
help
parameter in combination with other parameters.
HTTP={0|
1
}
Indicates whether to use HTTP connections for the Server Manager. Options are:
  • 0
    . Do not use HTTP connections.
  • 1
    . Use HTTP connections.
If you do not specify the HTTP parameter or HTTPS parameter, when you start the Server Manager for the first time, it uses the default value of 1 to use HTTP connections. When you later start the Server Manager again, it uses the value from the preceding run.
Default value:
1
HTTPS={
0
|1}
Indicates whether to use HTTPS connections for the Server Manager. Options are:
  • 0
    . Do not use HTTPS connections.
  • 1
    . Use HTTPS connections.
If you do not specify the HTTPS parameter or HTTP parameter, when you start the Server Manager for the first time, it uses the default value of 1 for the HTTP parameter so that HTTP connections are used. When you later start the Server Manager again, it uses the value from the preceding run.
Default value:
0
HTTPS_PORT=
nnnn
If you set the HTTPS parameter to 1, use this parameter to override the default listener port through which a client submits HTTPS requests to the Server Manager. Valid values are integers from 1 through 65535.
Default value:
8089
If you run a Server Manager subserver later with a different port number, change the port number in the Data Replication Console on the
Server Manager
tab >
Servers
view.
INSTANCE="
server_name
"
If you run the Server Manager as a service on Windows or as a daemon on Linux or UNIX, optionally specify a name for the Server Manager instance that overrides the default name. Use this option if you run multiple Server Manager instances from different DBSYNC_HOME locations on the same system.
JOURNAL_MODE={DELETE|TRUNCATE|PERSIST|MEMORY|WAL|OFF}
Specifies the rollback journal mode for the SQLite repository that contains configuration information. Journal mode options are:
  • DELETE
    . Deletes the rollback journal at the conclusion of each transaction.
  • TRUNCATE
    . Commits transactions by truncating the rollback journal to zero length instead of deleting it.
  • PERSIST
    . Prevents the rollback journal from being deleted at the end of each transaction.
  • MEMORY
    . Stores the rollback journal in volatile RAM.
  • WAL
    . Uses a write-ahead log instead of a rollback journal to implement transactions.
  • OFF
    . Disables the rollback journal completely.
For more information about SQLite journal modes, see the SQLite documentation.
Default value:
DELETE for Linux and UNIX, WAL for Windows
Ensure that this parameter has the same value for all Data Replication components.
PORT=
nnnn
If the HTTP parameter is set to 1, overrides the default listener port through which a client submits HTTP requests to the Server Manager. Valid values are integers from 1 through 65535.
Default value:
8088
If you run a Server Manager subserver later with a different port number, change the port number in the Data Replication Console on the
Server Manager
tab >
Servers
view.
RESET_IDRADMIN
Resets the password for the idradmin account to empty. This parameter also unlocks the idradmin account if the account is locked out after the maximum number of failed login attempts that is specified in the MaxLoginAttempts property is reached.
Do not use the
RESET_IDRADMIN
parameter in combination with other Server Manager command-line parameters.
RUN_AS_SERVICE {-i|-r|-s|-k|-d}
On Windows, enter the RUN_AS_SERVICE parameter with one of the following options to install, start, or manage the Server Manager as a service:
  • -i
    . Installs the server_manager program as a service but does not start it.
  • -r
    . Removes the server_manager service from the Service Manager.
  • -s
    . Starts the server_manager service.
  • -k
    . Stops the server_manager service.
  • -d
    . Runs the server_manager service in debug mode.
On Linux and UNIX, you do not need to use this parameter to start the daemon. The server_manager.sh script runs the Server Manager with the RUN_AS_SERVICE parameter by default.
START
On Linux and UNIX, starts the Server Manager instance.
If you run the server_manager.sh script without the
start
parameter, the script still starts the Server Manager instance by default. However, Informatica recommends that you include the
start
parameter to clearly indicate intent.
STATE={
0
|1|2}
Determines whether to start a Server Manager instance as a Main server or a subserver. Options are:
  • 0
    . Start the Server Manager without a predefined role. Data Replication assigns a role to the Server Manager instance the first time you perform one of the following actions in the Data Replication Console: connect to the Server Manager or add it as a subserver.
  • 1
    . Start the Server Manager instance as the Main server. You will not be able to add this Server Manager instance as a subserver later from the Data Replication Console.
  • 2
    . Start the Server Manager as a subserver. You will not be able to connect to this Server Manager instance later from the Data Replication Console.
Default value:
0
STOP
On Linux and UNIX, stops the Server Manager instance.
UDP_PORT=
nnnn
Overrides the default port through which the Server Manager communicates with the Data Replication components. Valid values are integers from 1 through 65535.
Default value:
8087

Examples:

The following command displays help information for Server Manager parameters:
server_manager.exe HELP
The following command removes the current Server Manager service:
server_manager.exe RUN_AS_SERVICE –r

0 COMMENTS

We’d like to hear from you!