Modeling Activation SRT Cartridges

Following this procedure and refer to the corresponding topics to model Activation SRT cartridges:

To model Activation SRT cartridges:

Import Activation Service cartridges from a cartridge project to obtain service actions that you can use for the SRT cartridge.

See "Importing Projects" for more information.
Create a customer specific service model.

In most cases you create a common service model based on the imported cartridges. See "About Common Service Models" for more information.
Create an Activation SRT cartridge project and set up the Activation SRT cartridge.
1. Use the Activation Cartridge Project wizard to create an Activation SRT cartridge project and display it in the Studio Projects view of the Design perspective.
  
  See "Creating New Activation SRT Cartridges" for more information.
2. Configure the cartridge details in the Activation SRT Project editor to define the content.
  
  See "Activation SRT Project Editor" for more information.
Create one or more translations.

You configure translations to enable the SRT to accept and recognize messages from upstream systems at runtime. See "Modeling Translations" for more information.
Model service bundles to enable the SRT to execute actions (service actions and atomic actions) based on the content of translated messages from upstream systems.
1. Create service bundles to map information from the incoming (translated) messages from upstream to the appropriate service actions that need to be executed downstream (against the network elements).
  
  See "Creating Service Bundles" for more information.
2. Associate service actions with the service bundle.
  
  Select the service actions from the customer specific service model that need to execute for the service bundle. See "Associating Service Actions with the Service Bundle" for more information.
3. Define service action spawning conditions (if required) that allow service actions to be conditionally spawned.
  
  See "Understanding Service Action Spawning Conditions" for more information.
4. Add upstream interface parameters that describe the parameters that are expected from the upstream system for this service bundle.
  
  See "Understanding Upstream Interface Parameters" for more information.
5. Map upstream interface parameters to service action parameters that allow the SRT to map the incoming data from the translated order to the service actions selected to run for the service bundle.
  
  See "Mapping Upstream Interface Parameters to Service Action Parameters" for more information.
6. Use lookups (if any were configured).
  
  See "Understanding Lookups" for more information.
  
  Note:
  Data required by the service bundle that is not provided on the order from the upstream system is obtained by configuring lookups. Lookups can also be used to format parameters (for example, to split parameters apart into constituent parameters, or to join parameters together into a single parameter).
  See "Configuring Lookups" for more information.
Package the cartridge.

Use the SRT Project editor to specify which elements will be included in the cartridge SAR file. See "Packaging Activation SRT Cartridges" for more information.
1. Create the JAR with ANT.
2. Include JARs in the SAR.
3. Put external JARs in the NEP classpath on the ASAP server.
Deploy the cartridge.

See "Deploying Cartridge Projects" for more information.
1. Create a Studio Environment project and a Studio Environment in the Studio Projects view (use corresponding wizards for both the tasks).
2. On the Connection Information tab of the Studio Environment editor, specify how to connect to the activation environment.
3. In the Cartridge Management view, add cartridges for deployment, deploy them to the run-time environment, undeploy them from the run-time environment, and remove them from the list of cartridges that were added for deployment.
4. Use the NEP Map editor to deploy and manage network elements.