My name is Shahfazal (Fazal) Mohammed and I'm with the WebSphere Process Server (WPS) Technical Support team. I've been with IBM for over 7 years, joining the WebSphere Process Server Test (QA) team as an intern, then moving up to WPS QA Functional and System verification testing. As part of the QA team, I worked on both White-box and Black-box testing, as well as User-Acceptance testing. I designed and developed End-to-End tests based on real-world scenarios from the Insurance domain. I also worked on System Integration Testing, Automation, Stress and Endurance testing as well. After about 4 years with the Testing team, I moved to the WPS Support team to leverage my in-depth knowledge of WPS to help our clients debug and resolve issues.
In my current role as a Support professional for WPS, I work on different areas of WebSphere Process Server runtime including Business Integration scenarios, Web Services, Service Component Architecture (SCA), Enterprise Service Bus (ESB) Business Objects (BO), High CPU usage (Java thread-level analysis), Out of Memory situations (Java Heap analysis) for WPS. Recently (since v7 of WPS came out) we observed there were a rash of Installation issues with WPS and I volunteered to work with Development, give them feedback on the pain points and eventually was able to drive down the number of issues we saw reported by our clients. This was achieved by improving (and increasing) the usability of the product, rigorous testing and improved documentation. This blog post is a result of the documentation effort and my attempt to outline the tips and tricks in the setup process and also perhaps enable you, the reader, to understand the different options of installation and avoid common mistakes/pitfalls.
I've written official technotes and contributed to other documentation to help you with your installation questions/issues but when asked by my manager to contribute to a 'blog' of sorts to write about Installation/Setup, I was very interested.
One of the most common questions I've encountered handling PMRs with WebSphere Process Server installation, especially in v7.0, is Silent/non-GUI installation by a non-root user. Back in pre-v7 WebSphere Process Server, we had straightforward instructions with response files and everything was handled by the WebSphere Application Server Install Shield Multi-Platform (ISMP) either via GUI mode or silently. And then there is the issue of the Installation Manager connecting to live IBM 'repositories' to gather information about the latest (and greatest) fixes and fix pack versions available.In v7.0, the Installation Manager (which was already being used for WebSphere Integration Developer and Rational Application Developer since v6.1.2) is being introduced as the tool for installing, configuring and managing WebSphere Process Server. Note that currently, WebSphere Application Server v7+ still needs to be managed/configured via the Update Installer. Eventually, both WebSphere Application Server and WebSphere Process Server will use the Installation Manager (like they used to use Update Installer in the past).
As this intro post for the Install blog, I'll discuss briefly what you'll need to do to be able to properly install WebSphere Process Server v7 via the most commonly requested method - silent installation as a non-root user. Installing silently allows you to control where each of the components can be installed, specifically the Installation Manager and the 'Agent DataLocation' for the Installation Manager. Here's how I explain/outline the silent installation process to our WebSphere Process Server customers:
1. Since WebSphere Application Server v220.127.116.11 does not support installation via IM, WebSphere Application Server needs to be installed first.
2. Installation Manager needs to be installed next.
3. Installation Manager needs to import the WebSphere Application Server installed in step 1 above.
4. Installation Manager will need to install WebSphere Process Server (along with the XML and SCA Feature Packs) to the WebSphere Application Server imported in step 3 above
The steps above are typically combined into one script with an appropriate response file. In my next blog post, I'll outline the above steps with an example and other items that you need to be careful about.
Please see the continuation of this blog in Part 2.