The Extension life cycle includes the following operations:
Definition. Define the Extension in Integration Studio. In this step you have to create your extension and define its actions, entities, and structures. How?
Coding. In this step you have to define the behavior of your actions.
If your extension does not contain actions that were added manually, you can skip this step. However, the extension continues to have its source code files. See About Extension Source Files.
To code the behavior of your actions, Integration Studio provides the necessary facilities to integrate with the IDE (Integrated Development Environment) you specified. These facilities are:
Edit the extension source code. How?
Update the extension source code with the extension definition in order to reflect the changes you have made in Integration Studio. How?
In the IDE, implement the behavior of your actions and compile the .NET or Java project, depending on the application server you are using, with the extended functionality. How?
Verify. Check whether the extension elements are correctly defined in regard to Integration Studio rules. Only valid extensions can be published and therefore used by eSpaces. This step also updates the extension source code with the extension definition, and afterward, depending on the application server you are using, the dll (Dynamic Link Library) or jar (Java Archive) of the extension is generated. See how to verify an extension.
Even if your extension contains only entities, this step is executed and a dll or jar is generated with the entities definition.
Save. Saves the xif (Extension and Integration Framework) file in the directory you specified.
Publish. Publish the extension in the Platform Server you are connected to. After this operation, the extension is available to be used in your eSpace. See how to use an extension?
To publish your extension, simply click 1-Click Publish in the File menu or Toolbar. The publication of an extension requires several operations that are executed automatically in this step. See the 1-Click Publish operation.
To add more elements to your extension, repeat these steps. If you want to change the behavior of an action already defined, then simply repeat from step 3 on.
Define the Extension | Code the Extension | Verify the Extension | 1-Click Publish the Extension