Building Your Event-Driven Architecture : Service Development Help : Managing Packages : Assigning Startup, Shutdown, and Replication Services to a Package : What Is a Startup Service? : Assigning a Startup Service
Assigning a Startup Service
Keep the following guidelines in mind when assigning startup, shutdown, and replication services to packages:
*When you assign a startup or shutdown service to a package, you can only assign a service that resides in the same package. For example, a startup service for the “Finance” package must be located in the “Finance” package.
*Because services in a package are not made available to clients until the 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 can assign one or more startup services to a package; however, you cannot specify the order in which the services execute. If you have a series of startup services that need to execute in a specific order, create a “wrapper” service that invokes all the startup services in the correct order. Designate the “wrapper” service as the startup service for the package.
*If a startup service invokes a service in another package, make sure to identify the other package as a package dependency for the package containing the startup service.
To assign a startup service
1. In Package Navigator view, select the package to which you want to assign startup services.
2. Click File > Properties.
3. In Properties for PackageName dialog box, select Startup/Shutdown Services.
4. Under Startup services, select the service from the Available Services list, and click .
Repeat this step for each service you want to add as a startup service for the package.
Note:  
A service that you just created does not appear in the Available Services list if you have not refreshed your session on the server since you created the service.
5. Click OK.
Copyright © 2016 - 2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback