Exports the Exports an OSB project from either an Eclipse or JDeveloper Workspace to a deployable jar file. The jar file will be stored in the artifacts folder for you automatically.
You should checkout or export code for OSB project (not entire JDeveloper application) from SCM prior to running this operation. Checkout or Export can be easily done if you configure project with Source details. A folder must exist in FD_TEMP_DIR with a name that matches the OSB Project project property, and must contain the sources for the OSB project.
This operation should be run on a OSB server. To accomplish this, Flexagon recommends adding the OSB instance to a build environment rather than checking the "Build Environment" checkbox in a deployment environment. This will reduce the number of environments that show up when you choose to build.
Environment/Instance Properties
| Property Name | Property Code | Required | Description |
|---|---|---|---|
| OSB Extended Classpath |
| YesNo | Allows the user to extend the classpath for this plugin call. |
| OSB Home |
| Yes | The Oracle OSB home. For example: /opt/middleware/Oracle_OSB1 |
| Oracle Weblogic Home (WL_HOME) |
| Yes | Weblogic Home Directory. (e.g. /u01/oracle/products/fmw/wlserver) |
Project Properties
| Property Name | Property Code | Required | Description |
|---|---|---|---|
| OSB Project |
| Yes | OSB Project Name. |
| OSB Jar Name |
| Yes | Name of the jar file used to deploy the OSB project. |
| OSB Configuration Project |
| No | OSB Configuration Project Name. |
| OSB Parent Project Path |
| No | This path is used for SCMs like Git where the project folder |
| is nested in a set of folders. Specify parent folders to the project (e.g. osb/Project, specify osb in this property) |
Inputs
| Input Name | Input Code | Required | Description |
|---|---|---|---|
...
During the build workflow, the customization/configuration file inside the project should be copied to the artifacts folder using the File Plugin's saveArtifacts operation.