Export OSB the project from JDeveloper project as the OSB server to a jar file. 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.
It is good practice to create FlexDeploy project with name that matches composite name.
This operation should be run on a SOA server. To accomplish this, Flexagon recommends adding the SOA 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.OSB server.
Environment/Instance Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
| Weblogic Admin User |
| Yes | The user for the WLS admin server. |
| Weblogic Admin Password |
| Yes | The password for |
| Weblogic Admin Listen Address |
| Yes | The listener address of the WLS admin server. For example: localhost |
| Weblogic Admin Listen Port |
| Yes | The port of the WLS admin server. (e.g 7001) |
| OSB Extended Classpath |
| YesNo | Allows the user to extend the classpath for this plugin call. |
| OSB Home |
| Yes | The Oracle OSB home. For example: |
| Oracle Weblogic Home (WL_HOME) |
| Yes | Weblogic Home Directory. (e.g. |
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 Passphrase |
| No | Passphrase used to encrypt or decrypt jar file. |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Outputs
Output Name | Required | Description |
|---|---|---|
Artifacts
This operation produces a deployable jar file artifact that will be stored in the artifacts repository.
...