An Instance is a logical concept representing represents a technology running across its environment lifecycle. in one or more Environments.
For example,
- You may have an Oracle SOA Suite instance Instance (SOA1) for most composites, and a second instance 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 Instances as per what makes sense for your topology.
- You may have a requirement to perform build for 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 instancesInstances. 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
...
This is simple variation from Example #1 above, where Build and Deploy instances Instances are named so that users can easily match Build with Deploy instanceInstance.
| 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 instancesInstances:
- Target Instances (often referred to as just Instance) support managing both build and Instances - represent a software technology that supports build and/or deploy.
- SCM (Source Code Management) Instances allow the user to manage a shares SCM instance like - 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 allow the user to manage a separate test instance when the test tooling is not located on the deploy or build server. An example would be SOAPUI that is installed on its own server and is used to test deployment across many target instances.Issue Track System Instances allow the user to manage a separate ITS instance that is not located on the deploy or build server. An example would be Jira that is installed on its own server and is used to manage issues that are resolved - 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 Instances defined within FlexDeploy, select Topology -> Instances from the menu.
By default, all active instances 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 Instances matching any of the specified criteria, or the All radio button to indicate that the search results should only include instances Instances matching all of the specified criteria. Click on the Reset button to return to the default search criteria form.
Creating
...
or Editing
...
Creating/Editing a Target Instance
To create a target Instance for either build or deploy click the Create button and select Instance. To edit an instance, select an existing instance and click the Edit button.
...
Enter values for the following fields.
...
Field Name
...
Required
...
Description
...
Instance Id
...
N/A
...
System generated identifier (read-only).
...
Instance Code
...
Yes
...
Short name for the instance.
...
Instance Name
...
Yes
...
Long display name for the instance.
...
Group
...
No
...
An optional group identifier which can be useful when searching for Instances.
...
SubGroup
...
No
...
An optional subgroup identifier which can be useful when searching for Instances.
...
Description
...
No
...
A description of the instance.
...
Deployment Target
...
Yes
...
Whether the instance can be deployed to. Defaults to "Yes".
...
Active
...
Yes
...
Whether or not the instance is active in the system. Defaults to "Yes".
...
...
Click the Next button to associate plugin operations to this instance. By associating plugin operations to the instance, you are indicating that any environment instance scoped properties defined for those plugin operations need to be configured for the instance across all selected environments. Likewise, any projects which reference the instance must define any associated project-scoped properties. In order to find specific plugin operations, type in Filter... text box and available Plugin Operations will be filtered accordingly.
...
Instances
Each Instance type has slightly different configuration requirements. The following links will assist in setting up Instances.
...
To create an SCM instance, click the Create button and select SCM Instance. To edit an existing instance, select an instance and click the Edit button.
Enter values for the fields as described in figure below. Selection of the SCM type dynamically prompts for properties required to for that SCM. Clicking the Test Connection button will use the values you entered to connect to the SCM instance.
Click the Save button to save the changes.
...
Field Name
...
Required
...
Description
...
Instance Code
...
Yes
...
Short name for the instance.
...
Instance Name
...
Yes
...
Long display name for the instance.
...
SCM Type
...
Yes
...
The SCM Type. Subversion, GIT, Microsoft TFS, CVS are the supported SCM Instance Types. Once SCM Instance is saved, this can not be modified.
...
Description
...
Yes
...
A description of the instance.
...
Active
...
Yes
...
Whether or not the instance is active in the system. Defaults to "Yes".
...
URL
...
Depends
...
URL to the repository (SubVersion,Git, TFS or CVS)
...
User
...
Depends
...
User name to login to the repository.
...
Password
...
Depends
...
Password to login to the repository.
Creating/Editing a Test Instance
To create a test instance, click the Create button and select Test Instance. To edit an existing instance, select an instance and click the Edit button.
Enter values for the fields as described in the table below.
...
Field Name
...
Required
...
Description
...
Instance Code
...
Yes
...
Short name for the instance.
...
Instance Name
...
Yes
...
Long display name for the instance.
...
Testing Tool
...
No
...
The testing tool that will be run on this test instance.
...
Description
...
Yes
...
A description of the instance.
...
Active
...
Yes
...
Whether or not the instance is active in the system. Defaults to "Yes".
...
Click the Next button to associate Environments to this instance.
...
Click the Save button to save the changes.
Creating/Editing an Issue Tracking Instance
To create an Issue Tracking System instance, click the Create button and select Issue Tracking System Instance. To edit an existing instance, select an instance and click the Edit button.
Enter values for the fields as described in the table below.
...
Field Name
...
Required
...
Description
...
Instance Code
...
Yes
...
Short name for the instance.
...
Instance Name
...
Yes
...
Long display name for the instance.
...
Issue Tracking System
...
No
...
The issue tracking system that will be used.
...
Description
...
Yes
...
A description of the instance.
...
Active
...
Yes
...
Whether or not the instance is active in the system. Defaults to "Yes".
...
Click the Save button to save the changes.
- 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 Instance and click the Inactivate button. This will temporarily hide that instance Instance until, a search is performed where the criteria for Active is switched to "No". To reactivate an instanceInstance, select the desired instance Instance and click the Edit button. Then change the drop down menu for active to "Yes" and click Save. This instance Instance is now active in the system again and ready for use.