Startup -Shutdown -Replicate | Services

 What Is a Startup Service?

A startup service is one that the server automatically executes when it loads a package. The server loads a package:

• At server initialization (if the package is enabled)
• When someone uses the Integration Server Administrator to reload a package
• When someone uses the Integration Server Administrator to enable a package

Startup services are useful for generating initialization files or assessing and preparing (e.g., setting up or cleaning up) the environment before the server loads a package. However, you can use a startup service for any purpose. For example, you might want to execute a time-consuming service at startup so that its cached result is immediately available to client applications.

What Is a Shutdown Service?

A shutdown service is one that the server automatically executes when it unloads a package from memory. If a package is in memory, the server unloads the package:

• At server shutdown or restart
• When someone uses the Integration Server Administrator to disable the package
• Before the server removes the package from memory when someone uses the Integration Server Administrator to reload a package

Shutdown services are useful for executing cleanup tasks such as closing files and purging temporary data. You could also use them to capture work-in-progress or state information before a package unloads.

What Is a Replication Service?

A replication service is one that the server automatically executes when it prepares to release or archive a package. The service executes when the administrator clicks the Create Release link on the Packages > Publishing > Create and Delete Releases screen or the Archive icon archive package icon on the Packages > Management screen.

Replication services provide a way for a package to persist state or configuration information so that this is available when the package is activated on the remote server.

Guidelines for Using Startup, Shutdown, and Replication Services

Keep the following points in mind when using startup, shutdown, and replication services.

• When you create a startup or shutdown service, you must register that service in the package with which it will be used. When you create a replication service, you can register any valid service from any loaded package on the server, including the current package itself.
• Because services in a package are not made available to clients until that package's startup services finish executing, you should avoid implementing startup services that access busy remote servers. They will delay the availability of other services in that package.
• You may assign one or more startup services to a package; however, you cannot specify the order in which they will execute. If you have a series of operations that must execute in a specific order, encode the entire sequence within a single service or have a startup service invoke others.

Source:

https://documentation.softwareag.com/

Refer: webMethods Developer guide for more info..