Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Starting BMC Small RDS

Use the following procedures to start the BMC Small RDS.

Before you begin

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

Powering on VMs

You must power on the virtual machines in the following order. Some of these pre-configured VMs require started applications before they can be powered on.  Following the sequence as shown starts the required applications in the required order. 

  1. BMC Atrium Orchestrator (clm-bao)
  2. BMC Server Automation (clm-bsa)
  3. BMC Network Automation (clm-bna)
  4. BMC BladeLogic Preboot Execution Environment (PXE) (clm-pxe)
  5. BMC Remedy AR System (clm-ar)
  6. BMC Cloud Platform Manager (OSGi) (clm-pm)
  7. BMC Remedy AR System Mid Tier (clm-mt)
  8. BMC Atrium Web Services (clm-aws)
  9. BMC Capacity Optimization (clm-bco)

Follow the same sequence when restarting the CLM services. 

To add VMs to a customer network

Note

If you are placing the BMC RDS into a customer network, you might need this procedure. However, in some cases, the environment might be isolated and can run as delivered.

  1. Obtain the following IP and DNS information from the customer for assignment to the BMC RDS VMs. 
    This information will likely be a pool of static IP addresses for use with the appliances. 
    1. Pool of static IP addresses for the virtual appliance 4.0 images
    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, right-click the VM, select Open Console, and then log on as the root user.
  7. From the console, select System > Administration > Network.
  8.  From the Devices tab of the Network dialog:
    1. Select the eth0 device and then select Edit from the toolbar. 

    2. Select the Static IP assignment option, and then add the IP, Subnet Mask, and Default Gateway obtained from the customer. 

      Note

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

    3. Click OK to close the dialog box.
    4. Select the DNS tab and enter the DNS information you obtain from the customer.
    5. Click File > Save to save the configuration changes.
  9. After completing the configuration changes, reset the Network Adapter device status to Connected and Connect at Power On.
  10. 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.
  11. Complete these steps for all the delivered images. 

Steps to perform after you power on the Single VM RDS

To check the availability of DHCP and DNS

In BMC Small RDS, the integration uses csm-*** hostnames. Therefore, perform the following steps: 

  1. Make sure that the VMs after deployment are reachable with the csm-*** virtual hostnames even though the actual hostnames of the VMs are clm-***. This is because all the integrations are carried using csm-***. User can make the required changes in the DNS before deployment if the IPs are static or after deployment. User needs to be sure that the IPs of the servers are not changed in case it is DHCP enabled.
  2. Record all static IP addresses so that, as soon as the VMs are started after deployment, you can allocate them.

  3. Keep all the IPs handy in case they are static so that as soon as VMs are started after deployment, the IPs can be allocated to them.

    Note

    • The following IPs are examples. Replace them with the correct IPs in your environment.
    • clm-*** hostnames are only used internally by the products
    • csm-*** is used for integration and communication between different products

    For example: 

    IP addresses

    Internal and integration host names

    123.45.67.1

    123.45.67.2

    123.45.67.3

    123.45.67.4

    123.45.67.5

    123.45.67.6

    123.45.67.7

    123.45.67.8

    123.45.67.9

    123.45.67.10

    123.45.67.11

    clm-ar csm-ar

    clm-mt csm-mt

    clm-pm csm-pm

    clm-aws csm-aws

    clm-bao csm-bao

    clm-bsa csm-bsa

    clm-pxe csm-pxe

    clm-bna csm-bna

    clm-bco csm-bco

    clm-planner

    clm-autodeploy

  4. If you plan to access the Atrium Orchestrator URL from other VMs, update the hosts file with clm-bao and csm-bao names.
  5. Check that the VM host names and IP addresses assigned to the VMs are correct.
  6. Restart the deployed VMs.

  7. Change the time zone of the VM clients to their 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
     
     

  8. 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

  9. On each VM, manually start the RSCD service.

    /etc/init.d/rscd start
    /etc/init.d/rscd stop
  10. Connect to the respective databases from the clm-ar, clm-bsa, and clm-bna VMs. 
  11. Restart the services of BMC Server Automation, BMC Network Automation, BMC Atrium Orchestrator, BMC Remedy AR System BMC Cloud Platform Manager (OSGi), BMC Remedy AR System, BMC Atrium Web Services, and the BMC Remedy AR System Mid Tier.
  12. Install the following client components on a computer running Windows 2008 R2.
    • BMC for Server Automation RCP Console—Installation is optional because the console is installed by default with the csm-bna VM.
    • BMC Remedy Developer Studio
  13. After starting all the services, access BNA, BSA, Mid Tier, Atrium Orchestrator, and so on. 

  14. 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://<midTierHost>:8080/arsys/forms

    or

    http://<midTierHot>:8080/arsys/forms/<arServerName>


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

  15. Log on to the mid tier as the Demo user and add the licenses for the BMC Remedy AR System server.
    For example:
    http://<midTierHost>:<port>/arsys/forms/<ARservername/Cloudservername>/AR+System+Administration
    You can obtain licenses from www.bmc.com/support with a valid user name and password.
  16. 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). 
      For example:
      http://csm-mt:8080/arsys/forms/csm-ar/AR+System+Licenses+Console/Default+Admin+View 
      ARServerLicense.jpg 
    3. Use the license key to add the license to the server. 
  17. In ITSM Foundation, open the People form and give AR Administrator permissions to the CloudAdmin user. 

  18. 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:

    SysPrep1.jpg

    SysPrep2.jpg

    Note

    Virtual VC/ESX Services must use Shared Storage (local storage will not work).

  19. Verify that the RSCD port number of Virtual Center and VM templates is 4750 in the secure file.

  20. 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

     

BMC Small RDS start and stop scripts

You can start and stop individual BMC Small 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.

BMC Small RDS application

Script

RSCD Agent (on each VM)

/etc/init.d/rscd start
/etc/init.d/rscd stop

BMC Remedy AR System (clm-ar)

/opt/bmc/ARSystem/bin/
./arsystem stop
./arsystem start

BMC Server Automation (clm-bsa)

/etc/init.d/blappserv start
/etc/init.d/blappserv stop

BMC Atrium Orchestrator (clm-bao)

/opt/bmc/ao-platform/amrepo/bin/bao.sh
start
/opt/bmc/ao-platform/amrepo/bin/bao.sh
stop
/opt/bmc/ao-platform/cdp/bin/bao.sh
start
/opt/bmc/ao-platform/cdp/bin/bao.sh
stop

BMC Remedy Mid Tier (clm-mt)

/u01/bmc/apache/tomcat6.0/bin/startup.sh
/u01/bmc/apache/tomcat6.0/bin/shutdown.sh

Atrium Core Web Services (clm-aws)

/opt/apache/tomcat6.0/bin/startup.sh
/opt/apache/tomcat6.0/bin/shutdown.sh

BMC Network Automation (clm-bna)

/etc/init.d/enatomcat restart
/etc/init.d/xinetd restart

BMC Cloud Platform Manager (OSGi) (clm-pm)

/etc/init.d/bmccsm stop
/etc/init.d/bmccsm start
/etc/init.d/BMCQuickStart stop
/etc/init.d/BMCQuickStart start 

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.
    HostChangeAO.png 
  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

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*