Structural Overview of the ePM GUI

The hierarchy of the Host Explorer tree in the left pane is structure as shown in Figure 5–4.

Figure 5–4 ePM Structure of the Host Explorer

Root

There is exactly one root, always named B2B Repository. It cannot be deleted. The root contains a special Schedules folder as well as one or more B2B Hosts.

B2B Hosts

B2B Hosts are the second-highest object type. They can be created, imported, renamed, exported, and deleted. Each B2B Host contains the following:

• A Business Protocols folder, containing one or more business protocols. Each business protocol contains one or more business action groups. Each business action group contains at least two business actions — at least one outbound business action and at least one inbound business action.

• A Delivery Protocols folder, containing one or more delivery protocols. Each delivery protocol contains one or more delivery action groups. Each delivery action group contains at least two delivery actions — at least one outbound delivery action and at least one inbound delivery action.

• A Transports folder, containing one or more external transports.

• A Host Transaction Profiles folder, containing zero or more transaction profiles. Each transaction profile contains an outbound transaction profile and and an inbound transaction profile.

• A Contacts folder, containing zero or more contacts.

Schedules

The special Schedules folder contains zero or more schedules that can be referenced by other objects in the B2B Repository. A schedule can be regularly periodic, or it can be specified according to a daily, weekly, or monthly arrangement. Each schedule can be created, renamed, and deleted, and schedules can be imported or exported in aggregate.

Notes section

For each item that can be modified, the canvas provides a Notes area where you can provide free text. (For an illustration, see Basic B2B Host Operations in ePM). Best practice is to use this area to the describe the item, and also to log every important change made to it.