Validate your S4S License is working

This post looks at how to make sure your S4S license is working before deploying it to production.

About the S4S License File

An S4S license is an XML file issued by FuseIT that looks similar to the example below.

<fuseIT license="S4S">
 <!-- The name of this file must be called "S4SLicense.xml". It should be saved next to the Sitecore license file. i.e. "license.xml". To find the correct location search web.config for the string "sc.variable" and read the location from the dataFolder item. The default folder is normally the "data" folder. -->
 <license>
 <!-- The FuseIT Customer AccountId. It will start with "001" and be 15 characters long -->
  <accountId>0014000009eyXwEAAU</accountId>
  <!-- The FuseIT issued LicenseId (Opportunity). It will start with "006" and be 18 characters long -->
  <licenseId>0068000000h2tC4111</licenseId>
  <!-- License Domain Keys provided by FuseIT for the specific domain - provided separately for each domain. -->
  <licenseDomainKeys>
   <key type="org" expiryDate="" id="00D7F0000000tAo">JKhLDgF0kToTh/AFs2wH22gRm24=</key>
   <key type="sandbox" expiryDate="" id="Sandbox">1J8X27VS/9sFQWr1FC5PpQo0TYM=</key>
   <key type="sandbox" expiryDate="" id="Sandbox">MKEF3DewjaXla7kZSSde9HYuUys=</key>
  </licenseDomainKeys>
 </license>
</fuseIT>

Please note the following:

• Locate the file beside the Sitecore license (as determined by the datafolder setting in config)
• Separate keys are required for each Salesforce Production org
• Two Sandbox keys are issued. These will work with all Sandboxes
• No key is required for working with Developer Editions
• A license type can be "org" (licensed against a Salesforce instance) or "domain" (licensed against an IIS binding )

Validating the License

It is important to check the license file will "take" before going live in production:

1. Install the S4S license in a non-production Sitecore website e.g. TEST or UAT
2. Change the S4S connection string to point to a Salesforce production org
3. Execute a transaction between Sitecore and Salesforce e.g. Submit a Sitecore Form with an S4S Save Action
4. Determine if the transaction was successful
5. Revert the S4S connection string changes

If the test fails, execute the following process:

1. In config, set Sitecore logging to DEBUG mode
2. Execute a transaction between Sitecore and Salesforce
3. Review the log file to determine the failure reason
4. Send the relevant log file extracts to FuseIT
5. Revert the config changes

More information on licensing is here:

• Where is the S4S license file located?
• After licensing, S4S still has licensing errors!
• What causes the S4S license to expire?
• Difference between S4S Basic and Other License Options
• Is my licensing impacted by a Sitecore upgrade?

For more information please contact FuseIT at S4S@fuseit.com