- 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 property and must contain the sources for the OSB project.
Target Properties
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. |
Weblogic Admin Use SSL |
| Yes | If the Weblogic admin server is using SSL to connect. |
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 | 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. |