Customizing components

This topic explains how to customize the application design components in Accessing the application design. It is assumed that you are not working in a virtual environment.

Customizing the existing serveer

Perform the following steps to customize the existing server component:

1. Click the existing server component.

2. On the Properties tab, enter the following information:

   Field	Description
   Name	Name of the server. This is typically the name of one of the two Ubuntu systems specified in Prerequisites.
   HOST-FQDN	Complete FQDN name of the server
   Modifiable during service creation	Select this check box if you want to update the FQDN during deployment. For more information about this, see the Codar online help.
   IP ADDRESS	IP address of the Ubuntu system
   PASSWORD	Password of the Ubuntu system
   SSH PORT	Port number for the application server and database to connect to this Ubuntu system. The default port is 22.
   PRIVATE KEY	Private key for secure SSH access
   USER NAME	User name for whom SSH access must be granted to this Ubuntu system. For example, root

   Customizing the second existing server

   Perform the following steps to customize the application server component:

   1. Click the existing server component.

   2. On the Properties tab, enter the following information:

      Field	Description
      Name	Name of the server. This is typically the name of the second Ubuntu systems specified in Prerequisites.
      HOST-FQDN	Complete FQDN name of the server
      Modifiable during service creation	Select this check box if you want to update the FQDN during deployment. For more information about this, see the Codar online help.
      IP ADDRESS	IP address of the second Ubuntu system
      PASSWORD	Password of the second Ubuntu system
      SSH PORT	Port number for the application server and database to connect to this Ubuntu system. The default port is 22.
      PRIVATE KEY	Private key for secure SSH access
      USER NAME	User name for whom SSH access must be granted to this Ubuntu system. For example, root

   Customizing MySQL

   

   Perform the following steps to customize the MySQL component:

   1. Click the MySQL component.

   2. On the Properties tab, enter the following information:

      Field	Description
      Name	Name of the database.
      artifactPassword	Enter the password for accessing the HTTP location. This is an optional field.
      Modifiable during service creation	Select this check box if you want to update the password during deployment. For more information about this, see the Codar online help.
      artifactURL	HTTP location where the MySQL database is located. That is, the location where mysql-server_5.6.22-1ubuntu12.04_amd64.deb-bundle.tar is located
      artifactUsername	Name of the user who accesses the HTTP location
      configurationUrl	HTTP location in which install_mysql.sh is located. For example, http://localhost:80/scripts/install_mysql.sh
      installPath	Path in which MySQL or Tomcat is installed. This is an optional field.
      privatekeyPath	Key to connect to MySQL. This is an optional field.
      remoteFilePath	Remote file path in which the files must be copied to the Ubuntu server.
      serviceCommand	sh install_mysql.sh
      sshPort	Enter 22 as the SSH port number.

   Customizing Tomcat

   

   Perform the following steps to customize the Tomcat component:

   1. Click the Tomcat component.

   2. On the Properties tab, enter the following information:

      Field	Description
      Name	Name of the Tomcat server.
      artifactPassword	Enter the password for accessing the HTTP location. This is an optional field.
      Modifiable during service creation	Select this check box if you want to update the password during deployment. For more information about this, see the Codar online help.
      artifactURL	HTTP location where the Tomcat server is located.
      artifactUsername	Name of the user who accesses the HTTP location
      configurationUrl	HTTP location in which install_tomcat.sh is located. For example, http://localhost:80/scripts/install_tomcat.sh
      installPath	Path in which MySQL or Tomcat is installed. This is an optional field.
      privatekeyPath	Key to connect to Tomcat. This is an optional field.
      remoteFilePath	Remote file path in which the files must be copied to the Ubuntu server.
      serviceCommand	sh /tmp/install_tomcat.sh
      sshPort	Enter 22 as the SSH port number.

Customizing the PetClinic DB Conf component

Perform the following steps to customize the PetClinic DB Conf component:

1. Click the PetClinic DB Conf component.

2. On the Properties tab, enter the following information:

   Field	Description
   Name	Name of the component. That is, PetClinic DB Conf
   artifactPassword	Enter the password for accessing the HTTP location. This is an optional field.
   Modifiable during service creation	Select this check box if you want to update the password during deployment. For more information about this, see the Codar online help.
   artifactURL	HTTP location where the PetClinic DB Conf is located.
   artifactUsername	Name of the user who accesses the HTTP location
   configurationUrl	HTTP location in which install_tomcat.sh is located. For example, http://localhost:80/scripts/mysqldb_conf.sh
   installPath	Path in which MySQL or Tomcat is installed. This is an optional field.
   privatekeyPath	Key to connect to Tomcat. This is an optional field.
   remoteFilePath	Remote file path in which the files must be copied to the Ubuntu server.
   serviceCommand	sh /tmp/mysqldb_conf.sh
   sshPort	Enter 22 as the SSH port number.

Customizing the PetClinic Application component

1. Click the PetClinic Application component.

2. On the Properties tab, enter the following information:

   Field	Description
   Name	Name of the component. That is, PetClinic Application
   artifactPassword	Enter the password for accessing the HTTP location. This is an optional field.
   Modifiable during service creation	Select this check box if you want to update the password during deployment. For more information about this, see the Codar online help.
   artifactURL	HTTP location in which petclinic.war is located
   artifactUsername	Name of the user who accesses the HTTP location
   configurationUrl	HTTP location in which petclinic_jdbc_conf.sh is located http://localhost:80/scripts/petclinic_jdbc_conf.sh
   localfilepath	Path in which petclinic.war is located. This is an optional field.
   port	Enter 22 as the port number.
   privatekeyPath	Key to connect to petclinic.war. This is an optional field.
   remoteFilePath	/tmp
   serviceCommand	sh /tmp/petclinic_jdbc_conf.sh