Hi everyone... a quick post covering things to keep in mind while working in the HP Software-as-a-Service (SaaS) environment. The lessons learned below have come from about a year's worth of experience across several client installations.
If you have additional items to add to this list, I would love to hear about them, as we can then help each other learn. So, please post a comment below :-)
In the initial project planning stage, you will need to allow additional time in the overall project schedule for the following required steps:
- Creating the documentation based on the HP SaaS Development Process
- SaaS requirements spreadsheet
- SaaS implementation document
- SaaS release document
- HP SaaS Technical CAB Reviews
- In addition to using HP QualityCenter for logging issues/defects, the HP SaaS program also makes use of HP QualityCenter for Release Management
- Note that Change records are moved through the Change Management lifecycle, including the delivery of TEST and PRODUCTION build packages, as attachments on the RFC
- Code migration occurs via the following steps:
- DEVELOPMENT--> TEST
- TEST --> PRODUCTION
- Note that Production implementations are performed by the HP Production Team
If you are an HP Partner and you are implementing or working with the HP Service Manager application in the HP SaaS environment, you will have access to the HP SaaS DEVELOPMENT environment via HP Service Manager's Windows/eclipse client and the web client. You will also only be granted Remote Desktop access to the HP SaaS DEVELOPMENT server. Partners are limited to accessing the HP SaaS TEST and PRODUCTION instances only via the HP Service Manager web client. Please plan accordingly.
- It is difficult to troubleshoot HP Service Manager application issues because the RAD debugger is not available via the web client.
- When troubleshooting possible issues in the TEST or PRODUCTION environment, the HP SaaS Team has to be engaged to access log files.
On a more positive note, one advantage of using the HP SaaS environment is that the HP product versions are maintained by HP. As an example, Techport Thirteen kicked off two projects under the HP SaaS Program in late 2011 and the plan was to implement HP Service Manager 9.2x for both. HP Service Manager v9.3 was released around that time and the HP SaaS Team updated their SaaS environments in time for us to perform development on the latest version of the application. Pretty cool!
So, that is what I have learned so far... It is important to know of these items ahead of time, as you will have a much more successful relationship with the HP SaaS environment in the long run.
Make sure you download a copy of the HP SaaS Development Process overview document per the button below. It is only 11 pages long, and reading it ahead of time, especially if you are in a Technical Lead or Project Manager role, will be very beneficial: