SQL Azure Connection Strings

Note: When using the deployment wizard in the administration tool to deploy a worker role-based deployment, these strings are auto configured. This section still contains valuable information for connection strings if you build your own deployment packages, or use virtual machine deployments.
  1. To configure SQL Azure connections for CICS systems deployed as worker roles, open the see.azure.config file in an editor.
    Tip: You may already have this file open in an editor if you are following the instructions for Configuring the CICS System.

Configuring SQL Azure Connections for a Local Machine or Virtual Machine Role

  1. Open machine.config in an editor as Administrator. The machine.config file is in %windir%\Microsoft.NET\Framework\v4.0.30319\Config for Windows 32-bit, and in %windir%\Microsoft.NET\Framework64\v4.0.30319\Config for Windows 64-bit.
  2. If the MicroFocus.SEE section is not defined in the file, add the following <section> element just before the </configSections> closing tag.
    <!-- Added for Micro Focus SEE for .NET -->
    <section name="MicroFocus.SEE" 
                   type="MicroFocus.SEE.Utils.GlobalConfigurationSection,
                   MicroFocus.SEE.Utils,Version=4.0.0.0,
                   Culture=neutral,PublicKeyToken=0412c5e0b2aaa8f0" />
    
  3. At the end of the file, just before the closing tag, add the MicroFocus.SEE section.
    <!-- Added for Micro Focus SEE for .NET -->
    <MicroFocus.SEE>
    </MicroFocus.SEE>
    

Adding Connection String Entries

  1. Define a connection string for each SQL Azure database accessed by the CICS system. Add each connection string as a child element of the MicroFocus.SEE element. For example:
    <MicroFocus.SEE>
      <add key="SQL.ConnectionString.[servername]/master" 
           value="Server=tcp:[servername].database.windows.net;
                  Database=master;
                  User ID=[username]@[servername];
                  Password=[userpassword];
                  Trusted_Connection=False;
                  Encrypt=True;"
      />
      <add key="SQL.ConnectionString.[servername]/MicroFocus$SEE$CrossRegion" 
           value="Server=tcp:[servername].database.windows.net;
                  Database=MicroFocus$SEE$CrossRegion;
                  User ID=[username]@[servername];
                  Password=[userpassword];
                  Trusted_Connection=False;
                  Encrypt=True;"
      />  
      <add key="SQL.ConnectionString.[servername]/MicroFocus$SEE$Region$ESDEMO" 
           value="Server=tcp:[servername].database.windows.net;
                  Database=MicroFocus$SEE$Region$ESDEMO;
                  User ID=[username]@[servername];
                  Password=[userpassword];
                  Trusted_Connection=False;
                  Encrypt=True;"/>
      <add key="SQL.ConnectionString.[servername]/MicroFocus$SEE$Region$TESTDB" 
           value="Server=tcp:[servername].database.windows.net;
                  Database=MicroFocus$SEE$Region$TESTDB;
                  User ID=[username]@[servername];
                  Password=[userpassword];
                  Trusted_Connection=False;
                  Encrypt=True;"/>     
      <add key="SQL.ConnectionString.[servername]/MicroFocus$SEE$Files$VSAM" 
           value="Server=tcp:[servername].database.windows.net;
                  Database=MicroFocus$SEE$Files$VSAM;
                  User ID=[username]@[servername];
                  Password=[userpassword];
                  Trusted_Connection=False;
                  Encrypt=True;"/>
    </MicroFocus.SEE>
    
  2. Define as a minimum a connection string for the master database, cross-region database, and one CICS region database. Enterprise Server for .NET implicitly creates the cross-region and CICS region databases, so connection strings are required even though they may not currently exist. In the example above, connection strings have been specified for the following:
    • Master database. The master database always has the name master
    • Cross-region database. The cross-region database always has the name MicroFocus$SEE$CrossRegion
    • ESDEMO and TESTDB region databases. A region database name is always of the form MicroFocus$SEE$Region$region name
    • Default VSAM file datastore. A VSAM file datastore database name is always of the form MicroFocus$SEE$Files$VSAM datastore name
  3. Define a connection string for each VSAM file datastore hosted in SQL Azure. The following is a connection string for the MyVsamFiles datastore:
    <add key="SQL.ConnectionString.[servername]/MicroFocus$SEE$Files$MyVsamFiles" 
         value="Server=tcp:[servername].database.windows.net;
         Database=MicroFocus$SEE$Files$MyVsamFiles;
         User ID=[username]@[servername];
         Password=[userpassword];
         Trusted_Connection=False;
         Encrypt=True;"
    />