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.For Full Project Builds -
- 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_DIRwith a name that matches the OSB Project project property, and must contain the sources for the OSB project.
For Partial Project Builds -
- No SCM checkout is necessary in the build workflow when using partial build.
- One FlexDeploy project should only include one 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.
...
| Property Name | Property Code | Required | Description |
|---|---|---|---|
| OSB Extended Classpath |
| No | Allows the user to extend the classpath for this plugin call. |
| OSB Home |
| Yes | The Oracle OSB home. (e.g., |
| Oracle Weblogic Home (WL_HOME) |
| Yes | Weblogic Home Directory. (e.g. |
...
| 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 | OSB Project folder is derived by using value of this property, i.e. if <Workflow Execution Temp Directory>/<OSB Parent Project Path>/<OSB Project> is considered Project Folder. Project folder is only valid if it contains either servicebus.sboverview, .settings or .project files. If that is not true or this property is not specified project folder will be derived by searching servicebus.sboverview, .settings or .project files in exported source. | OSB Partial Extensionsn/a | n/a | See partial build file extensions below |
Inputs
| Input Name | Input Code | Required | Description |
|---|---|---|---|
...
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.
Customization/Configuration File
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.
Partial Builds/Building Resources
This operation supports both export the entire OSB project as well as exporting specific OSB resources. When exporting resources your project should be configured for 'partial deployments' for the Oracle Service Bus project type. When populating files objects are filtered largely based on file extensions. If needed the extensions used for mapping can be changed in the project properties.
...
Project Property
...
Default Value
...
There is an additional Object Type for 'Customizations' which is matched based on 'customizationfile', case insensitive, being in the name and having an xml extension.
Resource Dependencies
In JDeveloper there is an option to build resources with dependencies which will automatically package your selected resources along with all the dependencies. This is not done when performing a partial build within FlexDeploy, equivalent of unchecking 'Include Dependencies' when exporting in JDeveloper.
Sboverview file
The .sboverview is required by the build process regardless of what resources are selected. The sboverview file is automatically bundled with each build request without any action needed. Only one sboverview file can be found in the project sources however. To make sure that is the case it is recommended that one OSB project be used per FlexDeploy Project.