To configure an Activation Service cartridge project:
Import the Activation Network cartridge projects that contain the entities you need for your Service cartridge project.
See "Importing Projects", "Importing Activation Cartridges from SAR Files", and "Importing Cartridge Projects from Environments" for more information.
Create an Activation Service cartridge project.
Double-click the cartridge project entity to display the project in the Activation Project editor. See "Creating New Activation Cartridge Projects" and "Activation Project Editor" for more information.
Design the service model.
Determine what type of service model you need.
Options are:
The vendor, technology and software load-specific service model. See "About Vendor, Technology, and Software Load-Specific Service Models" for more information.
The common service model. See "About Common Service Models" for more information.
The mixed service model. See "About Mixed Service Models" for more information.
Create elements for the service model.
You can create service actions with a wizard or with the Cartridge Generation feature. You can create the necessary atomic actions with a wizard (this is called a common service model) or use atomic actions from imported Activation Network cartridge projects (this is called a mixed service model). See "Creating Service Actions, Atomic Actions, and Action Processors" and "Generating Framework Models" for more information.
Define the relationship between model elements by linking them manually and defining their parameters.
See "About Service Action, Atomic Action, and Action Processor Relationships" for more information.
Extend the user-defined exit types.
See "Configuring User-Defined Exit Types" for more information.
Create custom action processors.
See "Working with Custom Action Processors" for more information.
Configure network elements.
Define a network element.
A network element represents one specific piece of equipment (a single instance) in the network. A connection pool contains one or more connections that can be used to connect to the network element (possibly simultaneously). Each network element has a single connection pool associated with it. See "About Network Elements" for more information.
Define a dynamic NE template.
If you do not intend to configure static network element instances for a specific customer solution, you can configure dynamic NE templates to allow network element attributes to be dynamically sent to ASAP 5.x on work orders. Dynamic NE templates are used when upstream systems (such as Inventory) contain the necessary information to connect to the network element instance. Passing this information to ASAP 5.x dynamically avoids having to configure it in multiple locations (for example, in ASAP 5.x as well as in an inventory system). See "Creating NE Templates" for more information.
Package the cartridge project.
Use the Project editor to specify which elements will be included in the cartridge project SAR file.
If the service model you have created depends upon elements in an Activation Network cartridge project it is also necessary to specify which elements of the Activation Network cartridge project should be deployed. Deselect any elements that are not required in the dependent cartridge project.
Create the JAR with ANT.
Include JARs in the SAR.
Put external JARs in the NEP classpath on the ASAP server.
See "Packaging Projects" for more information.
Deploy the cartridge project.
Create a Studio Environment project and a Studio environment in the Studio Projects view (use corresponding wizards for both the tasks).
On the Connection Information tab of the Studio Environment editor, specify how to connect to the activation environment. See "Studio Environment Editor Activation Connection Details Area" for more information.
The NEP Map editor and Activation Test case utility use the information specified in the Activation Connection Details area to deploy network element configuration and to submit test work orders to a run-time ASAP environment respectively.
In the Cartridge Management view, deploy cartridge projects to the run-time environment, and undeploy them from the run-time environment.
Use the NEP Map editor to deploy and manage network elements.
See "Deploying Cartridge Projects" for more information.