Getting Started
Guide
Version 3.5
2016-05-09
Introduction
The Getting Started Guide aims to get customers and potential customers on the fast-track for getting FlexDeploy up and operational in a very short period of time. This guide anchors on configuring FlexDeploy to perform build and deployments for Oracle ADF and SOA Suite (for a single deployment environment – e.g. Development). The same steps can be used to configure FlexDeploy for other technologies and/or environments.
This guide does not cover all features or configuration options for FlexDeploy. The complete documentation can be found in the FlexDeploy User's Guide found on the Flexagon Support Site.
Prerequisites
This guide assumes that you have the following prerequisites in place.
- FlexDeploy is installed and running (whether as a production implementation or the trial edition).
- A computer (server or PC/Laptop) which has the software components required for executing Oracle ADF and SOA Suite builds. (For the purposes of a trial this can be the same PC/Laptop which hosts the FlexDeploy server). The required build software components are:
- An SSH Server (i.e. OpenSSH)
- Oracle JDeveloper
- You must have existing JDeveloper projects containing an Oracle ADF application and Oracle SOA Suite composite, and have them under source control (Subversion or Git). This guide will walk through the steps necessary to configure FlexDeploy to begin building and deploying these projects.
Configuring FlexDeploy
Logging In to FlexDeploy
Launch FlexDeploy in a supported browser using the following address:
http://\{host}:{port}/flexdeploy
Enter the Username fdadmin and its password. The default password during installation is welcome1 (which can be changed using the Administration -> Security -> Users page).
Installing Plugins (This section can be skipped if using the Community Edition)
The following plugins will be used within the Oracle ADF and SOA Suite workflows that are developed within this Getting Started Guide.
...
*Note that newer versions may be used if available.
Creating Endpoints
The next step is to configure FlexDeploy with endpoints that provide the ability to communicate with each build and deploy server across your topology. Let's start by creating a BuildEndpoint which will hold the properties needed to connect to a server used for building applications. This server should have JDeveloper installed.
...
Follow the same steps to add an endpoint for the SOA and ADF servers.
Creating Environments
The next step is to configure FlexDeploy for the build and deploy environments across your topology. Let's start by creating a Build environment to execute the ADF and SOA Suite builds on, and another Development environment to deploy those builds to.
...
Field Name | Value | Description |
|---|---|---|
Environment Id | N/A | System generated identifier (read-only). |
Environment Code | DEV | Short name for the environment. |
Environment Name | Development | Long display name for the environment. |
Description | Development | A description of the environment. |
Active | Yes | Whether or not the environment is active in the system. Defaults to "Yes". |
Build Environment | No | Identifies whether the environment is used for builds. Defaults to "No". |
Sort Order | 2 | A sort index to control the order in which the environment is displayed within lists. |
Creating Technology Instances
Next we need to create instances for the technologies which we will be used for building and deploying. For the purpose of this guide, we will create a generic build instance to host our build-related technologies (i.e. JDeveloper), a build instance which has SOA Suite installed for our SOA related builds, and deployment target instances for ADF and SOA Suite.
...
Field Name | Value |
|---|---|
Instance Id | N/A |
Instance Code | SOA1 |
Instance Name | SOA1 |
Description | SOA1 |
Target | Yes |
Active | Yes |
Associated Environments | DEV |
Associated Workflows | (Skip) |
Associated Plugin Operations | FlexagonSOAPlugin – soaDeploy |
Creating a SubVersion Instance
Next we need to create an SCM instance for SubVersion which we will be used during the build process. SCM instances are not environment specific, so we will only configure this once.
...
Fill in the information per your SubVersion information.
Click save.
Configuring Environment Instances
An Environment Instance, as its name suggests, is simply an association between one environment and one instance. The Environment Instances were created automatically when we associated the instance to environments. The association can then be used to assign endpoints and provide values for any properties mapped to those environment instances (through workflows or plugin operations).
...
Note that for the BuildSOA/Build environment instance, you can associate it to the same endpoint that you will use for the DeploySOA/Development endpoint. From a SOA build perspective we simply need the libraries of any SOA Suite installation.
Creating Workflows
Next we will create reusable workflows which define the build and deployment operations for Oracle ADF applications and Oracle SOA Suite composites. These workflows will then be used by many projects to deploy specific applications and composites (coming in the next section).
...
For more information regarding inputs for these plugin operations refer to the plugin guides located on the Flexagon Support site. For the FlexDeploy Community Edition the documentation is located in the <flexdeploy install folder>/docs.
Creating Projects
You should now have workflows for building and deploying both ADF applications and SOA Suite composites. These workflows can be used to build and deploy hundreds of ADF applications and SOA composites across your enterprise without any changes required.
...
Repeat the steps in this section to create an application and project for SOA Suite, referencing the plugin guides as necessary.
Executing Build & Deployments
We have now configured FlexDeploy with everything it needs to begin executing build and deployment requests for the ADF and SOA projects that were created.
...