Activation SRT Project Editor

Use the Activation SRT Project editor to configure the Activation SRT cartridge. In the Studio Projects view, double-click the Project entity to open the Activation SRT Project editor.


  • Network elements and environments for activation are not defined inside an SRT cartridge project. Only items that get bundled for delivery are defined.

  • An Activation SRT cartridge project is also a Java project (builds on functionality of Java project). A separate Java project for development is not required.

  • Eclipse online documentation for a Java project and its configurations, properties, and settings also applies to the Java configuration of a service cartridge project.

When working with the Activation SRT Project editor, see the following topics:

Activation SRT Project Editor Properties Tab

Use the Properties tab to configure the cartridge properties.

Field Use
Description Specify a name for the project as it should appear in Design Studio and in the run-time environment.
Provider Specify a name or description for the project to help identify the project within the Design Studio environment.

If you have purchased a cartridge project from a third party, this field will contain the name of the third-party provider. For cartridges purchased from Oracle, for example, this field displays Oracle Corporation.

Identifier Specify a database name for the project.
Major Version Number, Minor Version Number, Maintenance Pack, Generic Patch, and Customer Patch Define values to create a 5-segment release version numbering scheme.

You can define release version numbers for any unsealed and deployable Design Studio cartridge project. Cartridge projects must always have a valid version number. When you create a cartridge project for the first time, Design Studio applies the following default values:

  • Major Version Number: 1

  • Minor Version Number: 0

  • Maintenance Pack: 0

  • Generic Patch/Customer Patch: 0

You can edit the values in these fields to create new project instances in the run-time environment. When you edit any of these fields, you create a new instance of the corresponding project when you deploy in a run-time environment. You can create new instances of a project when you want to deploy a new version of a project while keeping the older version in the run-time environment.

For example, when you make changes to a cartridge project, you can increment the version number and deploy the instance of the project to the run-time environment, while retaining the older version in the environment.

Note: Modifying these field values does not create a separate instance of the project in Design Studio. When changing version numbers, Oracle recommends that you use a source control system to ensure that you are able to return to the previous version.

Important: Design Studio cannot support multiple versions of a project in the same workspace. Multiple versions of a project in the same workspace create conflicting model entities.

Build Number Indicates which version of the metadata is used by the corresponding project. If you have enabled the automatic build feature, Design Studio increases the build number automatically every time you save. To enable the automatic build feature, from the Project menu, select Build Automatically.
Target Version Select the version of the run-time application instance to which you want to deploy the cartridge project. Design Studio builds your project to be compatible with the run-time software version you select from this list.

Select the highest version number that is equal to or less than the version of the run-time software to which you want to deploy the project. For example, if you are deploying to release 7.2, select the highest version number that is equal to or less than version 7.2.

Note: The list appears only for cartridge projects that are deployable to run-time environments. When you select a new value from the list, Design Studio automatically initiates a new build. Some entity configurations may no longer be valid for the new application version.

State Click any one of the following:
  • Seal: Prevents changes to the project. For example, you may seal a project after the cartridge design is complete, debugged, and tested to prevent users who import the project from rebuilding or overwriting the original build artifacts.

  • Unsealed: If you want to make changes to the project, then rebuild it to obtain a new archive file.

Note: To modify files defined as read only, you must edit the entity read-write properties. See "Defining Entity Read-Only Properties" for more information.

Related Topics

Activation SRT Project Editor

Creating ASAP SRT Cartridge Projects

Activation SRT Project Editor Packaging Tab

Use the Packaging tab to specify what entities will be included in the cartridge SAR file.

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 Java Libraries from the left-side column, then select 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.

Related Topics

Activation SRT Project Editor

Packaging Activation SRT Cartridges

Activation SRT Project Editor Locations

Use the Locations tab to display where items get stored. This tab is not configurable.


The Default Implementation Package name is used as a prefix for the generated code. You should accept default values and follow recommended naming conventions for anything you create.

Related Topics

Activation SRT Project Editor

Activation SRT Project Editor Blueprint Tab

Use the Blueprint tab to view the generated documentation of the project, including cartridge properties and SRT model configuration. This tab is read only.

Related Topics

Activation SRT Project Editor