[Top] [Prev] [Next] [Bottom]




GroupWise deployment


MAILsweeper for GroupWise provides protection between two GroupWise domains.

This protection can be provided between:

Messages are routed between the two domains via API (Application Programming Interface) gateways.

The API gateways for each domain must be purchased separately.

When a message is routed between the two GroupWise domains the message server in the originating domain delivers it initially to an API gateway. At this point MAILsweeper intercepts and examines the message. If it is safe for onward delivery, the message is delivered to the API gateway in the destination domain. The message server in the destination domain then routes it to its intended destination.

When MAILsweeper is deployed between a primary and secondary domain there is no automatic directory synchronisation. This is due to a GroupWise limitation.

Primary to primary domain

Deployment between two primary domains is achieved by placing MAILsweeper between two API gateways. This allows MAILsweeper to intercept all mail between the two domains.

For example:

To deploy MAILsweeper for GroupWise in a primary to primary domain follow the steps outlined below.

1. Install a Windows NT machine to act as the MAILsweeper host.

This machine should meet the technical specification outlined. It should also have TCP/IP and RPC services installed and enabled. See page 2-85 for a full list of pre-requisites the MAILsweeper host should be configured with.

2. Load any anti-virus tools that you wish to use with MAILsweeper and note their locations. You will be asked for this information later, during the installation.

Check the release notes to ensure compatibility between this release of MAILsweeper and the anti-virus tools you wish to use.

There are several evaluation copies of anti-virus tools supplied on the installation CD-ROM. Note that the set-up software does not automatically install these anti-virus tools.
3. Create and configure two API gateways, one for each domain, between which messages are routed.

See the API gateway configuration section on page 2-110 for details.

4. Set up routing.

See the Setting up routing section on page 2-111 for details.

5. Install MAILsweeper for GroupWise.

See the Installation section on page 2-119 for details.

API gateway configuration

Messages are routed between the domains via API gateways. You will need to create and configure two API gateways, one for each domain. This is achieved using the following steps:

1. Using Admin in the Admin Domain, create an API gateway (API Gateway 1 in the figure) and configure it as follows:
a. Set Gateway execution to MS Launch (assuming a DOS API gateway is used).
b. Set Executable filename to API.EXE.
c. Select Settings and set MS Launch Cycle to 1 minute (this is optional).
d. Select Optional, then Settings and enable Directory Synchronisation, Directory Exchange and Accounting. Set Outbound Status Level to Full.
e. Select Specific and set Addressing Format to GroupWise.
f. Select DS Export Fields and enable all options (this is the default setting).
g. Select Output Conversions and disable all options (this is the default setting).
h. Create a MAILsweeper administrator's account in GroupWise (this can be the same user as the email administrator).
2. Using Admin in the R&D Domain, create an API gateway (API Gateway 2 in the figure). This is achieved in an identical manner as for the Admin Domain. Follow step 1. except, in this case, do not enable Directory Synchronisation (step 1. d).
3. Run GroupWise Message Servers to synchronise the domains and ensure both domains are aware of the new gateways.

Setting up routing

Before MAILsweeper installation, routing is as follows:

Routing from Admin Domain  
Destination

R&D Domain

Routing

Direct

 
Routing from R&D Domain  
Destination

Admin Domain

Routing

Direct

 

After MAILsweeper installation, routing should be as follows:

Routing from Admin Domain  
Destination

R&D Domain

Routing

via API Gateway

 
Routing from R&D Domain  
Destination

Admin Domain

Routing

via API Gateway

 

This is achieved using the following steps:

1. Using Admin in the Admin Domain:
a. Edit the R&D Domain and set the domain type to Foreign. To do this you may have to re-create the domain exactly as before, with the exception of the domain type being Foreign.
b. Select Message Server Configuration then Network Links.
c. Change routing to the R&D domain from Direct to Gateway and select the API gateway.
2. Using Admin in the R&D domain:
a. Edit the Admin Domain and set the domain type to Foreign. To do this you may have to re-create the domain exactly as before, with the exception of the domain type being Foreign.
b. Select Message Server Configuration then Network Links.
c. Change routing to the Admin Domain from Direct to Gateway and select the API gateway.
Refer to your GroupWise documentation for more details.
 

Primary to secondary domain

Deployment between a primary and a secondary domain is achieved by creating a `foreign domain' between the two domains.

This domain acts as a protection domain and is home to MAILsweeper. Messages are routed between the domains via the API gateways.

For example:

As a result of a GroupWise limitation there is no directory synchronisation or exchange in this environment.

To deploy MAILsweeper for GroupWise between a primary to secondary domain follow the steps outlined below.

1. Install a Windows NT machine to act as the MAILsweeper host.

This machine should meet the technical specification outlined. It should also have TCP/IP and RPC services installed and enabled. See page 2-118 for a full list of pre-requisites the MAILsweeper host should be configured with.

2. Load any anti-virus tools that you wish to use with MAILsweeper and note their locations. You will be asked for this information later, during the installation.

Check the release notes to ensure compatibility between this release of MAILsweeper and the anti-virus tools you wish to use.

There are several evaluation copies of anti-virus tools supplied on the installation CD-ROM. Note that the set-up software does not automatically install these anti-virus tools.

3. Create and configure two API gateways, one for each domain, between which messages are routed.

See the API gateway configuration section on page 2-115 for details.

4. Set up routing.

See the Setting up routing section on page 2-116 for details.

5. Install MAILsweeper for GroupWise.

See the Installation section on page 2-119 for details.

API gateway configuration

To configure the API gateways use the following steps:

1. Using Admin in the Admin Domain, create a domain of type Foreign (MSW Domain in the figure). This is necessary as it is only possible to route a GroupWise API gateway to a foreign domain.
2. Using Admin in the Admin Domain, create an API gateway (API Gateway 1 in the figure) and configure it as follows:
a. Set Gateway execution to MS Launch (assuming a DOS API gateway).
b. Set Executable filename to API.EXE.
c. Select Settings and set MS Launch Cycle to 1 minute (this is optional).
d. Select Specific and set Addressing Format to GroupWise.
e. Select DS Export Fields and enable all options (this is the default setting).
f. Select Output Conversions and disable all options (this is the default setting).
g. Create a MAILsweeper administrator's account in GroupWise (this can be the same user as the email administrator).
3. Using Admin in the R&D domain, create an API gateway (API Gateway 2 in the figure). This is done in the same way as for the Admin Domain. Follow step 2. above.
4. Run GroupWise Message Servers to synchronise domains and ensure both domains are aware of the new foreign domain and API gateways.

Setting up routing

Before MAILsweeper installation, routing is as follows:

Routing from Admin Domain  
Destination

R&D Domain

Routing

Direct

 
Routing from R&D Domain  
Destination

Admin Domain

Routing

Direct

After MAILsweeper installation, routing should be as follows:

Routing from Admin Domain  
Destination

R&D Domain

Routing

InDirect via MSW Domain

MSW Domain via API Gateway
 
Routing from R&D Domain  
Destination

Admin Domain

Routing

InDirect via MSW Domain

MSW Domain via API Gateway
 

This is achieved using the following steps:

1. Using Admin in the Admin Domain:
a. Edit the Admin Domain.
b. Select Message Server Configuration then Network Links.
c. Change routing to the R&D Domain from Direct to Indirect via the foreign domain (MSW in the figure).
d. Set routing to the foreign domain to Gateway via the correct API gateway (API Gateway 1 in the figure).
e. Edit the R&D Domain and set the network link for the Admin Domain to None.
2. Using Admin in the R&D Domain:
a. Edit the R&D Domain.
b. Select Message Server Configuration then Network Links.
c. Change routing to the Admin Domain from Direct to Indirect via the foreign domain (MSW in the figure).
d. Set routing to the foreign domain to Gateway via the correct API gateway (API Gateway 2 in the figure).
e. Edit the Admin Domain and set the network link for the R&D Domain to None.
Refer to your GroupWise documentation for more details.
 


[Top] [Prev] [Next] [Bottom]



msw.support@mimesweeper.com

Copyright © 1998, Content Technologies Limited. All rights reserved.