Starting BMC Compact RDS

Use the following procedures to start the BMC Compact RDS.

• • Before you begin
  • To add VMs to a customer network
  • To power on BMC Compact RDS
  • Steps to perform after you power on the Single VM RDS
  • Contents of CLM startup script
  • BMC Compact RDS start and stop scripts
  • Using the change script to change the hostname
    • Prerequisites
    • To run the hostname change script
  • Where to go from here

Before you begin

After you deploy the OVF, do not change the IP of the server if it is DHCP-enabled.

To add VMs to a customer network

1. Obtain the following IP and DNS information from the customer for assignment to the BMC Compact RDS. 
   This information will likely be a pool of static IP addresses for use with the appliance. 
   1. Pool of static IP addresses for the virtual appliance 4.0 image
   2. Subnet mask address
   3. Default gateway address
   4. Primary DNS server
   5. Secondary DNS server
   6. Tertiary DNS server
   7. Domain name (DNS Search Path)—for example, bmc.com
2. Log on to the vSphere client with administrator privileges.
3. Select the VM, select Edit Virtual Machine Settings, and then select the Network Adapter device.
4. Clear the Network Adapter statuses of Connected and Connect at Power On.  
   This action saves time when starting the VM. The configured Network Adapter is unlikely to start otherwise, because it is assigned to a BMC network when it is delivered.
5. Right-click the selected VM and select Power On.
6. After the computer is powered on, log on as the root user.
7. From the command prompt, update or create /etc/sysconfig/network-scripts/ifcfg-eth0:
   1. Assign/update the IP, Subnet Mask, DNS and Default Gateway obtained from the customer.

   2. Save the file.

      Note

      For static IP assignment, contact your administrator, and see the online Help if you encounter a problem.

8. After completing the configuration changes, restart Network Services  using "service network restart" and then reset the Network Adapter device status to Connected and Connect at Power On.
9. To complete the changes, perform one of the following tasks:
   • Restart the VM
   • Open a terminal window and restart the network service by issuing service network restart from the prompt. Issue the ifconfig command to verify that eth0 configuration changes have taken place and that the IP information is correct.

To power on BMC Compact RDS

1. Log on to the vSphere client with administrator privileges.
2. Right-click the selected VM and select Power > Power On.
   
3. After the computer is powered on, log on to BMC Compact RDS as the root user (the default password is x33+esaC).

Steps to perform after you power on the Single VM RDS

1. Update the /etc/hosts file so that the VM host name and IP addresses assigned to the VM are correct.
   The following update comments out the second line for the loopback address and inserts the IP address of the VM in the cloudexpress line. 

   127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
   #::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
   172.19.141.201  cloudexpress
2. Restart the cloudexpress VM.

3. (Optional) Change the time zone of the VM to its correct location.
   The following example changes the time zone of the VM from IST to PST by linking PST to the local time of the VM:

   # date
   Wed Apr 10 07:49:37 IST 2014
   # ls -l local*
   -rw-r--r--. 1 root root 2819 May 14 14:54 localtime
   # mv localtime localtimeORIGINAL
   # ln -s /usr/share/zoneinfo/US/Pacific localtime
   # date
   Thu Apr 10 12:50:04 PDT 2014
    
    

4. Ensure that the database is running and that you can connect to the database instance:

   To start the Oracle instance, enter the following commands:

   su - oracle
   sqlplus / as sysdba
   startup
   exit
   lsnrctl start
   exit

   To determine whether Oracle is running, enter the following command:

   ps -ef | grep -i Ora

5. Start the BMC Cloud Lifecycle Management services by using the  /u01/Start_CLMServices.sh shell script.
   For example:

   # cd /u01
   # ./Start_CLMServices.sh

   The /u01/Start_CLMServices.sh shell script starts all the CLM services. Or run /u01/Stop_CLMServices.sh to stop all the CLM services.

   Note

   To start and stop individual applications, see BMC Compact RDS start and stop scripts.

6. Verify that you can connect to the Single VM RDS application URLs for the BMC Remedy Mid Tier, BMC Network Automation, and BMC Atrium Orchestrator:

   Application	URL	Logon ID and password
   BMC Remedy Mid Tier	http://cloudexpress:8080/arsys	Demo/clmAdm1n
   BMC Network Automation	https://cloudexpress:11443	sysadmin/clmAdm1n
   BMC Atrium Orchestrator Platform	http://cloudexpress:7070/baoam	admin/clmAdm1n

7. (Optional) Install the following client components on a computer running Windows 2008 R2.
   You can find installer in cloudexpress downloaded repository/share location.
   • BMC for Server Automation RCP Console—Installation is optional because the console is installed by default with the cloudexpress VM.
   • BMC Remedy Developer Studio

8. Use the following URLs to verify that you can access the mid tier object list (so that you can search any form on the BMC Remedy AR System server):
   http://cloudexpress:8080/arsys/forms
   

   or

   http://cloudexpress:8080/arsys/forms/cloudexpress 
   

   
   

   Specify the Demo/clmAdm1n credentials while accessing the object list.

9. Log on to the mid tier as the Demo user and add the licenses for the BMC Remedy AR System server.
   You can obtain licenses from www.bmc.com/support with a valid user name and password.
10. Add the permanent BMC Remedy AR System license to the BMC Remedy AR System server.
    A temporary one-month floating license is provided out of the box.
    1. Navigate to the BMC Remedy AR System Administrator Console (Applications > AR System Administrator > AR System Administrator Console).
    2. Navigate to the Add or Remove Licenses form (System > General > Add Remove Licenses). 
        
    3. Use the license key to add the license to the server. 

11. Install and license the RSCD Agent for Virtual Center. 
    Sysprep files are required on Virtual Center. For example, you would need the C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\sysprep folder to provision the Windows svr2003 (32-bit and 64-bit), Windows xp (32-bit and 64-bit), and Windows 2k operating systems. The respective paths differ, based on the operating systems, as well as the Virtual Center version and installation directory, as shown in the following figures:

    
    
    
    
    

12. Open the exports file and update it with the following setting:
    rw,user=administrator

13. In BMC Developer Studio, disable the following filters on the AR System server to improve system performance:
    CMF:DHB:SendDSO-CAR-HeartBeat-DSOtoEAR
    CMF:DHB:SendDSO-EAR-HeartBeat-DSOtoCAR_050
    CMF:DRH:SendDPE-CAR-PendingError-DSOtoEAR
    CMF:DRH:SendRE-CAR-PendingErrorToEAR
    CMF:DRH:UpdateDSO-EAR-HeartbeatCheck_050
    CMF:DRH:UpdateRE-CAR-HeartBeatCheck-DSOtoEAR
    CSM:DSO:BMC_ComputContainer_Filter
    CSM:DSO:BMC_FunctionalComponent_Filter
    CSM:DSO:ResourceSet_Filter
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_Cluster_DSO
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_Component_DSO
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_Component_HostedSystemComponents_DSO
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_ComputerSystem_DSO
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_ConcreteCollection_DSO
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_ContractLine_C_DSO
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_ContractLine_DSO
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_ContractLine_MM_DSO
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_Dependency_DSO
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_Dependency_TaggedWith_DSO
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_Document_DSO
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_HardwareSystemComponent_Memory_DSO
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_HardwareSystemComponent_Processor_DSO
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_Organization_MM_DSO
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_Price_DSO
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_ResourcePool_DSO
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_ServiceOfferingInstance_DSO
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_Tag_DSO
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_VirtualSystemEnabler_DSO
    DIST-CMDB:CLOUD_TO_ECMDB-BMC_VirtualSystemSettingData_DSO

     

Contents of CLM startup script

The /u01/Start_CLMServices.sh shell script starts all the CLM services.

BMC Compact RDS start and stop scripts

You can start and stop individual BMC Compact RDS applications with the following scripts. Some scripts might be already configured to start with the VM during the initial startup. All scripts are started when you run the /u01/Start_CLMServices.sh shell script.

Using the change script to change the hostname

Use the hostname change script to modify the hostname of the VM from cloudexpress to an assigned hostname. This script updates the /etc/hosts file and performs database and application changes with the new hostname.

Prerequisites

1. After you successfully deploy the OVF, power on the VM.
2. In the vSphere client, change the hostname of the VM from cloudexpress to the assigned name.
3. Update /etc/sysconfig/network and /etc/sysconfig/netowrk-scrips/ifcfg-eth0 with the new hostname.
4. Update the IP address details in ifcfg-eth if you plan to assign a static IP address.
   This step is optional if you plan to assign a dynamic IP address.
5. Temporarily set the HOSTNAME=<newhostname> environmental variable.
   For example:
   export HOSTNAME=<newhostname>
6. Clear the cloudexpress entry in /etc/hosts.
7. If any CLM services are running, use /u01/Stop_CLMServices.sh to stop all CLM services.

To run the hostname change script

1. Run the configChange.sh script (under the /u01/hostnamechange folder).
   The scripts updates the hostname and automatically reboots the VM.
2. After the VM is started, run the serviceConfig.sh script (under the /u01/hostnamechange folder).
3. When you see the All services are started and ready to be used with new hostname message displayed, log on to BMC Atrium Orchestrator.
4. Click the Manage tab, and then click the Adapters tab.
5. Select ARSAdapter.
    
6. Click Switch to XML View.
7. Review the warning and then click Switch View.

8. Replace <target>cloudexpress</target> with <target>newHostName</target>.
   For example:
   

   <config>
    <target>newHostName</target>
    <port>0</port>
    <user-name>orchestrationuser</user-name>
    <password>aouser</password>
    <use-connection-pooling>true</use-connection-pooling>
    <max-connections>20</max-connections>
   </config>

    

9. Click OK, and then log out of BMC Atrium Orchestrator. 

Where to go from here

Operating system and application logon accounts (to log on to the BMC Compact RDS operating system and applications)

Configuring BMC Server Automation