Skip navigation
Share:|

Most of us have various experiences deploying BMC Cloud Lifecycle Management 3001.

 

We follow the documentation but depending we don't know what sometime, we are facing some installation failure.

 

Here is what I managed to have my CLM deployment happening with success.

 

UNINSTALL EXISTING RSCD

If CLM servers have been provisioned with a RSCD agent, stop & uninstall it and delete the configuration files (exports, users.local & users).

 

PREVENT 4750 TCP PORT CONFLICT

- Comment ssad Linux services on tcp & udp in /etc/services on CLM IP and remote servers.

 

CONFIGURE TNSNAME

- If you are using Oracle, configure the TNSNAME.ORA on the remote servers where oracle client are installed. Test the connection with the databases using TNSPING and connect to the DB using SQLPLUS.

- Using CLM IP you will provide the DB connection information, but the Install Planner will ne configure you remote server, this need to be done previously the installation.

 

INSTALLATION STAGING DIRECTORY

- use the same path for the CLM install planner and the remote servers (/tmp - /tmp, /var/tmp - /var/tmp)

- The path should be executable on both sides

 

BMC BLADELOGIC SERVER AUTOMATION

- If you are integrating an existing BBSA infrastructure with CLM and if you are not at the correct build version (8.2.02 323), CLM will update Bladelogic integrated servers. If you do not want to have CLM managing the upgrade, be aware that you will have to perform the update prior to deploy the CLM components which have a dependency with BSA application server & console.

- Verify that your BBSA servers have the following settings

  • AppServer DefaultRestVersion = 8.1.02.
  • Appserver RestAssetAttributesUseInternalName = false
  • AppServer enableWebServices = true

- Temporary give access * rw in exports configuration file and delete all entries in the users & users.local files

 

IF YOU RESTART A REMOTE SERVER

- Make sure the RSCD agent installed by CLM is up & running before launching a deployment on this target.

 

Antoine GABORIT

antoine_gaborit@bmc.com

http://fr.linkedin.com/in/antoinegaborit

CLM HowTo

Posted by Antoine GABORIT Jan 28, 2013
Share:|

How to skip Cloud Lifecycle Management Install planner products dependencies

If you want to install some of the CLM products skipping the dependency, this option will allow you to go directly the component you want to install- Launch the CLM IP using setup.sh -J release_dependencies=true.

 

How to make your BBSA application server and console version compatible with CLM install planner without upgrading

If you want to be able to integrate BSA infrastructure without allowing CLM IP to upgrade the product, this solution can be use.On the BladeLogic Application Server where is installed Operation Manager and Server Automation console modify

  • ClientInstallerInstalledConfiguration.xml (located in the BSA install directory) with <version majorVersion="2" minorVersion="02" releaseVersion="8" subMinorVersion="323"/> (populate the version associate with you CLM IP version)
  • version (located in the BSA install directory) with APPSERVER=8.2.02.233 and CM=8.2.02.233 (populate the version associate with you CLM IP version)

 

How to keep DB connection between Enterprise AR & Cloud AR.

If you are able to connect to the EAR and CAR, but later, you are not able anymore, and if you are generating DB connection errors in the arerror.log, you are probably face to Firewall which close inactive connection after an elapse time or an Oracle configuration issue.

  • Reduce the Linux tcp_keepalive_time settings. This force Linux to probe the connection, and then keep it active before the Firewall close the inactive connection.
  • Modify Sqlnet.expire_time in sqlnet.ora to keep the connection with the Oracle client.

 

How to change a product failure status

If after having resolved a product issue on one of the remote server, CLM is still showing a deployment status failure on this server (with no explanation in the install planner logs), you need to modify some xml files on the remote server.

  • Example, for Bladelogic Server Automation edit BladelogicOperationsManagerInstalledConfiguration.xml and delete the data in the value tag

      <name>FAILED_INSTALL_FEATURES</name>

      <value></value>

  • Also delete BSA_CONFIGURATION_COMPLETE property in the BladelogicOperationsManagerInstalledConfiguration.xml.

 

 

Antoine GABORIT

antoine_gaborit@bmc.com

http://fr.linkedin.com/in/antoinegaborit

Share:|

Had you already felt alone face to a project issue, and the only one to identify the high level risk to the delivery?

 

Had you already question “why?” face to a lake of involvement of the project management?

 

Had you already be discouraged face to the silence after having send tons of messages to request actions?

 

If yes, to start this New Year, I give you a solution to manage your project risks using OpenAir. I hope this is going to help you driving your project.

 

Go in Openair

 

Select Projects => Projects

project.jpg

 

Retrieve you project from the list => Click on it

 

Click on Issues then new => issue

issue.jpg

 

Describe your issue and select

category.jpg

 

Send an email to your project management to make it aware about this new project risk issue.

 

Following this procedure you will create officially a risk that should be taking into account.

 

Before going in this final procedure don’t forget to follow the other procedure:

  • Make aware the project management about the risk and track with him the resolution
  • If no actions are taking in charge, make aware you management about the situation
  • If the risk is still not managed then you should go in Openair to create a project risk issue.

The project risk issue should identify a risk to your delivery with an impact on the planning, customer satisfaction, workload, architecture, functional …. The risk will not allow you to deliver your solutions as it was planned in the SOW.

 

I wish you to success in your futur project delivery.

 

Antoine GABORIT

antoine_gaborit@bmc.com 

http://fr.linkedin.com/in/antoinegaborit

Share:|
  • This week I am launching a CLM deployment integrating existing Bladelogic servers with new servers hosting new solutions to use with Cloud Lifecycle management.

 

This deployment is for the pre production environment. The customer already used some of the BMC solutions involved in the Cloud Lifecycle Management servers stack.

 

Only Bladelogic Server Automation will be integrated in this CLM technical architecture. The others products (Network automation, Atrium Orchestrator, ITSM, BPPM, …) will be installed by CLM.

 

Here I would like to share my first experience on CLM 3.0 with integration of an existing BSA infrastructure and the difficulties we were face to during the installation.

 

I am not coming back on the High Level Design and the deployment prerequisites and tasks performed before launching the CLM installation.

 

You can go on https://intranet.bmc.com/global_services/cel/Customer and Project Libraries/Sanofi Aventis GIS Transformation Programme/3 - CLM/2 - Analyze to have the technical context of this CLM implementation project.

 

At first we had to integrate the BSA servers. The BSA version we had to work with is BSA 8.2.02.

 

We used the Cloud Lifecycle Management Install Planner 3.0.00. CLM installer was failing to integrate the existing BSA servers. It did not accept the Bladelogic Operation manager server and the BMC Server Automation Console at version 8.2.02.

 

A case was opened to the support to solve the situation.

 

Cloud Lifecycle Management 3.0 matrix compatibility integrates the BBSA 8.2.02 support but the CLM Install Planner is only able to integrate the version he can deploy. The installer 3.0.00 only supports the Bladelogic server automation integration at level 8.2.01 build 290.

 

To bypass the BSA version validation, support provided an Install Planner option (release_dependencies=true). But this option failed to bypass our issue. The support escaladed to the CLM Install Planner team to identify the route cause.

 

Finally the CLM Install Planner team informed us that “If customer wants to use the BSA higher than 8.2.01.290 then they will have to use the CLM3.0 SP1 or CLM3.0.01 to integrate BSA 8.2.02”. This is how we learned that a new Installer 3.0.01 was existing since the 5th of December which was deploying and supporting the BSA 8.2.02 integration.

 

So we uninstalled the old Installer, downloaded, transferred and installed the new one.

 

We were able to integrate BSA infrastructure at version 8.2.02. But to continue the Cloud Lifecycle Management deployment, the Install Planner 3.0.01 requested to upgrade BSA to 8.2.02 build 233 which is 8.2.02 patch 1.

 

This patch does not exist in EPD and seems to be integrated only in the installer 3.0.01.

 

In pre production environment, for any update of my Bladelogic Server Automation customer infrastructure, a change management process have to be planned and followed, and it needs to involve others teams.

 

The situation was escaladed to the support as for integration of existing products, the Cloud Lifecycle Management Install Planner limits the products matrix compatibility to the version he is able to deploy (in this case BSA 8.2.02 233 – my customer is 8.2.02 231) and this version could only be deployed using CLM install planner.

 

BMC escaladed internally involving program manager, strategic account manager, customer success manager, critical account manager, practice manager, solution architect and product manager, to audit the issue and plan the resolution.

 

A workaround was identified to continue the Cloud Lifecycle Management implementation without upgrading BSA.

 

On the BladeLogic Application Server where is installed Operation Manager and Server Automation console we modified:

  • ClientInstallerInstalledConfiguration.xml (located in the BSA install directory) with <version majorVersion="2" minorVersion="02" releaseVersion="8" subMinorVersion="233"/>
  • version (located in the BSA install directory) with APPSERVER=8.2.02.233 and CM=8.2.02.233

 

In parallel the Install Planner team engaged to publish and document the BSA 8.2.02 patch1 (build 233) in EPD to allow a BSA upgrade to the only version supported for integration and manageable outside CLM deployment process as an update prerequisites.

 

After having cleaned all the Installer xml files (in the installer install directory and in the tmp folder), we were able to integrate successfully and with no update request the BSA servers. In this situation we could had access to the “modify existing deployment” setup the others servers for new product deployment.

 

This is my conclusion: before going to the integration of existing solutions with a Cloud Lifecycle Management implementation, be very careful about the CLM Install Planner compatibility matrix. This compatibility matrix is different to the Cloud Lifecycle Management one as CLM can interact with various product versions where the Installer is only able to support a specific product build version. Also make sure the Installer will not request you to upgrade the integrated product if the customer do not authorize this procedure.

 

Last point: this CLM Install Planner procedure does not allow any flexibility at the product version level. This will cause in the close future issues around migration. All solution has his own lifecycle outside CLM. I don’t see how multiple solution can be strictly at the build version correct level for a specific Cloud Lifecycle Management install planner version. We could not also say to our customer that to do not be face this situation they need to have CLM infrastructure with dedicated solutions added to the existing one. This position is against BSM one. The only reason we can say this is when the existing products technical architecture or functional design do not meet the CLM specifications.

 

Antoine

antoine_gaborit@bmc.com

http://fr.linkedin.com/in/antoinegaborit

Share:|

If you are involved in an architecture design specifications, one of the question which is always coming is "Could we use virtual machine instead physical one".

 

The BMC answer is yes as long as the VMs meet some prerequisites.

 

The most important prerequisite is the VM resources allocation as it has a huge impact on solutions availability. BMC expects to have dedicated virtual resources to the VMs hosting BMC java application.

 

Then usually your are challenged to explain why BMC is requesting this as VMware provides all the mechanisms to share computing resources and optimize the VMs availability. If you are not able to describe the impacts in case of no dedicated resources to your VM this will put at risk your architecture performances.

 

Here I would like to share a VMware document describing what are the best practices to host java application on Virtual Machines. Here you will learn that BMC prerequisites requests lean on VMware best practices.

 

So don't be afraid now to request what you need (and tune your java application) as it is perfectly aligned and justified with VMware environment.

 

I add a document provided by Dhananjay Gundre. Thanks

 

 

Antoine GABORIT

antoine_gaborit@bmc.com

http://fr.linkedin.com/in/antoinegaborit

Share:|

Forrester published a Case Study on Sanofi.
In this case study we learn that:

"From the outset, the company realized that this level of process transformation required the support of proven business service management technology solutions. Sanofi selected BMC as a key partner in harmonizing processes."

 

BMC Cloud Lifecycle Management (CLM), BMC ProactiveNet Performance Management (BPPM), BMC Remedy IT Service Management (ITSM), BMC IT Business Management (ITBM) are the solutions involved in the Sanofi Strategy.

 

 

http://www.forrester.com/Case+Study+Sanofis+Successful+IO+Transformation+Approach/quickscan/-/E-RES81781#/#heading8

Sanofi CLM HLD

Posted by Antoine GABORIT Nov 12, 2012
Share:|

I published the CLM HLD for Sanofi

https://intranet.bmc.com/global_services/cel/Customer and Project Libraries/Sanofi Aventis GIS Transformation Programme/3 - CLM/2 - Analyze

 

This document objective is to:

- Present Sanofi IT eco-system & constraints

- Identify the Sanofi user’s requirements

- Propose a high level technical architecture to answer Sanofi expectations

- Describe CLM and sub solutions.

 

The CLM project for is part of the Sanofi BSM one.

 

I started to work on this document in July.

 

I reviewed lot of Sanofi documents and met all the Sanofi teams concerned by the CLM scope.

 

Some of the choice we have (VM templates, IPAM) was rejected by some of the Sanofi team but I managed to have the best solution for the CLM implementation strategy.