OSI/MHS Administrative Utility (AU) Manual Abstract The OSI/MHS Administrative Utility (AU) allows you to obtain information about messages, reports, or probes (communications sent by an originator to the message transfer system (MTS) to test delivery of a message or report) in the form of Protocol Data Units (PDUs). This manual describes how to install and configure the AU, and it is intended for people who plan, install, configure, run, and operate the AU on a Compaq OSI/MHS subsystem.
Document History Part Number Product Version Published 126168 OSI/MHS AU D30 June 1996 132294 OSI/MHS AU D41 February 1997 424826-001 OSI/MHS AU D42 December 1999 Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your local sales representative. Document Disclaimer Information contained in a manual is subject to change without notice.
OSI/MHS Administrative Utility (AU) Manual Glossary Index Figures Tables What’s New in This Manual iii Manual Information iii New and Changed Information iii About This Manual v Related Manuals v Your Comments Invited viii Notation Conventions viii Abbreviations xii 1. Introducing the Administrative Utility Overview of the AU Design 1-1 2. Installing and Configuring the Administrative Utility Planning Configuration of the AU 2-1 Step-by-Step Installation 2-2 3.
3. Using the Administrative Utility (continued) Contents 3. Using the Administrative Utility (continued) Subsystem Statistics Screen 3-10 Additional Information About the AU 3-10 A. Recommended Settings for Your Browser Glossary Index Figures Figure i. OSI/MHS Manual Set vi Figure 1-1. Components of the AU and Their Relationships 1-2 Figure 3-1. AU Screens and Their Relationships 3-1 AU Pathway Parameters Described 2-3 Tables Table 2-1.
What’s New in This Manual Manual Information Tandem OSI/MHS Administrative Utility (AU) Manual Abstract The Compaq OSI/MHS Administrative Utility (AU) allows you to obtain information about messages, reports, or probes (communications sent by an originator to the message transfer system (MTS) to test delivery of a message or report) in the form of Protocol Data Units (PDUs).
What’s New in This Manual New and Changed Information OSI/MHS Administrative Utility (AU) Manual—424826-001 iv
About This Manual The Compaq OSI/MHS Administrative Utility (AU) allows you to obtain information about messages, reports, or probes in the form of Protocol Data Units (PDUs). You access the AU interface by using a World Wide Web browser. This version of the AU works under HTML version 2.0; if your browser does not support this version, some variation in formatting may result.
Related Manuals About This Manual • • OSI/MHS SCF Reference Manual describes the SCF commands used to configure and manage the OSI/MHS subsystem. These commands are the interactive equivalents of the programmatic commands described in this manual. OSI/MHS Management Programming Manual describes the programmatic and event management interfaces used by management applications to manage OSI/MHS.
Related Manuals About This Manual For background information on the Compaq environment, you can read the following manuals: • • • Introduction to Compaq Networking and Data Communications, which provides an overview of Compaq networking and data communications products. Introduction to Distributed Systems Management (DSM), which introduces the products and components called, collectively, Distributed Systems Management. It also discusses subsystem enhancements to support DSM.
Your Comments Invited About This Manual Your Comments Invited After using this manual, please take a moment to send us your comments. You can do this by returning a Reader Comment Card or by sending an Internet mail message. A Reader Comment Card is located at the back of printed manuals and as a separate file on the User Documentation disc. You can either fax or mail the card to us. The fax number and mailing address are provided on the card.
General Syntax Notation About This Manual each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num] [ text] K [ X | D ] address-1 { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines.
Notation for Messages About This Manual Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] CONTROLLER [ , attribute-spec ]... !i and !o.
Notation for Messages About This Manual lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed.
Abbreviations About This Manual Abbreviations The following list defines abbreviations used in this manual and in other Compaq OSI/MHS manuals. Both industry-standard terms and Compaq terms are included; Compaq terms are marked as such. ADMD. Administration management domain API. Application program interface APIA. Application Program Interface Association ASN.1. Abstract Syntax Notation One AU. Access unit BER. Basic encoding rules CCITT. International Telegraph and Telephone Consultative Committee DDL.
Abbreviations About This Manual IDU. Internal data unit IM. Interpersonal messaging IPC. Interprocess communication IPM. Interpersonal message IPN. Interpersonal notification ISO. International Organization for Standards MD. Management domain MH. Message handling MHS. Message handling system MOTIS. Message-Oriented Text Interchange System MPDU. Message protocol data unit MR. Message relay MRP. Message relay process MS. Message store MTA. Message transfer agent MTS. Message transfer system NBPS.
Abbreviations About This Manual PDU. Protocol data unit PRMD. Private management domain RTS. Reliable transfer service RTSE. Reliable Transfer Service Entity SC. Store cleaner SCF. Subsystem Control Facility (Compaq term) SCP. Subsystem Control Point (Compaq term) SPI. Subsystem Programmatic Interface (Compaq term) TAL. Transaction Application Language (Compaq term) TMF. Transaction Management Facility (Compaq term) UA. User agent UTC. Universal Coordinated Time XAPIA. X.
1 Introducing the Administrative Utility The OSI/MHS Administrative Utility (AU) product supports AU-specific requests and responses between an AU server and a World Wide Web browser, which provides the user interface (see Appendix A, Recommended Settings for Your Browser, for information about setting up your browser for best viewing of the AU screens).
Overview of the AU Design Introducing the Administrative Utility Figure 1-1.
Introducing the Administrative Utility Overview of the AU Design in Section 2, Installing and Configuring the Administrative Utility, for more information about the Pathway parameters used for the AU. The following events occur before a the URL for the AU is opened or anytime the Web browser sends a request to the AU-DISTRIBUTOR class: • • • After detecting the request, the AU-DISTRIBUTOR class performs a Pathsend procedure call to the AU-SERVER class.
Introducing the Administrative Utility Overview of the AU Design OSI/MHS Administrative Utility (AU) Manual—424826-001 1 -4
2 Installing and Configuring the Administrative Utility To install the AU product, a master user creates an AU user-permissions database and configures the AU Pathway server classes for the OSI/MHS subsystem to be administered (See Step-by-Step Installation on page 2-2 for details about establishing a master user).
Installing and Configuring the Administrative Utility Step-by-Step Installation Step-by-Step Installation The following procedure describes how to install and configure the OSI/MHS AU product: Note. If you have chosen a configuration requiring more than one user-permissions database, repeat steps 1 and 2 of the following procedure for each user-permissions database you will be using. 1. Create the AU user-permissions database file.
Installing and Configuring the Administrative Utility Step-by-Step Installation The following example shows what you should enter to create a Pathway server for the AU: PATHMON /NAME $MWEB,nowait/ PATHCOM /IN AUCNFG/ $MWEB Table 2-1 describes the AU-specific parameters for the AU-DISTRIBUTOR and AU-SERVER classes. Table 2-1. AU Pathway Parameters Described Parameters Description Example AUD-PORT The TCP/IP port that the AU-DISTRIBUTOR class listens to for connections.
Installing and Configuring the Administrative Utility Step-by-Step Installation 3. If you are the master user, define user permissions for accessing the AU. Only the master user can perform the initial access to the AU. If you do not wish to use the default TCP/IP connection, the master user may specifically define the Guardian TCP/IP process in the AUCNFG file. (See the Pathway/TS TCP and Terminal Programming Guide and the NonStop TCP/IP and IPX/SPX Programming Manual for more detailed information.
3 Using the Administrative Utility This section explains how you access and use the AU from a Web browser. See Appendix A, Recommended Settings for Your Browser, for information about setting up your browser for best viewing of the AU screens. Figure 3-1 shows the various navigation paths you can follow and the screens you encounter when you use the AU. Note that the bold-lined boxes indicate the options available on the control screen (the first screen you see after you have logged on). Figure 3-1.
Using the Administrative Utility Details of the AU Screens Details of the AU Screens The following subsections describe each screen shown in Figure 3-1. Logon Screen The browser displays the logon screen when you open the URL for the AU. You must enter a Guardian user name (in the form groupname.username) and password.
Using the Administrative Utility • • • User Permissions Screen List Gateway PDUs View Subsystem Statistics Define User Permissions Note. Only the master user can see the “Define User Permissions” option. User Permissions Screen The user permissions screen appears if the master user selects the “Define User Permissions” option on the control screen.
Subsystem List Screen Using the Administrative Utility The middle section of the screen allows you to filter PDUs in the subsystem. The pop-up menu under “Select Class/Group:” allows you to choose from among all the classes and groups configured for the OSI/MHS subsystem. The checkboxes and radio buttons under “Select State:” allow you to further filter PDUs in a particular state.
Route Retry and Link Retry Queue List Screens Using the Administrative Utility • • Archived PDUs All bad PDUs Route Retry and Link Retry Queue List Screens The route retry and link retry queue list screens display the list of PDUs in the route retry or link retry queue. These screens appear when you select either the “List Route Retry PDUs” or “List Link Retry PDUs” button on the control screen. The screens display the following information for each PDU: PDU-ID The PDU ID in component form.
Gateway Filter Screen Using the Administrative Utility START-TIME The date and time the PDU started the retry sequence. PRIORITY The priority of the message. STATUS The following to indicate the current state of the message: QUEUED Awaiting expiry of timer (next-action time). If it is available, the MPDU ID (which includes the country name and optionally the ADMD, PRMD, and a unique identifier) appears under the PDU ID.
Gateway Queue List Screen Using the Administrative Utility If the message “No Entry Manager available for gateway-object- name” appears below the list of PDUs, you may need to verify that the appropriate entry manager process is running. For information about entry manager operation, see the Compaq’s OSI/MHS configuration and management manual.
PDU Options Screen Using the Administrative Utility generate nondelivery reports for messages and probes represented by PDUs you have selected for removal from the queue. From the gateway queue list, you can select an individual PDU by clicking on the PDU ID shown on the screen. The PDU options screen for the selected PDU appears. See PDU Options Screen below for details about the PDU options screen.
PDU Options Screen Using the Administrative Utility The “Protocol Options” section of the PDU options screen provides choices for displaying the PDU when you choose the “Decode Trace” or “Decoded Message” display. The following options are available: Envelope The protocol that displays the envelope of the PDU. The protocol can be P1, P2, P3, or ROSE (includes P7). The default is P1. Content If selected, the message content appears.
Using the Administrative Utility Subsystem Statistics Screen Depending on the state of the PDU, the following buttons appear in the bottom section of the PDU options screen: Display PDU Appears for any PDU and causes the PDU data screen to appear for the specified display type. Activate PDU Only appears for a PDU if the PDU is on the link retry or route retry queue. Only PDUs that have been suspended can be activated.
Using the Administrative Utility Additional Information About the AU OSI/MHS Administrative Utility (AU) Manual—424826-001 3- 11
Using the Administrative Utility Additional Information About the AU OSI/MHS Administrative Utility (AU) Manual—424826-001 3- 12
A Recommended Settings for Your Browser You can use the AU product with any standard Internet browser that supports HTML 2.0.
Recommended Settings for Your Browser OSI/MHS Administrative Utility (AU) Manual—424826-001 A- 2
Glossary ADMD (administration management domain). An X.400 domain managed by an administration, such as a government or a public service. ADMDs can send, receive, and provide intermediate routing for messages. administrative management domain. See ADMD class. A grouping or category of objects, based on their shared purpose and internal structure.
message Glossary message. A communication, typically consisting of multiple, related data elements and control information. In X.400, an information object that consists of an envelope and its contents. The envelope identifies the originator and the potential recipient of the message and documents its path through the system. message protocol data unit. See MPDU message transfer agent. See MTA message transfer system. See MTS MPDU (message protocol data unit).
P3 protocol Glossary P3 protocol. The X.400 message transfer system access protocol, which defines a standard for the submission and delivery of messages and the interaction of user agents (UAs) and message transfer agents (MTAs). (See the CCITT standards documentation for X.411.) P7 protocol. The X.400 message store access protocol, which defines access to the message store by remote or local user agents. (See the CCITT standards documentation for X.413.) PAM. See Port Access Method.
ROSE (remote operations service element) Glossary ROSE (remote operations service element). An Application Layer service definition and protocol supporting interactive applications, implemented by the RS process in OSI/MHS. Examples of ROSE PDUs are: ROIV-APDU Invoke application protocol data unit RORJ-PDU Reject application protocol data unit ROER-APDU Error application protocol data unit RORS-APDU Response application protocol data unit uniform resource locator.
Index A Abbreviations Abbreviations-1 Acronyms Abbreviations-1 Activating PDUs 3-10 ADMD 3-4, 3-5, 3-6 Administration management domain (ADMD) See ADMD Administrative Utility (AU) accessing services of 1-2 defined 1-1 installing 2-2 Archived PDUs 3-5 ASN.
G Index G N Gateway queue 3-6, 3-7, 3-10 Gateway queue filter screen described 3-6 Gateway queue list screen described 3-6 Gateway-queued PDUs 1-3 Groups 3-4 Nondelivery reports 3-8, 3-10 I P Inactive PDUs 3-4 Internal trace elements 3-9 Invalid-MS PDUs 3-4 Parameter AUD-MANAGER 2-3 AUD-PORT 1-2, 2-3 AUD-SERVER 2-3 AUS, starting with 2-2 AUS-AUUSERS-FILENAME 2-2, 2-3 AUS-DB-SUBVOL 2-3 AUS-LOGONTXT-FILENAME 2-3 AUS-SUBSYS 2-3 Pathsend procedure call 1-1, 1-3, 2-3 Pathway monitor process 2-3 paramete
R Index PDU class 3-4 creation time 3-4, 3-6 data 1-3 envelope 3-9 envelope protocol P1 3-9 P2 3-9 P3 3-9 P7 3-9 ROSE 3-9 group 3-4 log records 3-4, 3-8 string length 3-9 PDU database 1-3 PDU ID 3-4, 3-5, 3-6, 3-7 64 bit number form 3-3 component form 3-3 PDU options screen described 3-8 PDU store 3-4, 3-10 PDUs activating 3-10 deleting 3-4, 3-10 displaying 3-10 listing 3-3, 3-6 removing 3-10 suspending 3-10 viewing 3-3, 3-6 Private management domain (PRMD) See PRMD PRMD 3-4, 3-5, 3-6 Product subvolume 2-
U Index OSI/MHS Administrative Utility (AU) Manual—424826-001 Index -4
