Preparing for FlexDeploy POC or Implementation

Here are details of what you need to prepare for FlexDeploy Configurations for POC or Implementation.

Topology and Environments

Explain various environments, technologies (applications, middleware, database etc.) and their purpose to FlexDeploy team if working together on POC or implementation. This can be discussed during first meeting.

Source Control Details

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. 

Preparations

• Gather details of source code repository setup. Such details will be different based on type of source code repository but generally
  
  

  • URL for source code repository

  • User / Password for source control system. You can setup generic user for this purpose. User should have read and write access to source control repository.

  • Path inside repository for specific components.

• Make sure FlexDeploy server has connectivity to Source Control system. You can use ping command to make sure that you can connect to source control system host.

• You should have necessary client to interact with source code repository, so that you can modify files if necessary. This depends on type of source code repository being used.

• Some SCMs require clients to be installed on the FlexDeploy servers. SCM clients are typically not needed on EBS Development server as mostly we use Partial Deployment and file export happens on FlexDeploy server in that model.
  

Target Environment Details

Details needed for each technology would be different, so here we just talk about general preparedness.

Preparations (for each environment)

• Endpoint connectivity over SSH

  • FlexDeploy must be able to connect to Endpoint. You can use ping command to make sure that you can connect.

  • Host name or IP address

  • User & Password or Key based authentication

  • Java Home (1.7 or higher)

• Credentials (User and Password) as appropriate for target platform.

• Various folder locations for installation of application/middleware

• URL for database connectivity. For example, JDBC URL.

• Access host and port as appropriate. For example, WebLogic admin host and port.

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 an 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. https://<org_identifier>.servicenow.com should be accessible from the host where FlexDeploy is installed.

Azure Boards Integration

This is an optional integration. PAT generated in the user settings should have Work Item Read access at the very least. dev.azure.com (test connection and work item details) and *.dev.azure.com (work item search in request form) must be accessible from the host where FlexDeploy is installed for the integration to work.