If you select the MQ Workflow option, whether you select it alone or with another option (WMQI and/or WICS), you must enter the following information:
The MQ Workflow Configuration parameters.
The MQ Workflow Database (the Event Queue Database) parameters.
In this case the BI Monitor will be forced to authenticate the logged users to BI Monitor Client through the MQ Workflow. That means any user who will login to BI Monitor Client must be an MQSeries Workflow registered user, and only MQSeries Workflow users have the privilege to log in to BI Monitor Client.
The following are the wizard screens that appear when you select the MQSeries Workflow / WebSphere MQ Workflow option:
In the next screen you will be informed that the wizard will check for the existence of the IBM MQ Workflow and its database. Click Next to continue.
In the next screen you will be asked to select the IBM MQSeries Workflow APIs types, that will be used by the BI Monitor to connect to the MQ Workflow server configuration. You have two options:
MQ Workflow Agent APIs
MQ Workflow Native APIs
Native APIs are supported by MQ Workflow v 3.6, or later.
Proceed to Step 3 if you select MQ Workflow Agent APIs, or proceed to Step 4 if you select MQ Workflow Native APIs.
In the next screen you will be asked to enter the following IBM MQ Workflow Configuration parameters in each corresponding field:
MQSeries Workflow Library File: The MQSeries Workflow library file named fmcojagt.jar. (You can click the Browse button represented as triple dots to select this file).
Configuration Id: The used MQ Workflow Configuration ID (Default or Non-Default).
Encoding: The MQSeries Workflow Server machine encoding. (This property must be set if the MQ Workflow Server machine encoding is different from the Monitor Server machine encoding).
Important Note: If the MQ Workflow Configuration ID is not defined, a default configuration must
be defined.
In the next screen you will be asked to enter the following IBM MQ Workflow Configuration parameters in each corresponding field:
MQWF Native Library File: The IBM MQSeries Workflow native library file named fmcjapi.jar. (You can click the Browse button represented as triple dots to select the appropriate file).
Configuration Id: The used MQ Workflow Configuration ID (Default or Non-Default).
Configuration Parameter File: The path containing the IBM MQ Workflow Configuration Parameter file named fmcrc. (You can click the Browse button represented as triple dots to select the appropriate file).
JMS Libraries Path: The path containing the IBM MQSeries JMS JAR files named com.ibm.mq.jar, com.ibm.mqjms.jar, jms.jar and connector.jar. (You can click the Browse button represented as triple dots to select the appropriate file).
Encoding: The MQSeries Workflow Server machine encoding. (This property must be set if the MQ Workflow Server machine encoding is different from the Monitor Server machine encoding).
Important Note: If the MQ Workflow Configuration ID is not defined, a default configuration must be defined.
Enter the required values for each corresponding field and click Next to continue.
In the next screen you will be asked to enter the following information for the IBM MQ Workflow database (The Event Queue Database):
In the Name/URL field, enter the MQ Workflow database name or the database URL.
If you are using Oracle database server, you can type one of the following for the MQ Workflow database URL:
jdbc:oracle:thin:@<Oracle_Server_Name>:<Oracle_Server_Por t_Number>:FMCDB
jdbc:oracle:oci:@FMCDB (for Oracle 9i and Oracle 10g) or jdbc:oracle:oci8:@FMCDB (for Oracle 8i)
where <Oracle_Server_Name> is the name or the IP address of the Oracle Database Server machine, and <Oracle_Server_Port_Number> is the Oracle Server Port Number (the default port is 1521)
In the Administrator and Password fields, enter the user name and password of the MQSeries Workflow database administrator.
In the Schema field, enter the MQSeries Workflow database schema (The default value is FMC).
In Oracle Database, the Event Queue database schema must be the same as the Database Administrator's User Name.
In the MQ Workflow Connector Queue section, type the TableSpaces names for each of the following:
Tables
Indexes
Large Objects (LOBs)
You can specify a different TableSpace name for each of these three fields. Alternatively, you can specify the same TableSpace for more than one field. In the later case these groups of tables and/or indexes will use the same TableSpace for storing the data physically on the hard drive.
If you leave a blank field without specifying a TableSpace name, then the default TableSpace will be used for the corresponding group of tables or indexes.
The specified TableSpace should have been previously created in the Database server. Otherwise, the deployment will not be performed properly and you will not be able to create the database tables.
The wizard will check the connection with the database using the entered database name (or URL), user name and password. If one or more of the entered parameters are not correct, then you will be informed by a message, and the wizard will not continue until you enter the correct parameters.
In case you have an existing database that belongs to a previous version and contains data, then you will not be able to define multiple TableSpaces, and the TableSpaces Names fields will be disabled.
Click Next to continue.