Objective
You have a given SOA composite that was developed in JDeveloper and the source code is managed in a GIT repository. The goal of the tutorial is to automate the deployment of the composite across multiple environments. This automation will include:
...
The tutorial does not cover every feature or configuration option available in FlexDeploy.
Checklist
Checklist | Description |
|---|---|
Are configuration plan files stored in a separate folder or along with composite? | Know where the configuration files are stored so that you can modify the build and deploy workflows accordingly. |
Oracle SOA Home (installation path) | Location to Oracle SOA Home i.e. indicates where SOA Suite is installed. |
SOA Server Host | Host name of the SOA-managed server. |
SOA Server Port | Port number of the SOA managed server, which will be the SSL Listen Port or Listen Port based on whether you desire to connect using SSL. |
WebLogic Admin User | Admin user name for WebLogic server. |
WebLogic Admin Password | Weblogic Admin User password for WebLogic server. |
MDS User Id | Username of MDS Access |
MDS Password | Password for MDS UserID. |
MDS JDBC URL | Database URL for MDS access. |
Connectivity to WebLogic Node(s) | FlexDeploy should be able to communicate over SSH with WebLogic domain nodes. |
User id which runs Oracle SOA (eg. Oracle) | FlexDeploy will connect to target server using this user. |
Password for user id which runs Oracle SOA | The password for the User Id which runs Oracle SOA. |
JDK Home for WebLogic Node(s) | Recommended JDK used by Oracle SOA |
Base Directory on each WebLogic Node | Minimum of 4GB space on each WebLogic node. Avoid /tmp and /var/tmp as Linux processes may clean up files automatically and conflict with FlexDeploy. |
Create SOA Project using Blueprint
...
Scroll through this guide to fill in the blueprint properties. It is a best practice to name the Project with the same name as the SOA Composite, a FlexDeploy property (ProjectName and FD_PROJECT_NAME) will be automatically set and can be utilized during the configuration.
...
Project Info
Property Name | Value for this tutorial | Description |
|---|---|---|
Composite Name | HRSOAService | Name of the composite that is being built and deployed. |
SOA Partition | Order | SOA Partition / Folder should this composite be deployed to. |
Jdeveloper .jws Name | HRSOAService | Brief description of the custom module. |
SOA Install Name | SOA1 | This value will provide environment independent name for SOA install (eg. SOA, SOAHR ). The default is SOA. |
Composite Description | Creating SOA project using Blueprints | Brief description of the composite. |
The Build and Deploy options are auto-selected.
...
Otherwise add one by clicking on “Create new Source Repository”. Enter the sparse checkout folders script, if any.
...
Inputs Info
Field | Required | Description |
|---|---|---|
Name | Yes | A descriptive name for this SCM instance. |
Code | Yes | A technical code for the instance, without any spaces. The codes are available as variables to shell and Groovy scripts, and therefore needs to comply with their limitations. |
Source Control Type | Yes | Type of Source Control Management System. We will use Git for this tutorial. Supported Source Control Management Systems are:
|
Description | No |
|
SCM Properties | Yes | The remaining properties are specific to the selected SCM. For Git:
|
We selected the SCM type as GIT. The properties related to the GIT source control management will be displayed on the screen.
...
Enter values for any workflow properties which are required for the build and deploy. In the image below, no properties are required for this build. Select the target endpoint that the build and deploy should execute on.
...
Target Properties
Property Name | Values for this Tutorial | Description |
|---|---|---|
SOA Server Host | locate this value from your SOA server. | The hostname of SOA Server. |
SOA Server Port | 8001 | The Port number of the SOA Server. |
Oracle SOA Home | locate this value from your SOA server. | Oracle SOA Home, indicates where SOA Suite is installed. |
MDS JDBC URL | locate this value from your server. | The database URL for MDS Access. |
MDS User | DEV_MDS | The Username for MDS Access. |
MDS Password | locate this value from your MDS Access. | Password to connect for MDS Access. |
WebLogic Admin User | weblogic | The admin username for the WLS Admin Server. |
WebLogic Admin Password | locate this value from your WLS admin server. | The admin password for the WLS Admin Server. |
The Project Name will be auto updated as HRSOAService since it takes the value same as SOA Composite.
...