The developerWorks Connections platform will be sunset on January 2, 2020. This blog will no longer be available unless an extension has been requested. More details available on our FAQ.
X
When WAS start and stop scripts don't seem to completeI've been running into issues recently with the various WAS start and stop scripts (sta
Look for the following signs:
Once you identify that the desired action was performed, you can simply terminate the script by running Ctrl + C. I haven't identified a root cause for why this happens, but the workaround is easy enough that I've been able to live with it.
Chad Scott, IBM Connections, Software Support Engineer |
Video overview: IBM Sametime product family - A brief demo of the Websphere SSL Configuration area
We have a new video uploaded on our Coll This 7-min demo overview by Tony Payne is an excerpt of a Sametime Open Mic session titled "SSL and Sametime: POODLE Training 101" (held in March 2015). It demonstrates using the Sametime System Console -- showing some default settings, key stores, and cell vs. node ideas within the concept of the WebSphere Application Server (WAS). The full playback recording of this entire Open Mic event, along with the presentation used, can be found here.
In addition to subscribing to our support YouTube channel, you can connect with IBM Collaboration Solutions Support on Twitter and Facebook.
For additional Sametime support resources, visit the IBM
|
Manually registering & federating a WAS-based Sametime serverOccasionally, after installing a new Sametime server, the installer fails to register and federate the server. To remedy the situation, we offer a script named registerProduct.sh (or .bat for those poor souls on Windows). I had a customer try and run the script, to only partial success. The script successfully registered the server, but did not federate it. The error message he got was this: AIDSC1689E: JRE path entered does not seem correct.
I dug into our script and Java code, looking for what may have caused the error. After understanding what it was trying to do, I re-examined the logs that were generated. The logs are located in the same directory as where the script was run. At the bottom of the logs was this message: 2016:5:17› 14:28:40› com. The relevant part is at the beginning of the path - notice it starts with "Manager"
Reviewing the text printed to the screen after running the script, we see a more clear example of the issue: Parameters passed are: -federateNode, C:\I Note there are three parameters: [-federatenode] [C:\
This is not what we want - we want two parameters: [-federateNode] and [C:\
Our code is equipped to handle three parameters, since you have the option of passing in [-silent] as the second parameter. Unfortunately, all we do is check to see if the second parameter is exactly equal to "-silent". If it isn't, we just ignore it and move on. Our sanity checking for the third parameter involves checking to see if it ends with "bin", and whether the path actually exists. That second check is what generates the error message "AIDSC1689E: JRE path entered does not seem correct."
To resolve the issue, you have three options: (1) escape the space (C:\
You can then re-run the script, as it can be run multiple times with no ill effects.
|
