Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Service Packages

Updated on April 6, 2022

Use a Service Package data instance to define a package name, define access for listeners, and support deployment of services.

Where referenced

The name you choose for your service package is also used as the first key part of a set of service rules that are developed, deployed, and used together. (A service rule is an instance of a class derived from the Rule-Service - class.)

Create the Service Package data instance before creating any service rules with that package name. After you create or modify the corresponding service rules, access the Service Package data instance again and use the Methods and Deployment tabs to support deployment and client software development for the service.


Use the Records Explorer to review or create Service Packages in your system.


The Data-Admin-ServicePackage class contains service package data instances. This class is part of the Integration-Resources category.

Associated ruleset

When you save a service package data instance, the system automatically associates it with the ruleset of the Application rule for the current application. This association assists with application packaging. You can update the associated RuleSet using the field in the upper right corner of the form.

If there is no ruleset associated with the data instance (for example, for existing instances not previously associated with a ruleset), the Associated Ruleset displays [none].

To create a service package, complete the following tasks:

  • Creating a service package

    Create a service package to group service rules that are designed to be developed, tested, and deployed together. The service package determines the security scheme and access for the services in the package.

  • Service package access group

    Learn about the differences between configuring a service package access group for an authenticated user and unauthenticated user. Review the following information so you can decide which configuration applies to your business needs before completing the Context tab of your service package.

  • Defining processing and authentication for service packages

    Complete the Context tab to indicate whether stateful or stateless processing applies to this package, and to identify an access group for listeners and requestors.

  • Viewing methods for a service package

    After completing or updating the service rules in the service package, confirm that all the services rules you expect are present and accessible before you deploy. For Service REST rules, you can also view and delete the invocation history.

  • Configuring a requestor pool for a service package

    Use the Pooling tab to configure a requestor pool for the services in this service package.

  • Stateless processing and pooling for service packages

    Stateless processing and requestor pooling are appropriate when the client (calling) system handles security, transactions, workflows, and similar aspects of the interface.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us