Preparing for the Install

These instructions are for Broker 6.5.2 included with Fabric 6.5 and Fabric 7.0. The setup for 7.1 is significantly easier than this.

Before you go and install a broker be very careful about your plan first. Take some time to remember how a broker is structured.

• Broker Monitor: A process which manages Broker Servers. There can only be one of these per machine in pre 7.1 Broker Monitors can manage Broker Servers of lower versions but can not manage Broker Servers with a version greater to theirs.
• Broker Server: A process which opens a port on the machine. Most common version of Broker Server are 6.1 and 6.5. A 6.5 Broker Manager can manage a 6.1 Broker Server.
• Broker Instances: 1 or more of these run inside of a Broker Server. They are identified by host:port (which is the broker server) and then name. Clients (ie an IS) connect to a particular Broker instance, not a whole broker server.

If there is already a broker running on the machine this is ok, however you can not start another broker monitor. You will need to use the existing broker monitor to create a new broker server.

If you require to run a 6.5 Broker Server on a machine which already has a 6.1 broker on it, you need to shutdown the 6.1 broker monitor, then start the 6.5 broker monitor and point it to the same data directory. It will happy manage the 6.1 Brokers and now you can create a new 6.5 broker server.

If you are changing an existing installation a data directory will already exist, if not you need to chose a place on disk. The manual seems to insist you need to use /var/opt/webmethods and this is probably good for production as this could be a different disk but in dev and systest this can just be a directory anywhere.

Dont install as root! Install as the webm user, then start broker manually. You only need root to install the rc3.d script and give you access to /var/opt/webmethods (if thats where you want to put the data dir). Once the monitor it up you can create Broker servers on different ports.

If you are installing a a broker on a machine without any brokers beforre the news is good, this process is quite easy and straight forward.

Installing The Broker Monitor

• Use the webMethods installer to install the broker. Do this as the users under which the broker will run, dont run the installer as root, it is not needed and will just cause you hassle later.

• For the user who will run the broker set two environment variables, one to the Broker install directory and another to where the base of the data directory is. To achieve this easily, add similar lines to the ".profile" file of your operating system user

# webmethods broker path
ACTIVE_HOME=/webm65/webMethods65/Broker
ACTIVE_CONFIG=/webm1/broker

export ACTIVE_HOME
export ACTIVE_CONFIG

• Create the data directory, this is the path you specified above as "ACTIVE_CONFIG". Ensure broker user has full access to it.

• excute the following command to create the Broker Monitor config file in the directory you specified in ACTIVE_CONFIG
  webmethods-broker-directory/bin/awbrokermon -config webmethods-broker-directory -user user-who-will-run-broker -group group-of-this-user

• You can now start the broker by excuting the script

webmethods-broker-directory/S45Broker65 start

• If you want to run the Broker as a daemon, copy this file to the /sbin/rc3.d directory

• Now you have a running Broker monitor. You can verify this by running this command seeing the awbrokermon service there

ps -ef | grep aw

Creating A Broker Server

• Inside of the webmethods-broker-directory/bin/ is a script "server_config". You use this to create broker servers from the broker monitor. There is no graphical tool to do this.

  ./server_config create /webm65/broker_data/5804 -k YOURKEYHERE 
  -p 5804 
  -session_config qs -qs_log_file /webm65/broker_data/5804/BrokerConfig.qs.log 50M 
  -qs_storage_file /webm65/broker_data/5804/BrokerConfig.qs.stor 100M 20M 
  -session_data qs  -qs_log_file /webm65/broker_data/5804/BrokerSession.qs.log 50M 
  -qs_storage_file /webm65/broker_data/5804/BrokerSession.qs.stor 100M 20M

• Before you run the following command you need to create the /webm1/broker/6844 directory. By placing all the broker server files inside of a directory named after the port we help to organised our installation.

• This command creates an average but small broker storage file. The first number on the end of the maximum size, the second is the inital. Broker sizing requirements are beyond the scope of this document.

• You can verify your Broker server is running by running

server_config list

Creating a Broker Instance

Now you have a broker server running on a port. Use the screens inside of the portal tool to connect to this broker server and from these graphic screens you can create a broker instance to which the Integration Server can connect to.