OSI/MHS Configuration and Management Manual

Planning Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual424827-003
3-6
Using OSI/MHS as a Message Store
To connect to the MS, a UA accesses the message store through the OSI/AS services
using an X.25 or LAN connection. If you plan to use the OSI/MHS subsystem as a
message store, you should consider the following:
How many MS users will you have? (Each MS group can have up to 1000 user
mailboxes.)
How many MS groups will you need?
What is the pattern of message flow?
What are your capacity expectations?
What are your average message-storage requirements? What are your peak
message-storage requirements? Both of these needs affect the sizing of your
PDU stores and SQL database.
What are your retrieval and submission rates?
What do you expect to be the average size of messages going through the
subsystem? (The maximum size of each message is 10 MB for a local user
agent and 2 MB for a remote user agent.)
What message attributes do you want to use as the basis for retrieval of messages
from the message store? For example, do you want to filter on the delivery
envelope? The sequence number? You specify these attributes through the ADD
APPL command.
Where does this message store fit in the O/R name hierarchy? Does this MS
represent all the users in an organizational unit, or does this MS represent the
organizational unit only?
How do you plan to set up the SQL environment for the message stores? For
information, see the NonStop SQL/MP Installation and Management Guide.
What type of accounting information do you want to collect?
What are the physical connections to the UAs? How will you access the
communications lines?
What are your availability and throughput needs? This factor will affect the number
of RS, LO, and MR groups you configure.
What are the OSI addressing requirements?
You configure a UA through the following objects:
APPL object of the MS type
MS CLASS object
RS CLASS object
LO CLASS object
Appendix B, Configuration Checklists, contains checklists for configuring local and
remote UAs.