You can create and configure Activation Network cartridges. See "Understanding Design Studio for Activation Projects".
To configure an Activation Network cartridge:
Create an Activation Cartridge project and set up the Activation Network cartridge.
Use the Activation Network cartridge project wizard to create an Activation Network Cartridge project and display it in the Studio Projects view of the Design Perspective. See "Creating New Activation Cartridge Projects" for more information.
Configure the cartridge details in the Activation Network Project editor. See "Activation Project Editor" for more information.
Define and edit the elements.
Create service actions, atomic actions, action processors, and activation run-time parameters as elements for the model. See "Creating Model Elements" and "Creating Activation Run-Time Type Parameters in the Data Dictionary"for more information.
You can create elements with a wizard or with the Cartridge Generation feature, which creates and links the elements. See "Generating Framework Models" for more information.
Do any one of the following:
For elements that you created with a wizard, define their relationships by manually linking service actions, atomic actions, and action processors, and define the element parameters.
For elements that you created with the Cartridge Generation feature, the linking process is automated, and elements are automatically created and linked.
See "Understanding Model Element Relationships" for more information.
Add information that will be used for auto-generation of documentation for the model.
See "Documenting Cartridges" for more information.
Implement the action processor.
Define a Java action processor implementation.
Use the Java with code generation implementation to write the logic in the execute method of the processor class (the proxy automatically performs several steps of code generation). See "Understanding Java with Code Generation" and "Understanding the Java Processor Class" for more information.
Configure Java libraries. See "Understanding Java Libraries in Design Studio" for more information.
Use the Unit Test procedure to generate a test case, which enables you to test the processor outside of the ASAP environment.
Configure a Unit test for the processor. See "Testing ASAP Cartridges in Design Studio".
Configure the user-defined exit types (UDET). See "Configuring User-Defined Exit Types" for more information.
Create UDETs as elements for the model.
Configure the UDETs in the editor to define the content.
Implement the connection handler.
Write a Java Connection Handler. See "Generating a Telnet NE Connection Handler Implementation" and "Generating a Custom NE Connection Handler Implementation" for more information.
Define the network element model. See "Working with Network Elements" for more information.
You must create and configure at least one of the following elements (all three elements are related as they involve connection to equipment):
NE templates.
A template that can be copied to create one or many specific network elements.
Network elements.
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.
Dynamic NE templates.
In some cases it is not ideal to configure static network element instances for a specific customer solution. In such cases, dynamic NE templates can be configured allowing 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).
Package the cartridge.
See "Packaging Activation Cartridges" for more information.
Model the packaging.
Use the Project editor to specify which elements will be included in the cartridge (SAR file).
Create the JAR with ANT.
Include JARs in the SAR.
Put external JARs in the NEP classpath on the ASAP server.
Deploy the cartridge.
See "Deploying Cartridge Projects" for more information.
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 cartridges to the run-time environment, and undeploy them from the run-time environment.
Use the NEP Map editor to deploy and manage network elements.