Versions Compared

Old Version 7

changes.mady.by.user Chandresh Patel

Saved on

compared with

New Version 8

changes.mady.by.user Chandresh Patel

Saved on

Key

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

Here are details of what you need to prepare for EBS Configuration Deployments POC with FlexDeploy. EBS Supported objects reference can be found at Supported EBS Object Types.

EBS

...

  • We need to configure User Id and Password on endpoint (we can use SSH Keys as well).

  • User Id is same as what EBS processes are running as on target server.
  • This would be needed for each EBS installation where you want to perform Builds or Deployments.

...

  • Password for apps user
  • This would be needed for each EBS installation where you want to perform Builds or Deployments.

EBS Topology

Explain various EBS environment and their purpose to FlexDeploy team if working together on POC or implementation. This can be discussed during first meeting.

Source Control Details

Here is the recommended structure in repository - Source Control Folder Structure. Be ready to share source control folder structure with FlexDeploy team if working together on POC or implementation. Subversion, Git, Microsoft TFVC, Perforce, CVS, PVCS etc. are supported out of box. 

...

  • Password for apps user.
  • Path of EBS Source script. see Deploy EBS for more details. This would be environment script on application tier nodes. (for example, /u1/apps/apps_st/appl/APPSorcl_ebs01.env)
  • User Id and Password for UNIX user that is used to copy files on application tier nodes. This is generally applmgr or something similar to that. Alternatively, we can use SSH Key based communication as well if password is not known or not desired.
    • Make sure FlexDeploy server has connectivity to application tier node. You can use ping command to validate this.
  • Java Home. For example, /u01/install/APPS/apps/tech_st/10.1.3/appsutil/jdk/jre/. There should java executable in bin sub-folder. We can use same Java as used by EBS processes.
  • Temporary directory for FlexDeploy. We can use default /var/flexdeploy as well.

Active Directory or LDAP Integration

This is optional integration. See Realms for more details. You will need read only system user for setup along with details of user and group locations.

ServiceNow Integration

This is optional integration. You will need read only user to access ServiceNow from FlexDeploy. As part of setup, we will enter user and password for ServiceNow in FlexDeploy instance.