How to Deploy Axon on VMware vcenter

Size: px

Start display at page:

Download "How to Deploy Axon on VMware vcenter"

Felix Flynn
6 years ago
Views:

How to Deploy Axon on VMware vcenter Copyright Informatica LLC

Big Data Mangement, and Live Data Map are trademarks or registered

1 How to Deploy Axon on VMware vcenter Copyright Informatica LLC Informatica, the Informatica logo, Intelligent Data Lake, Big Data Mangement, and Live Data Map are trademarks or registered trademarks of Informatica LLC in the United States and many jurisdictions throughout the world. A current list of Informatica trademarks is available on the web at

2 Abstract This document describes how to deploy the Axon vapp on VMware vcenter using the vsphere desktop client. Supported Versions Informatica Axon Informatica Axon HotFix 1 Table of Contents Overview Prerequisites Deploying Axon Post Deployment Increase the Number of CPUs Power On the vapp Assign a Static IP Upgrade VMware Tools Extend the Root Partition Disk Space Modify the Gateway Configuration File Add License Information Log in to Axon Troubleshooting Overview Informatica Axon is a knowledge repository and data governance tool. You can deploy Axon as a VMware vapp. After deployment, you can access Axon from a web browser in the same network where you have deployed the vapp. Prerequisites Before you deploy Axon, ensure that you have the following deployment components available: vcenter Server Your VMware infrastructure must be running vcenter server version You must have vsphere client version installed to manage your virtual machines. ESXi Host Your vcenter server must contain an ESXi host. Informatica recommends that the ESXi host is in a cluster. Axon Open Virtualization Appliance (OVA) File The Axon OVA file consists of a manifest, Open Virtualization Format (OVF) and Virtual Machine Disk (VMDK) file. You deploy the OVA file as a vapp using the vsphere client. 2

The configuration of the Axon OVA file is: Component Disk Memory Specification 64 GB 16 GB CPU Cores 4 The system settings of the ESXi host must support the configuration of the Axon vapp.

3 The configuration of the Axon OVA file is: Component Disk Memory Specification 64 GB 16 GB CPU Cores 4 The system settings of the ESXi host must support the configuration of the Axon vapp. You can modify the configuration of the Axon virtual machine after deployment. Deploying Axon You deploy the Axon OVA file using the VMware vsphere desktop client. The Axon OVA file deploys as a vapp in the WMware vcenter server. 1. Copy the Axon OVA file to the host system where the vsphere desktop client is installed. 2. Open the vsphere desktop client and connect to the vcenter server of your organization. 3. Select the cluster where you want to deploy the Axon vapp. 4. From the File menu, click Deploy OVF Template. 3

4 The Deploy OVF Wizard opens. 5. In the Source step, select the location of the Axon OVA file, and click Next. 4

5 6. In the OVF Template Details step, verify the details of the Axon OVA file, and click Next. 5

6 7. In the Name and Location step, enter a name for the Axon vapp. Select the data center where you want to deploy the Axon vapp, and click Next. 6

7 8. In the Resource Pool step, select the cluster where you want to deploy the Axon vapp, and click Next. 7

8 9. In the Storage step, select a data store for the Axon vapp, and click Next. 8

9 10. In the Disk Format step, verify the information, and click Next. 9

10 11. In the Network Mapping step, select the network resource where you can configure a static IP after deployment, and click Next. 10

12. In the Ready to Complete step, review the deployment information, and click Finish. The deployment task begins. Post Deployment Perform the following tasks after you deploy Axon: 1.

11 12. In the Ready to Complete step, review the deployment information, and click Finish. The deployment task begins. Post Deployment Perform the following tasks after you deploy Axon: 1. Increase the number of CPUs from four to eight. 2. Power on the vapp to start the Axon virtual machine. 3. Assign a static IP using the console. 4. Upgrade VMware tools that is installed on the Axon virtual machine. 5. Optionally, extend the root partition disk space. 6. Modify the gateway configuration file to enable notifications. 7. Access Axon from a web browser. 11

Increase the Number of CPUs Use the vsphere client to increase the number of CPUs to eight. The total number of cores must be equal to or less than the total number of logical CPUs on the host server.

12 Increase the Number of CPUs Use the vsphere client to increase the number of CPUs to eight. The total number of cores must be equal to or less than the total number of logical CPUs on the host server. 1. In the vsphere client, click the Axon virtual machine. 2. In the Summary tab, click Edit virtual machine settings. 3. Select CPUs in the Hardware tab. 4. Change the value of the Number of virtual sockets and Number of cores per socket to obtain 8 as the total number of cores. 5. Click OK. Power On the vapp Power on the vapp to boot the virtual machine that runs Axon. 1. In the vsphere desktop client, select the vapp that you deployed and right click. 12

13 2. Click Power On to boot the Axon virtual machine. 13

14 Assign a Static IP The Axon virtual machine does not have an IP address assigned to it. Assign a static IP address using the vsphere console. 1. Right click the Axon virtual machine that is available in the vapp that you deployed. Click Edit Settings and then select the Network adapter component. Note the MAC address of the virtual machine. 14

$Use the following password to log in as root: "Y9=/(.Q@&4\Fwa 4.$

15 2. Right click the Axon virtual machine, and click Open Console. 3. Log in to the virtual machine from the console using the root credentials. Use the following password to log in as root: 4. Type the following command to view the network configuration of the Axon virtual machine: 15

16 ifconfig -a 5. Go to the network scripts directory using the following command: cd /etc/sysconfig/network-scripts 6. Edit the eth1 file using the following command: vi ifcfg-eth1 If the ifcfg-eth1 does not exist and you have a eth0 file instead, type the following commands to copy the settings of the eth0 file to the eth1 file and delete the eth0 file: cp ifcfg-eth0 ifcfg-eth1 rm ifcfg-eth0 7. Update the network details for the eth1 file. The following table lists the settings that you must update: Setting NAME Value Change to eth1 if your deployment had a eth0 file. HWADDR MAC address of the virtual machine that you noted in step 1. GATEWAY DNS1 DNS2 Gateway address of your network. First DNS address of your network. Second DNS address of your network. 16

17 Setting DEVICE NETMASK IPADDR Value Change to eth1 if your deployment had a eth0 file. Subnet mask of your network. Static IP that you want to assign to the virtual machine. 17

8. Add the persistent static route using the following command: route add -net 0.0.0.0 gw 10.65.x.x dev eth1 Note: Replace 10.64.x.x with the gateway details of your network. 9.

update: Setting HOSTNAME GATEWAYDEV GATEWAY Value Hostname of the the virtual machine Change the value to eth1 if it is eth0 Specify the gateway details of your network 10.

18 8. Add the persistent static route using the following command: route add -net gw x.x dev eth1 Note: Replace x.x with the gateway details of your network. 9. To persist the gateway details across the virtual machine reboots, run the following command to edit the network file: vi etc/sysconfig/network The following table lists the settings that you must update: Setting HOSTNAME GATEWAYDEV GATEWAY Value Hostname of the the virtual machine Change the value to eth1 if it is eth0 Specify the gateway details of your network 10. Restart the network services using the following command: service network restart 11. To access the virtual machine using SSH, you must update the SSH daemon configuration file. Run the following command to edit the SSH daemon configuration file: vi /etc/ssh/sshd_config The following table lists the settings that you must update: Setting PermitRootLogin PasswordAuthentication Value yes yes 18

19 12. Restart the SSH daemon using the following command: service sshd restart 19

Upgrade VMware Tools You can optionally upgrade the version of VMware tools that is installed on the Axon virtual machine. VMware tools helps you manage the virtual machine easily.

20 Upgrade VMware Tools You can optionally upgrade the version of VMware tools that is installed on the Axon virtual machine. VMware tools helps you manage the virtual machine easily. Before you begin, you must assign a static IP to the virtual machine. You should be able to log in to the virtual machine from another computer via Putty using SSH. 1. Verify if you need to upgrade the version of VMware tools. The following image shows the message that is displayed in the vsphere console if you need to upgrade VMware tools: 2. Right click the Axon virtual machine and select Guest. Select Install/Upgrade VMware Tools. 20

21 3. In the Install/Upgrade Tools dialog box, select Interactive Tools Upgrade and click OK. 21

$Use the following password to log in as root: "Y9=/(.Q@&4\Fwa 6.$

22 4. Start Putty on another computer and enter the IP address and port number of the virtual machine to connect to it. Click Open. 5. Log in to the virtual machine using the root credentials. Use the following password to log in as root: 6. Run the following command to mount the VMware tools drive: mount /dev/cdrom /media 7. Run the following command to untar the VMware tools installer: tar -zxf /media/vmwaretools-*.tar.gz -C /tmp 22

After the installation is complete, run the following command to delete the installer: rm -rf /tmp/vmware-tools-distrib

23 8. Run the following command to start the upgrade of the VMware tools: /tmp/vmware-tools-distrib/vmware-install.pl --default 9. After the installation is complete, run the following command to delete the installer: rm -rf /tmp/vmware-tools-distrib Extend the Root Partition Disk Space The Axon virtual machine ships with 64 GB of thick provision and 16.5 GB of thin provision disk space. You can extend the space of the root volume. This is an optional task. 1. Power on the Axon virtual machine. 23

$2. Connect to the virtual machine using Putty via SSH. 3. Log in using the root credentials. Use the following password to log in as root: "Y9=/(.Q@&4\Fwa 4.$

24 2. Connect to the virtual machine using Putty via SSH. 3. Log in using the root credentials. Use the following password to log in as root: 4. Use the following command to see the current disk usage: fdisk -l 5. Create new partitions with the available free space using the following command: fdisk /dev/sda 24

25 6. Add the partition using the following command: partx -v -a /dev/sda 7. Create a physical volume on the disk and extend the volume group using the following command: pvcreate /dev/sda3 8. Check the updated information using the following command: pvscan 25

26 9. Increase the size of the logical volume using the following command: lvextend -l +100%FREE /dev/vg_centsos6464bit/lv_root 10. Extend the filesystem on the logical volume using the following command: resize2fs /dev/vg_ccentos64b64bit/lv_root 11. View the new size using the following command: df -h Modify the Gateway Configuration File The Axon virtual machine ships with an gateway that is different from gateway of your organization. You must update the gateway configuration file for notifications to work correctly. 1. Log in to the Axon virtual machine using Putty via SSH. 2. Change the path to the following directory: /opt/axon/app/config/ 3. Edit the following gateway configuration file: parameters.yml 4. Modify the following parameters in the yml file: Parameter host mailer_transport mailer_host mailer_user mailer_password Value hostname of your Axon virtual machine in the following format: Type of server, for example: gmail server name. For example, smtp.gmail.com server user name. For example, server password. For example, =m8k8)kpz mailer_port server port. For example, 465 disable_delivery false 5. Execute the following script to clear the caches and use the new configuration: /home/centos/masterlesspuppet/modules/profiles/files/deployment_scripts/axoncore-full-etl.sh 26

27 Add License Information You must copy the license file provided by Informatica to the Axon vapp. The licence file specifies the duration for which your deployment of Axon is valid. 1. Power on the Axon virtual machine. 2. Connect to the virtual machine using Putty via SSH. 3. Log in using the root credentials. Use the following password to log in as root: 4. Copy the Axon license file to the following location: /opt/licence/ 5. Edit the following file: /etc/php.d/zendguardloader.ini a. In the zend_loader.enable line, change the value from 0 to 1: zend_loader.enable=1 b. Add the property, zend_loader.license_path, to specify the path to the directory where you have copied the license file. For example, if axon.zl is the license file name, add the following line: zend_loader.license_path=/opt/license/axon.zl c. Save the zendguardloader.ini file. 6. Enter the following command to restart the webservice: service httpd restart Log in to Axon You can log in to Axon from any web browser which is in the same network as the IP that you assigned to the Axon virtual machine. 1. Open a web browser. 2. In the address field, enter the URL in the following format: http[s]://<publicip>/ 3. Your deployment of Axon may not require a HTTP username and password to log in. If you are asked for a HTTP username and password, contact Informatica. 4. Click Login and use the following credentials to log in to Axon: Your root@diaku.com Your Password: changeme 27

28 Troubleshooting You might encounter errors during deployment or after deployment. The following table describes a few of the problems that you might encounter and how you can resolve them: Error The vsphere Client displays an error, "The OVF package is invalid and cannot be deployed" when you try to deploy the Axon OVA file. The Unison screen flickers after you log in. Resolution This error is because of a mismatch in the version of SHA. Perform the following steps to deploy the vapp if you see this error: 1. Uncompress the OVA file using a utility such as 7zip. 2. Delete the manifest file from the folder that contains the uncompressed files. 3. Deploy the OVF file from the folder that contains the uncompressed files. Click any Axon facet or resize the browser window to stop the flickering. Author Pratap J Lead Technical Writer 28

How to Administer the Axon vapp

How to Administer the Axon vapp Copyright Informatica LLC 2017. Informatica, the Informatica logo, Intelligent Data Lake, Big Data Mangement, and Live Data Map are trademarks or registered trademarks of