Question: What is xDA?

Answer: xDA (xCP Deployment Agent) is a lightweight spring-boot application used for xCP application deployment. xDA allows registration of manually provisioned environments and deploy xCP applications to one of the environments.

 

Question: How about xDA compatibility with previous version of xCP release?

Answer: xDA is a component in xCP stack for xCP 2.3 release which replaces xMS Agent from xMS release that was used for deploying applications with previous versions of xCP release.

xDA and xDA Tools are compatible with xCP 2.3 release and provides feature parity with xMS Agent whereas xMS Agent and xMS tools are compatible with xCP 2.2 and earlier.

 

Question: Is xDA supported on non-windows platform?

Answer: Yes, xDA is supported on RHEL Linux, IBM AIX and Oracle Solaris.

 

Question: Can xDA be installed on Windows Client operating systems?

Answer: xDA can be installed and run on any client machine along with xCP Designer provided there are enough hardware resources to support both the applications

 

Question: xDA is certified for which Oracle Java?

Answer: xDA is certified with Java 7 and Java 8.

 

Question: Does xDA needs to be installed on an application server?

Answer: No. xDA is a spring-boot based standalone application (which packages an inbuilt app server to host the application); there is no explicit dependency on the application server.

 

Question: What is xDA tools and how is it different from xMS tools?

Answer: xDA Tools is a command-line interface (CLI) and it connects to xDA to configure xDA and deploy xCP application.

  • xDA tools is only for connection to xDA to configure xDA or to deploy xCP application and it doesn’t contain script to install xMS Server.
  • xDA tools does not have xMS Server provisioning related blueprints, environment profile, upgrade plans and properties files.

Question: What benefits and improvements xDA provides over xMS Agent?

Answer:

  1. xDA being a spring-boot based standalone application (which packages an inbuilt app server to host the application) reduces the TCO on xCP.
  2. xDA supports registering multiple manually provisioned environments. Deployment can be performed on one of the registered environments. This removes the limitation of one to one mapping of xMS Agent and registered xCP environment.
  • Designer UI supports selecting one of the multiple environments registered in xDA for deployment. The user can select the target xDA environment from xCP Designer to deploy the application.
  • CLI from xDA tools also supports multiple environments by exposing a parameter to specify the environment name.

     3. xDA configurations (in xda-config.properties) support externalising the catalog folder, changing startup port, loading         libraries of JBoss/WebSphere/Weblogic.

Question: What is the quick synopsis of the steps user should perform in xDA before starting application deployment?

Answer:

  1. Install and Configure xDA- Refer section Installing the xCP Deployment Agent in xCP 2.3 Deployment Guide.
  2. Register xCP environment in xDA catalog from xDA Management Center- Refer section Using the xDA Management Center to Register an Environment in xCP 2.3 Deployment Guide.
  3. Synchronize the environment- Refer section Synchronizing a Manually Provisioned Environment in xCP 2.3 Deployment Guide.

 

Question: Is xDA context name fixed?

Answer: Yes xDA context name is fixed as xda. User should always access xDA URL as <protocol>://<host/IP>:<port>/xda

 

Question: Is Validate Environment mandatory for application deployment?

Answer:

  • “Validate Environment” validates the services with registered endpoints viz. the URL and ports and shows the status as passed or failed accordingly. This is helpful for user in case any wrong/invalid endpoint port is entered and user can correct it before going for Synchronize Environment.
  • Validate Environment is not mandatory and helps to check and confirm if the endpoints details are entered properly from xDA Management Center. It is independent of Synchronize Environment; user can skip validation and synchronize a completely registered environment to make it ready for application deployment.

Question: What are the steps/pre-requisites I need to perform/confirm from xDA perspective to ensure that environment is ready for application deployment?

Answer:

  1. Ensure all the relevant endpoints are entered correctly from xDA Management Center UI. Disable the services which do not form part of your manually provisioned xCP environment.

On successful registration of environment, the environment status would be Registered else it would be seen as Registration Incomplete.

     2. On status as Registered, Select the environment and Click on Maintenance button and synchronize the environment by    clicking on Synchronize Environment button

The intermediate environment status during synchronize will be Maintenance which on successful synchronization would be seen as Provisioned.

The status as Provisioned on UI is saved as environment state Ready in xDA catalog and suggests the environment is READY for application deployment. This Ready environment is validated by xCP to start application deployment.

 

Question: Can I deploy xCP application using xDA tools CLI other than xCP Designer?

Answer: Yes, deploy-xcp-application command from xMS CLI can be used to deploy the application.

For model-only deployment, specify the path, including the file name, to the artifact_bundle JAR file and set the repositoryservicesonly parameter value as true.

 

Question: What are the logs required to analyze application deployment failure?

Answer: For deployment failures, check the runapp.log from xCP Designer and xda.log and xda-full.log from xDA logs.

To enable DEBUG logging, change the configurations under “Configuring loggers for Builder code” section in log4j.properties file located at ${xda-home}\config to “DEBUG”.

 

Question: Can xDA be used to deploy xCP 2.2 applications?

Answer: No, use xMS Agent 1.2 patch to deploy xCP 2.2 applications. xCP Deployment Agent 2.3 can be used to deploy xCP 2.3 applications only on xCP 2.3 application hosts.

 

Question: Can I backup and restore xMS Agent catalog when upgrading to xCP 2.3?

Answer: xMS templates, environments and catalog are not compatible with xDA.

So users upgrading to xCP 2.3 should not attempt to restore xMS catalog in xDA and should register the upgraded xCP environment in xDA freshly by following steps in Installing the xCP Deployment Agent and Using the xDA Management Center to Register an Environment sections in xCP Deployment Guide. This is a one-time activity.

 

Question: Can xMS Server be used to provision xCP 2.3 environments automatically?

Answer: No, you can build xCP 2.3 environments through the manual mode only. xMS Server provisioning in fully automated or orchestrated provisioning mode is not supported to provision xCP 2.3 environments.