An Instance represents a technology running in one or more Environments.
For example,
- You may have an Oracle SOA Suite Instance (SOA1) for most composites, and a second Instance (SOA2) for hosting composites which contain sensitive information such as financial or HR related data.In this case, you would create two Instances in FlexDeploy named SOA1 and SOA2. You can define Name and Code for Instances as per what makes sense for your topology.
- You may have a requirement to perform builds using multiple versions of JDeveloper, such as JDeveloper 11.1.1.9 and JDeveloper 12.2.1. In which case you can create JDEV11119 and JDEV1221 Instances. Then you can associate each Instance with one or more Environments, and describe which endpoints fit in each Environment/Instance combination.
Example #1 Instances for ADF Build/Deploy
| Instance Code | Instance Name | Notes |
|---|---|---|
| ADF11119 | ADF 11.1.1.9 | ADF runtime 11.1.1.9 installation with WebLogic 10.3.6 |
| ADF1221 | ADF 12.2.1 | ADF runtime 12.2.1 installation with WebLogic 12.2.1 |
| JDEV11119 | JDeveloper 11.1.1.9 | JDeveloper 11.1.1.9 installation |
| JDEV1221 | JDeveloper 12.2.1 | JDeveloper 12.2.1 installation |
Example #2 Instances for ADF Build/Deploy
This is simple variation from Example #1 above, where Build and Deploy Instances are named so that users can easily match Build with Deploy Instance.
| Instance Code | Instance Name | Notes |
|---|---|---|
| ADF11119 | ADF 11.1.1.9 | ADF runtime 11.1.1.9 installation with WebLogic 10.3.6 |
| ADF1221 | ADF 12.2.1 | ADF runtime 12.2.1 installation with WebLogic 12.2.1 |
| ADFBUILD11119 | ADF Build 11.1.1.9 | JDeveloper 11.1.1.9 installation |
| ADFBUILD1221 | ADF Build 12.2.1 | JDeveloper 12.2.1 installation |
There are 4 types of Instances:
- Instances - represent a software technology that supports build and/or deploy.
- SCM (Source Code Management) Instances - represent a source code management system such as Subversion, Git, TFS, CVS, etc. Holds properties necessary to authenticate. The paths to specific projects in the SCM are contained in the project instead so that the Instance can be used across many projects.
- Test Instances - represent a software test tool. Holds properties necessary to run tests, and allows the properties to be used wherever the test is run.
- Issue Tracking System Instances - represent an Issue Tracking System. Currently JIRA is supported. The settings on this Instance allow FlexDeploy to authenticate and manage tickets in the issue tracking system.
Viewing Instances
To view the list of Instances defined within FlexDeploy, select Topology -> Instances from the menu.
By default, all active Instances are displayed in the search results. To refine the search results, select one or more criteria options and click on the Search button. Select the Any radio button to indicate the search results should include Instances matching any of the specified criteria, or the All radio button to indicate that the search results should only include Instances matching all of the specified criteria. Click on the Reset button to return to the default search criteria form.
Creating or Editing Instances
Each Instance type has slightly different configuration requirements. The following links will assist in setting up Instances.
- Creating/Editing an Instance
- Creating/Editing an SCM Instance
- Creating/Editing a Test Instance
- Creating/Editing an Issue Tracking Instance
Inactivating/Activating Instances
To inactivate an Instance at any time, select an existing Instance and click the Inactivate button. This will temporarily hide that Instance until, a search is performed where the criteria for Active is switched to "No". To reactivate an Instance, select the desired Instance and click the Edit button. Then change the drop down menu for active to "Yes" and click Save. This Instance is now active in the system again and ready for use.