OSI/MHS Configuration and Management Manual

Planning Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
3-5
Using OSI/MHS P7 API to Communicate With Local
Users
•
What is your expected message volume and how will it affect availability?
Message volume affects the number of entry manager processes you want to use.
(You can have up to five entry manager processes.) Message volume also
determines the size of the entry manager queue files and log queue files.
•
What are the expected average and maximum message sizes, and what is the
average number of recipients per message? OSI/MHS can deliver messages of
up to 10 MB to a GPI gateway.
You configure a general user gateway through the GATEWAY object. You configure a
client application through the APPL object of the GW type.
Appendix B, Configuration Checklists, contains checklists for:
•
Configuring a general user gateway
•
Configuring a gateway interface (GI CLASS object)
For specific information about GPI, see the OSI/MHS Gateway Programmatic Interface
(GPI) Reference Manual and the OSI/MHS Gateway Programmatic Interface (GPI)
Programming Guide.
Using OSI/MHS P7 API to Communicate With Local Users
You can use the P7 Application Programmatic Interface (P7 API) to communicate
between a local user agent, or client application, and the OSI/MHS subsystem on the
same system. The P7 API eliminates the need for client applications to use the
underlying OSI layers to reach the local OSI/MHS subsystem.
If you plan to use the P7 API, you must consider the following:
•
How many local users will you define?
•
What type of APPL objects will you define (generic or specific)?
•
What are the expected average and maximum message sizes, and what is the
average number of recipients per message? OSI/MHS supports a maximum
message size of 10 MB for local user agents.
You configure a P7 API through the LO CLASS object.
Appendix B, Configuration Checklists, contains checklists for configuring a local user
agent (LO CLASS object).
For specific information about P7 API, see the OSI/MHS P7 Application Programmatic
Interface (P7 API) Manual.
Using OSI/MHS as a Message Store
For long-term storage of messages, you use a message store (MS). MS users are
configured and defined within OSI/MHS. A user does not have to be connected to the
subsystem when a message arrives at the local MS; a user can log on to the MS at
any time to retrieve or send messages to other X.400 users.