Sametime 9.0 Issue Connecting to Deployment Manager When Adding a WebSphere Based Component
For my lab environment I use the Amazon EC2 (Elastic Compute Cloud). One limitation is the difficulty setting static IP addresses. (For those in the know, I could use Elastic IPs but that is a solution that I would discourage for reasons I’ll not mention here.) Consequently I have a script infrastructure that makes maintaining hosts files easier. My machines are named in a manner that is independent of the solution. For example win3.davalen.com is also ldap.renovations.com or, another example, win2.davalen.com is also the Sametime System Console / DMGR system, sametime.renovations.com. What I failed to take into account when I first named these systems was the need for my hosts file to reference both names when it came to the DMGR.
Initial hosts file.
Let me explain. I did not encounter any issues with the environment. I installed the Sametime System Console which resulted in a federated / managed node with a deployment manager, DMGR. I updated the system to use an LDAP server successfully. And I added a Sametime Community Server. It was not until I added a Sametime Proxy (web chat) server, that I had issues. Why? Well, the problem emerged at this point because it was the first WebSphere based component added since I installed the console. The error message during install was that the DMGR could not be reached. I talented to the host sametime.renovations.com over port 8700 and 8701 without issue and I was stumped. Then, for reasons that I can’t comprehend, I decided to look more closely at the DMGR configuration. When I did I realized that the install script grabbed the system host name, win2, as the host name for the DMGR. As soon as I updated my hosts file on the proxy component server, I was able to complete the install and the proxy server was successfully federated into my Sametime cell.
Whether you have a problem of this kind or some other adventure, I am happy to report there are a number of blogs and resources available for guiding an installer through the process of installing an enterprise solution. One of these is the Knowledge Center. This resource replaced the ‘old’ product Wiki and the revised format is far superior to the former.
Step-by-Step Installation and Configuration of IBM WebSphere Portal V8.5
WebSphere Portal Enable V8.5
Installation and Configuration of a Single Host Proof of Concept
Launching the New Config Wizard
Download Instructions
Using either IBM’s Partnerworld Software Catalog or IBM’s Passport Advantage locate the eAssembly part number CRRW9ML. The download list will include the following component parts:
IBM WebSphere Portal and Web Content Manager V8.5 Multilingual Quickstart Guide (CIYE7ML )
IBM WebSphere Portal Enable Setup V8.5 Multiplatform Multilingual IMPORTANT: All parts of this image (Setup, Install, WAS ND, SDK) must be extracted into the same directory to create an installable image (CIYW3ML )
IBM WebSphere Portal Server Install V8.5 Multiplatform Multilingual IMPORTANT: All parts of this image (Setup, Install, WAS ND, SDK) must be extracted into the same directory to create an installable image (CIYV9ML )
IBM WebSphere Portal Enable Install V8.5 Multiplatform Multilingual IMPORTANT: All parts of this image (Setup, Install, WAS ND, SDK) must be extracted into the same directory to create an installable image (CIYW4ML )
IBM WebSphere Application Server Network Deployment V8.5.5.2 Multiplatform Multilingual IMPORTANT: All parts of this image (Setup, Install, WAS ND, SDK) must be extracted into the same directory to create an installable image (CIYW0ML )
IBM WebSphere SDK Java Technology Edition V7.0.6.1 Multiplatform Multilingual IMPORTANT: All parts of this image (Setup, Install, WAS ND, SDK) must be extracted into the same directory to create an installable image (CIYW1ML )
IBM WebSphere Portal V8.5 Remote Search and Document Conversion Services Multiplatform Multilingual (CIYW2ML )
Other Software
In order to configure the evaluation environment for conventional fault tolerance and scalability additional software components are needed.
IBM DB2 Workgroup Server Edition – Restricted Use V10.5 for Windows on AMD64 and Intel EM64T systems (x64) Multilingual (CIWN9ML ) NOTE: This may not be needed if installing a simple single host proof of concept that includes IBM Security Directory Server for which DB2 9.7 is included.
IBM Security Directory Server
IBM Security Directory Server v6.3.1 Client-Server with entitlement(zip file) for Windows Multilingual (CIS0HML )
IBM Security Directory Server 6.3.1, IM 1.7 for Windows Multilingual
(CIS0JML )
IBM Security Directory Server 6.3.1, JDK 1.6 SR 14 for Windows Multilingual (CIS0KML )
IBM Security Directory Server 6.3.1, DB2 v 9.7 FP6 for Windows Multilingual (CIS0LML )
IBM Security Directory Server 6.3.1, eWAS 7.0.0.29 for Windows Multilingual (CIS0MML )
IBM Security Directory Server 6.3.1, GSKit 8.0.14.26 for Windows Multilingual (CIS0NML )
Unpacking Procedures
For the purpose of these notes we are doing an install on Windows Server 2012. Extraction is done using 7-zip based on prior experience with extraction using native Windows tools.
Extracting IBM WebSphere Portal Enable
Take note of the comments in the download list regarding proper unpacking in order to create an installable image. These parts should be extracted such that they form a single directory: CIYW3ML,CIYV9ML,CIYW4ML, CIYW0ML, CIYW1ML.
In addition you should extract these parts into folders of their own: CIYW2ML and CIYE7ML).
Extracting DB2 should be done into a single DB2 folder.
Extracting IBM Security Directory server should be extracted into a single IDS directory.
A complete and illustrated procedure guide is available in PDF format. I just got too lazy to post the whole process as a blog post so be sure to take advantage of the detailed guide: Installation and Configuration of IBM WebSphere Portal Enable V8.5
Prevent Community Deletion in IBM Connections 4.5
When considering the strategic values of Communities in IBM Connections an important consideration is to determine whether Community owners should be able to delete them. By default, the are able to do so. To prevent ALL Community owners from deleting ANY Community follow the feature described in the Wiki
Taking Notez - Island Pond Consulting 