Chapter 1. About This Book; Audience; Roles, Access Levels, And Responsibilities - IBM E02HRLL-G - WebSphere Partner Gateway Express Administration Manual

Chapter 1. About this book

This document describes how WebSphere Partner Gateway can be maintained to
suit the requirements of the business-to-business (B2B) trading community. This
guide assumes that you have already performed the necessary hub configuration
tasks provided in the WebSphere Partner Gateway Hub Configuration Guide.

Audience

Administrators maintain WebSphere Partner Gateway. This book assumes two
types of administrators:
v Hub administrator: is the super user in the community. The hub administrator is
v Account administrator: has access to a subset of the hub administrator features
v Internal Partner: is the primary company and driving force within the hub
v External Partner: is the company that does business with the internal partner
Refer to WebSphere Partner Gateway Partner Guide for more information on hub
administrator, internal partner, and external partner.

Roles, access levels, and responsibilities

In WebSphere Partner Gateway, the hub administrator sets up the profiles of the
partners. A partner always has at least one administrator user and can have
additional users added by the administrator of that profile.
To illustrate the concept of roles, a simple implementation of WebSphere Partner
Gateway with a minimum of three profiles is described as follows:
Hub Operator
This is a system defined profile that will be included on the machine during
installation. The Hub Operator profile has one defined user name, hubadmin,
which is the super-user of the system and can accomplish any configuration task.
You can relate this role to the IT group that runs the actual WebSphere Partner
Gateway server, but is not actively sending documents back and forth. There can
be only one Hub Operator type participant.
Internal Partner
This partner is created by the hubadmin user. This user is the company that
bought the WebSphere Partner Gateway and is running the system. There can be
many internal partners, but only one default internal partner. Businesses act as
© Copyright IBM Corp. 2007, 2008
responsible for overall hub community configuration and management,
including partner configuration and connection activation.
and is the main administrative user for the internal partner or external partner.
community. Internal partner is responsible for the purchase and creation of the
hub community. In addition, the internal partner provides the definition of the
electronic business process transactions that happen between them and their
external partners.
through the hub community. External partners have to complete a configuration
process to connect to the hub community. Once connected, external partners can
exchange electronic business documents with the internal partner.
1