HP 3000 Manuals

Configuring an API Client [ Installing and Configuring HP X.400 Administrator's Guide ] MPE/iX 5.0 Documentation


Installing and Configuring HP X.400 Administrator's Guide

Configuring an API Client 

Configure an API client only if you are using the API. A maximum of 200
API clients, adjacent MTAs, and HP X.400/HP Desk Nodes can be configured.

To configure an API client:

   *   Select the CLIENT item from the Configure X.400 Menu.

This displays the Configure API Clients screen. 

[]
Figure 7-17. Configure API Clients Menu The fields on this screen are: API Client Name Display. A uniquely defined API client name (does not match any other client, adjacent MTA, HP X.400/HP Desk node, Sendmail connection, OpenMail connection, or local MTA name). This is the name registered by the HP X.400 application using the x4_register routine. The name is a printable string of up to 32 characters. Output Queue Display. The output queue assigned by the MTA to the API client. O/R Attributes Display. A list of the O/R attributes assigned to this API client (for example, country name, ADMD, PRMD, organization name, and organization units). All attributes that fit on the screen are displayed. To add, modify, or delete a client, * Press the Action Menu key to display the Action Menu so you can add a client, modify a client, or delete a client. Adding an API Client To add an API client, * Select Add API Client from the Configure API Clients Action Menu. This displays the Add API Client screen.
[]
Figure 7-18. Add API Client Screen The fields on this screen are: API Client Name Required. Enter a uniquely defined API client name (cannot match any other client, adjacent MTA, HP X.400/HP Desk node, Sendmail connection, OpenMail connection, or local MTA name). This is the name registered by the HP X.400 High-Level API application using the x4_register routine. The name is a printable string of up to 32 characters. Output Queue Display. The output queue assigned by the MTA to the API client. If you are adding a client, this field is blank. Country Code Display. Country of the local MTA. Administration Domain Name Display. ADMD of the local MTA. Private Domain Name Display. PRMD of the local MTA. Organization Name Optional. Enter the organization name assigned to the API client. The name is a printable string of up to 64 characters. The wildcard, asterisk (*), and the null character (#)are not allowed in this attribute for the primary route. Organization Unit Name 1-4 Optional. Enter the organization unit names assigned to the API client. Each organization unit name is a printable string of up to 32 characters. The wildcard, asterisk (*), and the null character (#)are not allowed in this attribute for the primary route. One primary route to the API client is created automatically when the API client is configured. Additional routes can be configured for the API client by selecting the ROUTES item on the Configure X.400 Menu. If the route configured to this API client is not a valid 1984 X.400 standard address form, a warning message displays. 1984 X.400 systems may not be able to handle such O/R addresses. Take this into consideration when configuring an O/R address for the first route to an API client. See the O/R Address Attributes and Forms section in Chapter 2 for more information on 1984 X.400 standard address forms. When the fields on the screen are correctly defined, * Press the Perform Task key to save the data. * Press the Exit Task key to return to the Configure API Clients screen. If you need to cancel the data you just typed, * Press the Exit Task key and return to the Configure API Clients screen. If you want to define additional routing attributes, * Press the Action Menu key to display the Action Menu so you can select Terminal Address Fields, Personal Name Fields, or Domain Defined Attributes. Refer to the "Adding a Route" section of the "Configuring Routes and Alternate Routes" chapter for more information on these windows. When defining additional routing attributes, * The Common Name field does not appear in the Personal name Fields window. * The wildcard, asterisk (*), and null character (#) are not allowed. Modifying an API Client To modify an API client, * Select the API client to be modified from the Configure API Client screen. * Press the Action Menu key. * Select Modify API Client from the Configure API Client Action Menu. This displays the Modify API Client screen.
[]
Figure 7-19. Modify API Client Screen For a description of the fields, refer to the Add API Client screen field descriptions. When the fields on the screen are correctly defined, * Press the Perform Task key to save the data. * Press the Exit Task key to return to the Configure API Clients screen. If you need to cancel the data you just typed, * Press the Exit Task key and return to the Configure API Clients screen. If you want to define additional routing attributes, * Press the Action Menu key to display the Action Menu so you can select Terminal Address Fields, Personal Name Fields, or Domain Defined Attributes. Refer to the Adding a Route section in this chapter for more information on these windows. When defining additional routing attributes, * The Common Name field does not appear in the Personal name Fields window. * The wildcard, asterisk (*), and null character (#) are not allowed. Deleting an API Client To delete an API client, * Select the API client to delete from the Configure API Client screen. * Press the Action Menu key. * Select Delete API Client from the Configure API Client Action Menu. This displays the Delete API Client screen.
[]
Figure 7-20. Delete API Client Screen To delete the information for the selected API client, * Press the Confirm key. To cancel the delete operation, * Press the Cancel key.


MPE/iX 5.0 Documentation