Adding a bus

A bus is a way of interconnecting machines so that they can be treated as one logical entity. You must first add a bus before you can add servers or server clusters to that bus.

Before you begin

Plan your bus topology. For more information, review the topic Planning issues for bus topologies.

About this task

Adding a bus is the first step in the procedure to create a bus. Use the administrative console to complete the following steps.

Procedure

  1. In the navigation pane, click Service integration > Buses. A list of buses is displayed in the content pane.
  2. In the content pane, click New.
  3. Specify a unique name for the bus in the Name field.
  4. Type a description for the bus in the Description field. The description is used for administrative purposes only.
  5. Specify the following properties for the bus:
    Enable bus security

    When bus security is enabled, that is, when the Secure property is selected and global security for the cell is also selected, access to the bus itself and to all destinations on the bus must be authorized.

    Inter-engine authentication alias
    The name of the authentication alias used to authorize communication between messaging engines on the bus. This field can be left blank. If a value is specified, and bus security is enabled, incoming connections to the bus are controlled to prevent unauthorized clients or messaging engines from establishing a connection.
    Mediations authentication alias
    The name of the authentication alias used to authorize mediations to access the bus.
    Inter-engine transport chain
    The transport chain used for communication between messaging engines in this bus.

    The transport chain must correspond to one of the transport chains defined in the Messaging engine inbound transports settings for the server. All servers automatically have a number of transport chains defined to them, and it is also possible to create new transport chains.

    The default transport chain is InboundBasicMessaging.

    Discard messages
    Whether messages on a deleted message point should be retained at a system exception destination or can be discarded.
    Configuration reload enabled
    Select this option to enable certain changes to the bus configuration to be applied without requiring the messaging engines to be restarted. These changes are when destinations or mediations are added to or removed from the bus. This option also controls whether automatic updates occur on all the messaging engines on the bus.
    High message threshold
    A threshold above which the messaging system will take action to limit the addition of more messages to a message point. When a messaging engine is created on this bus, the value of this property is used to set the default high message threshold for the messaging engine.
  6. Click OK.
  7. Save your changes to the master configuration.

What to do next

You can now create a messaging engine, and a bus member.



In this information ...


Related tasks

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 10:03:57 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-zos&topic=tjj0500_
File name: tjj0500_.html