Tips for installing, troubleshooting and reinstalling the underlying components
of IBM Lotus Sametime Advanced (DB2, WebSphere MQ, WebSphere Event Broker)
DB2 v9.1 ESE (Enterprise Server Addition)
Run script to create the Sametime Advanced database (referred to as STADV
in the Infocenter) as user who has Database Administration rights (this
one creates the databases and tables)
- AIX, Linux, Solaris => ./createDb.sh STADV
- Windows => createDb.bat STADV
the text index script (this one makes the content in DB2 searchable (persistent
- AIX, Linux, Solaris => ./dbtext.sh STADV
- Windows => dbtext.bat STADV
- Ignore warnings/not found
- This is the Net Search Extender piece. Make sure
you have installed the NSE and run the script.
a separate database for Event Broker (in the Infocenter, this database
is referred to as BRKRDB). The Event Broker must use a DB2 database. It
is recommended that you create and use a separate database than the one
that is being used for Sametime Advanced (STADV) for better design, performance,
- Use of separate Broker DB server could improve performance
- Catalog the database if using Event Broker with a remote
- DB2 Client required only in this case
WebSphere MQ v220.127.116.11
- Websphere MQ is used for creating and maintaining the
queue manager (SCCS.QUEUE.MANAGER).
- MQ Explorer -this is the GUI tool for managing the queue
- Very handy for debugging and/or troubleshooting
- Visual way of looking at the status of the queue manager
- MQ commands
- IBM AIX, Linux, Solaris (log in as root) / Windows (log
in the Windows system administrator)
- Start WebSphere MQ Queue manager
- Stop WebSphere MQ Queue manager
- Uninstall/cleanup -- If you run into a problem and you
want to delete the queue manager, use these commands. The main point
here is that you don't need to delete WebSphere MQ, just the queue manager.*
dltmqm sccs.queue.manager* ConfigureEB script -- Once
you stop and delete it, you can recreate the queue manager using the ConfigureEB
WebSphere Event Broker v18.104.22.168
- There are two things created for Advanced
- A Broker called => BRKR_SCCS
- The Broker's Configuration Manager called => CMGR_SCCS
- Create separate DB for broker/on broker machine (performance/better
Deploying BAR file -- 'BAR' file = 'Broker Archive File' --
common problem area
- If you have problems deploying the BAR file....
- Try without Security enabled
- If it succeeds enable security then try deploying the
- Try With Security Enabled
- If after enabling security the deployment fails...
- Check the classpath (for SametimePlusExits.jar) this
is the security exit for the broker For more about security exits in MQ,
see this in the Infocenter
- Enable/Disable broker security - the bullets below are
the steps for disabling/enabling Broker security
- Disabling Broker Security
- mqsiservice BRKR_SCCS -r PubSubAccessControl=no
- mqsiservice BRKR_SCCS -r PubSubAuthorizationService=
- mqsiservice BRKR_SCCS -r PubSubPrincipalDirectory=
- Enabling Broker Security
- mqsiservice BRKR_SCCS -r PubSubAccessControl=yes
- mqsiservice BRKR_SCCS -r PubSubAuthorizationService=com.ibm.orgcollab.wbi.exits.rest.RestImpl
- mqsiservice BRKR_SCCS -r PubSubPrincipalDirectory=com.ibm.orgcollab.wbi.exits.rest.RestImpl
- If after disabling broker security, you still cannot deploy
the BAR file, it means there is something fundamentally wrong with the
setup that must be fixed first.
Manually unistalling WebSphere Event Broker v22.214.171.124
It is very important to follow the correct sequence when cleaning up (uninstalling)
Always delete the broker and configuration manager first before you delete
the database, or anything relating to the broker that's stored in the database.
There is a lot of configuration information that is stored in the
database that the broker requires for it to complete operations when it
needs to clean up.
Uninstall/Clean up sequence
4.>mqsideleteconfigmgr CMGR_SCCS -n
This command tells you what the system thinks is available. When
you run this command, you want to be sure that the list shows that nothing
is available. In other words, if the delete did not happen correctly,
mqsilist is going to tell you that those components are available.
6.Clean up ODBC data source
7.Clean out Broker tables/Drop Broker DB (another reason to keep
this database separate...if you need to drop it in order to reconfigure)
Manually configuring WebSphere Event Broker
Configure Event Broker - manual steps
1.Create Broker DB.
2.Set up ODBC data source that connects to the Broker DB.
4.Create Config Manager.
5.Stop Broker and Config Manager.
8.Deploy realtime1506 BAR file.
9.Start Message flow.
ConfigureEB script (automates manual steps)
MQ + EB steps