Use the Activation Project editor to configure the cartridge specifications and parameters. In the Studio Projects view, double-click the Project entity to open the Activation Project editor.
Notes:
Network elements and environments for ASAP are not defined in Activation cartridge projects.
Activation cartridge projects are also Java projects (built on functionality of Java project). Java development can be done inside Activation cartridge projects; you do not need a separate Java project for development.
Eclipse online documentation for Java projects (including configurations, properties, and settings) also applies to the Java configuration of an Activation cartridge project. See Eclipse online documentation when setting up a cartridge.
When working with the Activation Project editor, see the following topics:
Use the Blueprint tab to view the generated documentation of the project, including cartridge properties, service actions, atomic actions, action processors, connection handlers, and network element configuration (for network cartridges) or service configuration (for service cartridges). This tab is read only.
Use the Properties tab to configure cartridge properties and network element details. See "Project Editor Properties Tab" for more information about fields in this tab that are not specific to ASAP.
Note:
In Activation, the Default field is not applicable.| Field | Use |
|---|---|
| Cartridge Type | Displays the cartridge type (Activation Service Cartridge or Activation Network Cartridge) selected on the New Studio Activation Cartridge Project wizard. |
| Vendor, Technology, and Software Load | Displays as specified in the New Studio Activation Cartridge Project wizard. In case of a new network element version you can change the vendor, technology, and software load. This allows you to reuse the cartridge. |
| Supported Hardware Models | Specify which network elements the cartridge supports. |
Use the Cartridge Layout tab to generate a framework model for a network or service cartridge.
For network cartridges, this tab enables you to generate a framework model, which creates a service action, atomic action and an action processor for any combination of action and entity and creates the appropriate association for the three elements in a 1:1:1 relationship. See "Generating Framework Models" for more information about framework models.
For service cartridges, this tab enables you to generate service actions. You can create a service model that is appropriate for a specific customer.
| Field | Use |
|---|---|
| Add | Click to add action names and description in the cartridge project. For example, ADD, MOD, DEL, or QUERY. |
| Remove | Click to clear action names and description from the cartridge project. |
| Add | Click to add entities, which are related to actions, and their description in the cartridge project. For example, SUBSCRIBER, GSM-SUBSCRIBER, ROUTE, TRUNK, or LINE. |
| Remove | Click to clear entities from the cartridge project. |
| Generate Cartridge | Click to generate a framework model for a network or service cartridge. The framework model is based on a combination of actions and entities. See "Generating Framework Models" for more information about framework models. |
Use the Packaging tab to specify which entities to include in the cartridge SAR file. For service cartridges, usually all entities are deployed. In the Cartridge Packaging Instructions area select which entities you want to include for each of the categories.
| Field | Use |
|---|---|
| Include all from Project | Select to include all entities from a specific resource. For example, if you want to include all of your Java libraries, select Libraries from the left-side column, then select the Include all from Project check box. The system will include all libraries in the package file. |
| Select | Click to add an entity in the package file. |
| Open | Click to open a specific entity. |
| Remove | Click to clear a specific entity from the package file. |
Use the Locations tab to display where items get stored. In Default Naming area, the Archive File Name field displays the same name as the project name.
Notes:
If you change the ASAP version in the Locations tab to a version different than the version you selected during cartridge project creation, you must also update all dependent JAR files, such as asaplibcommon.jar, JInterp.jar, Studio_2_6_0.jar, and any other related JAR files. These files are required when the cartridge depends on third-party libraries. Additionally, you must delete any generated code. Lastly, you must perform a clean and full build to regenerate the code.
Design Studio uses the default implementation package name as a prefix for generated code. Oracle recommends that you accept defaults and follow recommended naming conventions for all entities that you create.
Use the Testing tab to view ASAP test cases that you created for your projects and run them individually or simultaneously.
| Field | Use |
|---|---|
| Environment | Select a Studio environment that has configuration for an ASAP environment. |
| Include all from Project | Select to include all test case entities. |
| Entity | Displays activation test case entities. |
| Status | Displays the status of a work order. |
| Run All | Click to execute all test cases one by one in the Studio environment. |
| Separate Console for each Test Case | Select to open a different console window for each test case in a Studio environment. |
| Select | Click to add a test case entity from the project. |
| Open | Click to open a specific test case entity. |
| Remove | Click to clear a specific test case entity from the Testing tab. |
| Run | Click to execute a specific test case. |