Amadeus cookies policy - you'll see this message only once.

Amadeus use cookies on this website. They help us to know a little bit about you and how you use our website, which improves the browsing experience and marketing - both for you and for others. They are stored locally on your computer or mobile device. To accept cookies, continue browsing as normal. Or, go to the privacy policy for more information.

Distributing Connection Profiles to Enterprise Guide Users

Deploying a new version of Enterprise Guide across an organisation can be challenging, with pre-requisite installation requirements and compatibility of current EG projects as important considerations. The provision of a standard connection profile, which contains pre-defined references to a SAS metadata server can make the transition more manageable.

The SAS Enterprise Guide Explorer application is used to create this and can be opened from the 'Tools' menu in Enterprise Guide.

The 'Profile Deployment Wizard', accessed from the Explorer's 'Tools' menu provides a step by step approach for standardising and deploying a profile. It involves four key stages:

  1. Setting up the profile
  2. Verifying the profile
  3. Specifying the location for an update file (which when accessed will apply the new profile)
  4. Specifying the location for the configuration file which contains the new profile.

For step 1, the configure profiles button opens the 'Connections' dialog which enables one or more profiles to be defined. The dialog used here is the same as is used in Enterprise Guide. If there are multiple servers or environments (e.g. dev, test, live) to connect to, it may be advisable to set up separate connection profiles for each one. These profiles should consist of a meaningful profile name, the details of the remote server and port and they should also contain your user name and password. Don't worry, these credentials will not form part of the final package but will at least enable us to verify the profile in the next step.

Distributing a Standard Connection Profile to groups of Enterprise Guide Users2

On saving all profiles, we can then move onto the verification stage where each connection can be tested by selecting 'Begin Test'.

Distributing a Standard Connection Profile to groups of Enterprise Guide Users3

The location of the update file then needs to be specified along with the location of two XML files which contain the profile configuration. SDSUpdate.xml is the key file here as it contains the profile but without the credentials entered earlier. That's it for creating the default profile!

On deploying Enterprise Guide, the only thing which each user now needs to do is select the Connection profile link in the bottom right hand corner to open the 'Connections' dialog.

The location where the SDSUpdate.xml file has been saved should be specified on the 'Updates' tab. This will ensure the profile is automatically applied.

Distributing a Standard Connection Profile to groups of Enterprise Guide Users4

Enterprise Guide will request the user's credentials at this point. Entering this information automatically saves these details to the new profile.

Distributing a Standard Connection Profile to groups of Enterprise Guide Users5

This step can be further improved by pre-defining options for all users so that the 'Location of Update File' is already configured to look for SASUpdate.xml in the correct place. If this is defined, the user simply needs to open Enterprise Guide to get connected to the new environment.

See 'Distributing Options to groups of Enterprise Guide Users' for more information on the topic.