X.400 Messaging Server Suite Evaluation Guide. Configuring Isode's M-Switch for X.400 Messaging. Isode

Transcription

1 X.400 Messaging Server Suite Evaluation Guide Configuring Isode's M-Switch for X.400 Messaging Isode

2 Objectives This guide will show you how to set up a basic X.400 messaging configuration using Isode servers and management tools. During this evaluation you will: Create, start and connect to a directory server to be used to hold your messaging configuration. Create a messaging configuration and user mailboxes. Exchange X.400 messages using Isode's test X.400 User Agent, Xuxa. Explore some of the operational management capabilities of MConsole. For the purposes of this evaluation guide we have assumed that this is a 'clean' installation of both MVault and M-Switch R16.2. The guide will therefore take you through the process of installing and configuring M-Vault as well as M-Switch. Please do not 'Mix and Match' M-Vault and M-Switch Versions. If you're installing R16.2 M-Switch, make sure that M-Vault is also R16.2 and not an earlier version. You ll use two Isode tools to achieve the objectives of this guide. These are both installed with MSwitch: MConsole is Isode's central tool for M-Switch Configuration and Operational management for both Internet and X.400 Messaging deployments. MConsole will also set up the directory used to hold your messaging configuration and user details. Xuxa is a X.400 user agent that Isode ships to demonstrate some server features. Xuxa should not be deployed operationally, it exists for test purposes only. NOTE FOR WINDOWS USERS: If you're running Windows Vista or Windows 7 you will need to run Isode Management tools (like M-Link Console) as an Administrator. You can do this by right-clicking on the program icons and choosing 'Run as administrator' from the pop-up. Installation Requirements You should visit [ to discover which operating systems are supported for Isode evaluations. Evaluation downloads (excluding documentation) are held in a password-protected section of the Isode website. If you have not already done so you should apply for password access by filling in the form located at [ Installing the Isode Applications Many Isode management tools are written in Java. You should install Java before installing the Isode packages. You can obtain the required packages (Java SE 7 JRE) from [ After obtaining password access to the Isode binary files you should download and install M-Vault and M-Switch following the instructions on the download page for your platform. The number of packages required will vary depending on platform. Obtain a License File Isode products require a valid license from Isode before they will run correctly. Licenses are issued by X.400 Messaging Server Suite Evaluation Guide: Page 2

3 Isode Customer Service. If you haven't already been sent a license when requesting access to the evaluation files, please send a message to request a license to [[email protected]] remembering to specify which Isode server products you need a license file for. By default the license file you receive needs to be installed in \Isode\etc\ (Windows) or /etc/isode/ (Linux) as 'license.dat'. You may have chosen an alternative installation directory when installing the software, in which case you will have to place the license file there. X.400 Messaging Server Suite Evaluation Guide: Page 3

4 Create a Messaging Configuration using MConsole Your messaging configuration will be held in a Directory Server (DSA). In this section we are going to use MConsole to set up the DSA and your messaging configuration. Starting MConsole (Windows) From the Windows 'Programs' menu, select 'Isode 16.2 > MConsole (Message Switch Console)'. Starting MConsole (Linux) Type in the following command: % /opt/isode/bin/mconsole Setting a Bind Profile Passphrase If this is the first time you have run one of the main Isode management GUIs, at startup a window will be displayed asking if you wish to encrypt your bind profile (the answer is Yes) and then asking for a passphrase that will be used for that purpose. Type in the passphrase you want to use to access the bind profile you're about to create and click [OK]. NOTE: You must remember this passphrase as you will be asked to provide (but not set) it every time you start MConsole or other Isode Management GUI. Creating the DSA After setting a bind profile passphrase, MConsole will prompt you to create a DSA to hold your messaging configuration. X.400 Messaging Server Suite Evaluation Guide: Page 4

5 Click on [Yes] and accept the defaults in the DIT Structure Configuration screen (below), the Password configuration screen (making sure to take a note of the password or change it to one of your own). Click on [Next >] and MConsole will create and display Bind profile name and filesystem location for the Directory. Accept the defaults in the two fields and click [Next>]. X.400 Messaging Server Suite Evaluation Guide: Page 5

6 Click [Next >] and accept the defaults on the 'Address Configuration' screen. Click [Next >] to display the 'Confirm Details' screen. Clicking [Finish] will create and start your DSA. You'll then be prompted to connect to the DSA in the 'Bind Profile Management' screen. Click on [Connect] and MConsole will prompt you to create a new MHS configuration in this new DSA. Creating the Messaging Configuration Select the default value of Create a new MHS configuration in a DSA (below), click [Next >] on the 'Isode Bind Profile' screen. X.400 Messaging Server Suite Evaluation Guide: Page 6

7 In the 'Set the Messaging Configuration Base DN' screen select the 'o=messaging' entry as the one under which a messaging configuration will be created. Click on [Next >] and select 'X.400 MTA (M-Switch X.400)' from the 'Messaging Configuration Type' screen. X.400 Messaging Server Suite Evaluation Guide: Page 7

8 MConsole will prompt you for a Market Segment choice, allowing the creation of configurations tailored towards Military X.400 (STANAG 4406), Aviation X.400 (AMHS) or EDI. For the purposes of this evaluation accept the default 'General Purpose' option and click on [Next >]. Specify the fully qualified hostname of the MTA (this will be pre-filled) and click on [Next >]. Enter the authentication details for the MTA Queue Manager. These details are used by MTA clients such as MConsole's Switch View. Now enter an Admin Password and click on [Next >]. You now need to specify the O/R address to be used by the MTA. This is the address used by the MTA as its local O/R address. X.400 Messaging Server Suite Evaluation Guide: Page 8

9 You'll now specify the configuration files to be created for the MTA to be able to initialize its services and startup. The defaults displayed in the next screenshot assume the MTA will be running on the local system. Click on [Finish] and you'll be dropped back into MConsole, with the configuration you've just created displayed. X.400 Messaging Server Suite Evaluation Guide: Page 9

10 X.400 Messaging Server Suite Evaluation Guide: Page 10

11 Installing and Starting Services In this section we're going to use the Isode Service Configuration Tool to create and start Isode services. Starting Services on Windows (Isode Service Configuration tool) Click start from the Programs menu and select 'Isode 16.2 > Isode Service Configuration'. You'll see that the DSA you created earlier has already been started. From the menu select 'Actions > Install Isode Services.' Tick the 'M-Switch', 'M-Store X.400' and 'MSwitch Audit Database' options in the 'Service Selection Type' pop-up and click [Finish]. Start the following services by highlighting them in turn and clicking on the [Start] button: Isode M-Vault (isode.dsa.x) - this will already be running as above Isode M-Switch Queue Manager (isode.pp.qmgr) Isode M-Switch OSI Listener (isode.iaed) Isode AuditDB Embedded HSQLDB Back-end Service (isode.adb.hsqldb) Isode AuditDB Log Parsing Service (isode.adb.lp) Isode M-Store X.400 Server (isode.pumice) Starting Services on Linux For Linux, the required services can be started by executing: # /etc/init.d/pp start # /etc/init.d/isode-hsqldb start # /etc/init.d/adb-lp start # /etc/init.d/pumice start Creating a User Mailbox You now need to create a P7 user mailbox. Go back to MConsole and open the X.400 mailbox view by selecting 'View > X.400 Mailbox Management'. Add a P7 Mailbox by expanding the Routing Tree and right-clicking on the O/R Address node under which you wish to add the user (o=localhost) and selecting 'Add P7 Mailbox'. Choose the 'Common Name' address radio button, click on [Next >] and X.400 Messaging Server Suite Evaluation Guide: Page 11

12 then add a name for the user. Click on [Next >]. In the screens following this step you can edit the O/R address of the user (which should not be necessary for this evaluation) and set the user to have a whitepages entry (click on the relevant radio button to do this, as in the following screenshot). This allows your X.400 User Agent (we'll be using Isode's XUXA X.400 test user agent) to easily access the list of P7 users for addressing in messages. In the next screen you'll be invited to configure the MTA and Message Store the P7 user is to use. For this single MTA/MS system the defaults can be accepted. X.400 Messaging Server Suite Evaluation Guide: Page 12

13 Click [Next >] and in the next screen add the user's P7 Message Store and P3 Access password. These default to randomly generated values. Click on Show to note down and/or change these passwords. Click [Finish] to complete the setup. The user has now been added and is displayed in the mailbox view as shown below. X.400 Messaging Server Suite Evaluation Guide: Page 13

14 Using Xuxa to Send/Receive Messages In this section we are going to use Isode's X.400 test user agent, Xuxa, to connect to the Message Store that we've just configured and to then send and receive a message. Starting Xuxa on Windows Click 'Start' and from the 'Programs' menu, select 'Isode 16.2 > Xuxa (X.400 Demo User Agent)'. Starting Xuxa on Linux Type in the following command: % /opt/isode/bin/xuxa Configuring Xuxa The first time you run Xuxa, it will prompt you to select an existing user in the directory. The P7 user we set up in the previous section can be found by using the White Pages Browser to expand the DIT to find 'cn=p7user1' under cn=white Pages, o=messaging as below. Select the user and click [OK]. You'll be prompted for the user password, as set in the previous section. Sending a Message Click on the Write icon to compose a message. As you set up a White Pages entry for the user earlier in this guide, you can click on the Address Book icon in the composition screen. Now find the user and X.400 Messaging Server Suite Evaluation Guide: Page 14

15 double-click to add the user to the recipient field. Add a subject and content and click on [Send]. A sent message confirmation screen will be displayed and returning to the Xuxa Inbox view will show that the message has been received. As you are both sender and recipient of this message, as soon as you read the message (as recipient) you'll receive (as sender) a Receipt Notification and Delivery Report. X.400 Messaging Server Suite Evaluation Guide: Page 15

16 Adding an Additional Mailbox User in Xuxa You may wish to experiment with sending messages between different users by adding an extra user and using Xuxa to send and receive messages between that new user and the one already set up. You'll first need to create another user mailbox using MConsole. You can do this by repeating the steps outlined in the section Creating a User Mailbox. To set up that User in Xuxa, select 'Preferences' in the 'File' menu, copy your existing account displayed on the right, giving the new account a new name. Now select the new Account from the drop-down. In the Xuxa Accounts section on the left, select P7 Message Store and adjust the following values: Message Store User (O/R) Message Store password (if necessary) Message Store User DN (pick new user using Pick button) You can find the correct values the same way that you did for the original mailbox user you set up in the Creating a User Mailbox section earlier. Click on Bind to the Message Store and then [OK]. You'll be returned to the Xuxa view of the new user. You can switch between users by using the Xuxa Account drop-down under 'File > Preferences.' X.400 Messaging Server Suite Evaluation Guide: Page 16

17 MConsole Operational Management MConsole is Isode's central tool for messaging operational/configuration management and can be used, amongst other things, to monitor message status, message queues, message switch and store status. Message Tracking The Message Tracking Tab, accessible from MConsole's View menu, will show the message you sent in the last section (together with receipt notification and delivery report). Right clicking on the message shows a number of examination and handling options. Double-clicking on the message will drill down into message details. Mailbox and M-Store X.400 Connection Monitoring Mailbox and M-Store connection monitoring can be accessed from 'View > X.400 Messages Stores 'menu in MConsole (you'll need to right click on the store and select 'connect'). X.400 Messaging Server Suite Evaluation Guide: Page 17

18 For detailed information on MConsole features (and how to use them) please refer to the What Next section at the end of this guide where you'll find pointers to MConsole product information as well as the relevant sections of the M-Switch Administration Guide(s). X.400 Messaging Server Suite Evaluation Guide: Page 18

19 What next/other resources Help us improve our Evaluation Guides Producing evaluation guides that are easy to follow and that help evaluators get started with our products is important to us. Please help us improve this guide by ing us at Product Information While following this guide you have installed M-Switch X.400, M-Store X.400 and M-Vault (LDAP/X.500 Directory Server) for more information on these server products, follow the links below: M-Switch X.400: [ M-Store X.400: [ M-Vault: [ You have also used Isode's MConsole (messaging configuration and operational management for internet & X.400 messaging). For more on MConsole see [ Exploring Product Capabilities This guide has covered only the basic setup and monitoring of an X.400 messaging system. To extend your system and explore the capabilities of Isode's management tools further you can read the Administration Guides available from the Isode website in PDF format: The M-Switch Administration Guide (X.400 Messaging) includes detailed information on X.400 messaging system configuration and management, including: Configuring an X.400 Messaging System (Chapter 8) Connecting to other X.400 MTAs (Chapters 13 & 14) In-depth information on MConsole capabilities (Chapter 17) The Message Audit Database (Chapter 21) The M-Switch Administration Guide (X.400 Messaging), together with all other Isode documentation is available from [ Whitepapers Isode regularly publishes whitepapers relevant to X.400 messaging markets (including EDI, Military Messaging and Aviation (AMHS) Messaging). All whitepapers can be searched from the whitepaper index page on the Isode website at [ You can browse whitepapers relevant to your particular area of interest by following the links on the sub-menu on the left hand side of that page. X.400 Messaging Server Suite Evaluation Guide: Page 19

20 Isode The Isode Logo and Isode are trade and service marks of Isode Limited. All products and services mentioned in this document are identified by the trademarks or service marks of their respective companies or organizations, and Isode Limited disclaims any responsibility for specifying which marks are owned by which companies or organizations. Isode software is copyright Isode Limited , All rights reserved. Isode software is a compilation of software of which Isode Limited is either the copyright holder or licensee. Acquisition and use of this software and related materials for any purpose requires a written licence agreement from Isode Limited, or a written licence from an organization licensed by Isode Limited to grant such a licence. This manual is copyright Isode Limited. X.400 Messaging Server Suite Evaluation Guide: Page 20