An Example Simulation [ HP DeskManager Customization ] MPE/iX 5.0 Documentation
HP DeskManager Customization
An Example Simulation
To see how the Foreign Service Connection works in HP Desk, the following
simulation can be done:
Firstly an FSC gateway must be configured in Mailconfig. This is similar
to configuring a remote computer gateway, but it has some additional
fields such as the type of ARPA format you wish to use. The name of an
IPC file must also be entered to pass information from one process to
another.
After setting up the FSC gateway, the next step is to create a mailnode
for users to send to that gateway, and a route from the mailnode to the
FSC gateway, similar to setting up remote mailnodes.
When a user sends to someone configured on a foreign mailnode, the
message is processed by the Master Truck. Also the the ARPA header is
attached to the message. Then HP Desk tries to convert anything in the
message to ASCII text. Finally the Master Truck creates an E file in the
group HPMAIL.HPOFFICE. The final job of the Master Truck is to write to
the IPC file with the name of the E file. At this point HP Desk has
completed its job. To transfer the message to a foreign system, another
piece of software must be used. This could be an Hewlett-Packard
supplied package, such as HP Office Connect to PROFS or HP Office Connect
to DISOSS or it could be a customer written application. Whatever
software is used it must:
* Read the IPC file noting the name of the E file in the IPC file.
* Process the E file and handle whatever type of datacomm link is
necessary to transport to the foreign machine.
Incoming messages are handled in a similar fashion with the software
package creating E files, and writing to the HP Desk IPC file
ARPAIPC.MAILDB.HPOFFICE. The FSC Slave Truck waits on this IPC file and
delivers any messages it finds into the Desk system.
So to simulate this we could do the following:
1. Run Mailconfig, and create an FSC gateway called FSCGAT. Call the
IPC file FSCIPC--this name is up to you. It is generally put in
the group HPMAIL.HPOFFICE, although it can be put in another
group. Use ARPA format 2. Make the gateway availability all
"4"s.
2. Create a test mailnode for the gateway called FSCLOC/01.
3. Create a route from FSCLOC/01 to gateway FSCGAT.
4. Create a local user named "Test User" on a mailnode "HP/01".
5. Exit Mailconfig.
6. Signon as MGR.HPOFFICE,HPMAIL and BUILD the IPC file.
:BUILD FSCIPC;MSG;REC=-80,,F,ASCII;DISC=1024
7. Run HP Desk. For this simulation pretend that your mailnode is
HP/01. Since this is a simulation we are going to send a message
to a local user by sending it out through the FSC gateway to an E
file, and then deliver it back to the local Desk system. So SEND
to the user you created:
TO: Test USER(HP/01)/FSCLOC/01
The number in parentheses is the foreign address, or the address
that the message will be delivered to when it reaches the foreign
system. In this simulation it is the local mailnode since we are
delivering the message back to the local system. Note that the
message is sent to a mailnode called FSCLOC/01 in the same way
that a non-FSC message would be.
8. If you have a Master Truck running, FSCIPC.HPMAIL.HPOFFICE will
soon have an EOF of "1", and there will be an E file in the same
group. You may want to FCOPY the E file to your screen to see
what the ARPA header looks like. To do this you will first have
to get the name of the file from the IPC file. To do a
non-destructive read on the IPC file, use the following commands:
:FILE FNAME=FSCIPC.HPMAIL.HPOFFICE;COPY
:FCOPY FROM=*FNAME;TO;HEX;CHAR
9. This is the point where the other software packages take over, but
in this simulation the message will be brought back into HP Desk:
:FCOPY FROM=FSCIPC.HPMAIL.HPOFFICE;TO=ARPAIPC.MAILDB.HPOFFICE
The message is now ready to be processed by the FSCARPA Truck.
10. Issue the MAILFSCARPAON command and the message will be delivered
to the user.
11. Log on as the user to make sure that the message has arrived.
12. You can see that the message has gone through an FSC gateway by
reading the message, and seeing that Part 2 of the message has an
ARPA header.
MPE/iX 5.0 Documentation