Objective
You have a given ADF application 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 application across multiple environments. This automation will include:
...
ADF Build (JDeveloper) Checklist
Checklist | Description |
|---|---|
JDeveloper Install Home | The JDeveloper installation directory on server with JDeveloper is installed. Build of ADF application requires JDeveloper. Make sure to install proper version of JDeveloper as required to build your ADF applications. |
Hostname for JDeveloper endpoint | This is the endpoint where JDeveloper is installed. FlexDeploy will connect to this endpoint to build the EAR/WAR file.Location to Oracle SOA Home i.e. indicates where SOA Suite is installed. |
User Id for JDeveloper endpoint | FlexDeploy will connect to target server using this user. User must have access to JDeveloper installation |
Password for user id | Password for user Id for JDeveloper endpoint. |
JDK home for JDeveloper endpoint | JDK path used by JDeveloper. |
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. |
WebLogic (Java/ADF Application) Checklist
Checklist | Description |
|---|---|
Oracle WebLogic Home (WL_HOME) | WebLogic Home Directory. (e.g. /u01/oracle/products/fmw/wlserver) |
WebLogic Domain Name | WebLogic Domain Name. |
WebLogic Admin Listen Address | The listener address of the WLS admin server. (e.g. localhost) |
WebLogic Admin Listen Port | The port of the WLS admin server. (e.g. 7001) |
WebLogic Admin User | The user name for the WLS admin server. |
WebLogic Admin Password | The password for |
WebLogic Application Name | The name of the application (EAR or WAR) to be deployed. |
WebLogic Server or Cluster Name(s) | WebLogic Server or Cluster name to deploy application. |
WebLogic Domain Directory | WebLogic Domain Directory for managed servers. |
WebLogic Node Manager Host | Host for Node Manager connection. |
WebLogic Node Manager Port | The port for the WLS Node Manager. |
WebLogic Node Manager User | The user id for the WLS Node Manager. |
WebLogic Node Manager Password | The password for WLS Node Manager. |
WebLogic Admin Server Host | The host name for WebLogic Admin Server. |
User Id which runs Admin Server (e.g. oracle) | The User Id which runs Admin Server. |
Password for user Id | The password for user Id which runs Admin Server. |
Create ADF Project using Blueprint
...
Scroll through this guide to fill in the blueprint properties. The Build and Deploy options are auto-selected.
...
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. |
Source Control
Click on source repository dropdown. If you have already created a connection to your source code repository, select it from the list.
...
Otherwise add one by clicking on “Create new Source Repository”.
...
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. Click on “Confirm”.
...
Target Properties
Property Name | Values for this Tutorial | Description |
|---|---|---|
WebLogic Server/Cluster | FlexDeploy_Server1 | The weblogic server or cluster where application should be deployed. |
WebLogic Home Directory | locate this value from your server. | The Port number of the SOA Server. |
Domain Name | fd_domain | The WebLogic Domain Name. |
Application Installation Directory | locate this value from your server. | The base directory to install the weblogic deployments from. For example: /oracle/middleware/product/user_projects/applications |
Admin Server Listen Address | localhost | The listener address for the WLS Admin Server. |
Admin Server Listen Port | 7001 | The port for the WLS Admin Server. |
Admin User | weblogic | The admin username for the WLS Admin Server. |
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 to WorkBetterFaces since it takes the value same as Application Name.
...