Operations Guide

10.5 HotFix 2
- 10.5 HotFix 1
- 10.5
- 10.2 HotFix 1
- 10.2
- 10.1 HotFix 1
- 10.1
- 10.0 HotFix 1
- 10.0

Back Next

idssvc Utility

Use the idssvc utility to create or delete a Windows service for all the servers except the Synchronization Server. The idssvc utility uses the following syntax:

To create a Windows service:

idssvc install <Service Name> <Start Program Name> <Stop Program Name>

To delete a Windows service that you create:

idssvc delete <Service Name>

The idssvc utility uses the following parameters:

Service Name: Name of the service that you want to create. The idssvc utility adds the
IDS_
prefix to the service name to ensure that the
MDM Registry Edition
services group together when you view them in the Service Control Manager.
Start Program Name: Fully qualified name of a program or script to run when you start the service. Enclose the name of the program or script and its parameters within double quotes (").
Stop Program Name: Fully qualified name of a program or script to run when you stop the service. Include all the parameters that you specify in the
Start Program Name
parameter, and enclose them within double quotes (").

Informatica recommends that you use batch scripts instead of programs because a batch script can establish environment variables that

MDM Registry Edition

requires to function correctly. For example, when you set a service startup type to automatic, a batch script can set the environment variables before starting the

MDM Registry Edition

servers so that the servers function correctly.

After you create a Windows service, you can manually start or stop in the Service Control Manager or from a command line. To start or stop a service from a command line, run the following commands:

To start a service,

net start <Service Name>

To stop a service,

net stop <Service Name>

When you specify a Windows service name, ensure that you include the

IDS_

prefix.

You can use the Service Control Manager to change the service startup type to automatic.

The

<Service Name>.log

file in the following directory logs all the error messages and informational messages associated with the service:

<MDM Registry Edition Installation Directory>\bin

. The service does not log the messages to the Windows Event Log, which requires the provision and registration of a dependent message DLL file.

Sample Script to Create a Windows Service

You can find a sample script in the following directory:

<MDM Registry Edition Installation Directory>\bin\svcdemo.bat

The following example uses the sample script for both the start and stop calls. However, in the production environment, you can use different start and stop scripts. Specify the

start

parameter with the start script name so that the scripts do not run in the same shell.

idssvc install demo "c:\InformaticaIR\bin\svcdemo start" c:\InformaticaIR\bin\svcdemo

Use the following guidelines if you create a script that runs when you start or stop a Windows service:

Call the following file to establish the

MDM Registry Edition

environment variables:

<MDM Registry Edition>\env\mdmres.bat

Start all the processes with the

start

parameter so that the processes do not run in the current shell. For example, if you start the Update Synchronizer without the

start

parameter, the service script cannot return the control until the Update Synchronizer stops.

The

idsup.bat

file located in the following directory uses the

start

parameter internally:

<MDM Registry Edition>\bin

Call other scripts, but ensure that you transfer the control by using a

call

parameter. Otherwise, the control never returns when the called script ends, and the service script cannot return the control.

When you stop the servers by using the

idsdown.bat

file located in the following directory, you can specify the

hard

option to force an immediate shutdown that disconnects the active clients:

<MDM Registry Edition>\bin

For example, you can start the Update Synchronizer with the

--rbcheck

switch to periodically test the Rulebase connectivity and to abort the connection when the Rulebase Server is inaccessible. This switch avoids the need to run the

syncstop

script.

Set the response code to indicate success or failure at the end of the script. Use the

cmd /c exit /b %SSARC%

command, which sets

SSARC

to 0 for success and 1 for failure.

Windows Services

Download Guide

Watch

Comments

Communities