Cross-Domain setup

The installation instructions provided by Rocket Software, while very helpful, are not specific enough on some items when trying to set up a system for Cross-Domain login. Below is a list of items we needed to do to get this up and running. To be fair, much of this work and discovery was done by Rocket Software support as they helped us a great deal. Because of all the things we did it may turn out some of this is unnecessary, but I felt it best to put everything in.

First - at the pc level

1. The pc needs to have the .net 3.5 framework with service pack 1

2. Open ports 11000 and 808 (only 808 is required, it is the port that WCF is connecting through)

3. Add the IP address of the communications server to c:\windows\system32\etc\hosts (this should not be required if the DNS is working correctly)

Second - Database/Application server, Active Directory/Workgroup, Network

1. The user needs to be set up on the domain controller, if using a workgroup the user must be set up in windows on the SBXA communcations server.

2. SB+ users set up for cross-domain login need all the single sign on information set up just as if you were doing single sign on, with the exception of the Auto Login, leave that set to 0. (This step is independent of cross domain installations, i.e. it needs to be setup regardless of where the user is connecting from.)

3. Open port 808 on firewall. (If the Application Server, i.e. the server where UniVerse or UniData is installed on, is a different machine from the Communications Server, then port 808 does not need to be opened, however port 11000 does need to be open.)

Third - Certificates

1. The name of the certificate needs to match the name of the server exactly, case sensitive.

2. To create cert, from c:\program files\Microsoft SDK's\Windows\v6.1\Bin run &gt;makecert -n "CN=servername" -pe -sr localmachine -ss My -a sha1 -sky exchange

3. If you need to remove the cert, before re-creating it. From c:\program files\Microsoft SDK's\Windows\v6.1\Bin run &gt;certmgr -del -s -r localmachine -ss My -all

4. To see the certificate created. From c:\program files\Microsoft SDK's\Windows\v6.1\Bin run &gt;certmgr -v -s -r localmachine My | more

Finally - Licensing

1. Your profile on U2BC must be updated as using the SBXA version before licensing.

2. Use SBXA after serial number when licensing the product.

Obviously, some of this will probably change over time as the product matures and I may be forgetting a few items. But, hopefully it will help relieve some frustration for others.