To complete the installation process
for IBM® WebSphere® Message Broker Connectivity Pack for Healthcare you must configure WebSphere Message Broker.
If you enabled the WebSphere Message Broker runtime
environment or WebSphere Message Broker Explorer for the IBM WebSphere Message Broker Connectivity Pack for Healthcare, you must complete the following
steps after the installation wizard completes.
- If you enabled the WebSphere Message Broker runtime
environment for the IBM WebSphere Message Broker Connectivity Pack for Healthcare, complete the following steps.
Complete these steps for each IBM WebSphere Message Broker Connectivity Pack for Healthcare enabled
broker that you created, and for every new IBM WebSphere Message Broker Connectivity Pack for Healthcare broker that you create.
On Linux,
add the directory that contains the WebSphere MQ libraries to the LD_LIBRARY_PATH environment
variable. The WebSphere MQ libraries are in the <MQInstallDir>/lib directory,
where <MQInstallDir> is the location of your
WebSphere MQ installation. The default location of a WebSphere MQ
installation is /opt/mqm.
- Open a command prompt:
On Windows,
open a command console by clicking , where version is the version number
of WebSphere Message Broker for which you want
to use IBM WebSphere Message Broker Connectivity Pack for Healthcare.
On Linux,
initialize the command environment by running the mqsiprofile command.
For more information about the mqsiprofile command,
see Command environment: Windows platforms and Command environment: Linux and UNIX systems in the WebSphere Message Broker documentation.
- You must enable function that becomes available in WebSphere Message Broker fix packs. To enable
fix pack function, stop the broker by running the mqsistop command,
then run the mqsichangebroker command. For example, in WebSphere Message
Broker Version 8.0.0.2:
mqsichangebroker BROKERNAME -f 8.0.0.2
where BROKERNAME is the name of your IBM WebSphere Message Broker Connectivity Pack for Healthcare broker. For more information
about the mqsistop and mqsichangebroker commands,
see mqsistop command and mqsichangebroker command in the WebSphere Message Broker documentation.
- To run a broker in the operation mode for which you purchased a
license, start the broker by running the mqsistart command,
then run the following command:
mqsimode BROKERNAME -x modeExtensions
where:- BROKERNAME
- Specifies the name of your broker.
- -x modeExtensions
- Specifies the mode extension to which the broker is entitled.
Use one of the following values:
healthcare
Use this value if your license permits you to use
all of the functionality except for the MedicalDeviceInput node.
medicalDevices
Use this value
if your license permits you to use only the MedicalDeviceInput node.
"healthcare,medicalDevices"
Use this value if your license permits you to use
all of the functionality, including the MedicalDeviceInput node.
The -x parameter switches on
the IBM WebSphere Message Broker Connectivity Pack for Healthcare mode extensions.
To run the command with this set of parameters, you must be entitled
to use IBM WebSphere Message Broker Connectivity Pack for Healthcare.For more information
about the mqsistart and mqsimode commands, see mqsistart command and mqsimode command in the WebSphere Message Broker documentation.
- Check for error messages. If you reconfigure
the broker to a mode that is
not suitable for the deployed resources, the mqsimode command issues a warning
to indicate that changing the mode is
not allowed.
For more information about how to resolve problems,
see Resolving problems that occur during deployment
of message flows in the WebSphere Message Broker documentation.
- Restart the broker. Run the mqsistop command,
then run the mqsistart command
For more information about the mqsistop and mqsistart commands,
see mqsistop command and mqsistart command in the WebSphere Message Broker documentation.
- If you are not using the default work path
on your workstation, you must move the MedicalDeviceInput install script
to your work path.
On Windows, move the C:\Documents
and Settings\All Users\Application Data\IBM\MQSI\common\profiles\MedicalDeviceInputNode.cmd file
to the your_work_path\common\profiles\ folder.
On Linux,
move the /var/mqsi/common/profiles/MedicalDeviceInputNode.sh file
to the your_work_path/common/profiles/ directory.
For
more information about the work path and how to find your work path,
see Changing the work path in the WebSphere Message Broker documentation.
- To use the Healthcare Operational Monitoring view in WebSphere Message Broker Explorer, complete the following steps.
You must complete these steps in the WebSphere Message Broker Explorer once for each computer on
which the IBM WebSphere Message Broker Connectivity Pack for Healthcare is installed.
- Make sure that you are logged on as a user with root
or administrator authority.
- Start the WebSphere Message Broker Explorer.
On Windows,
click , where version is the version number
of WebSphere Message Broker for which you want
to use IBM WebSphere Message Broker Connectivity Pack for Healthcare.
On Linux,
enter the strmqcfg command on a command line, or
run /usr/bin/strmqcfg.
- Click , then click OK.
- Click .
On Windows Vista, Windows 7, or Windows Server 2008, ensure that
the user ID that you want to use to run the IBM WebSphere Message Broker Toolkit has authority to access
the files and folders in the IBM WebSphere Message Broker Toolkit installation
folder and all subfolders.
Next:After you complete these
post-installation steps, you can verify that IBM WebSphere Message Broker Connectivity Pack for Healthcare installed successfully by
following the instructions in Verifying your installation.