...
- EBS Custom Top on R12.1 or R12.2 instance. You should know name of custom top. For example, XXHR. We will need this to configure FlexDeploy.
- Source Control repository setup with sample EBS Objects. Here is the recommended structure in repository - Source Control Folder Structure.
- You can use Subversion, Git, TFVC, Perforce, CVS etc.
- EBS Supported objects reference can be found at Supported EBS Object Types.
- You should have necessary client to interact with Source Control, so that you can modify files during POC.
- EBS Endpoint details
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.
- EBS Installation details
- Password for apps user
- Location of EBS Source script. see Deploy EBS for more details.
- This would be needed for each EBS installation where you want to perform Builds or Deployments.
- If you are using Git, make sure that Git 1.7.9 or higher is installed on FlexDeploy server. Git is not needed on EBS Development server as mostly we use Partial Deployment and file export happens on FlexDeploy server in that model.