Versions Compared

Old Version 1

changes.mady.by.user Copy Page Tree

Saved on

compared with

New Version 2

changes.mady.by.user Karl Henselin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

An Instance is a logical concept representing a technology running across its environment lifecyclein 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 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 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

...

There are 4 types of instances:

  1. Target Instances (often referred to as just Instance) support managing both build and Instances - represent a software technology that supports build and/or deploy.
  2. 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.
  3. 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.
  4. 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.

...