Install OrchestraCMS

The first step is to install the OrchestraCMS managed package in your Salesforce organization.

You can install it to either your production or sandbox organization.

We recommend installing the managed package and any updates to your sandbox environment first.

An initial installation of OrchestraCMS may be done in a partial or development sandbox, but if you are testing an upgrade of OrchestraCMS we recommend you use a full sandbox environment.

If you would like us to install OrchestraCMS, contact us using our Connect With Us form at www.stantive.com.

Before you install the OrchestraCMS managed package, you should log out of any instances of Salesforce that you currently have open. This will prevent the OrchestraCMS managed package from being installed in the wrong Salesforce environment.

To install the OrchestraCMS managed package

1. Click the link that was provided to you by Stantive in order to install the new release of OrchestraCMS into your sandbox environment or into your production environment (if you have already tested the upgrade in your sandbox).
2. Sign in to Salesforce with a System Administrator username and password.
3. Choose Install for Admins Only and click Install.
   
4. When the installation process has completed, you will receive a confirmation email from Salesforce.com. Wait until you receive this email before completing the upgrade in OrchestraCMS.
   

Whether it’s a first installation of OrchestraCMS or an upgrade to Winter 2018, the system administrator will need to add the OrchestraCMS Section to the OrchestraCMS Permission Set, which is generated after the installation. This is a one-time configuration.

On a first installation of OrchestraCMS, the OrchestraCMS Permission Set is automatically available.

On upgrade, you must either log into OrchestraCMS or run the OrchestraCMS Permission Generator.

Add the OrchestraCMS Section to the OrchestraCMS Permission Set

1. In Salesforce Setup, expand Manage Users and click Permission Sets.
2. On the Permission Sets page, locate the OrchestraCMS Permission Set.
3. Click on the OrchestraCMS Permission Set.
4. On the OrchestraCMS Permission Set page, select Object Settings.
   
5. Select OrchestraCMS.
   
6. On the Permission Set page for OrchestraCMS, click Edit.
7. Enable the Visible check box. ✅
   
8. Click Save.

Generate or refresh OrchestraCMS Permissions

An upgrade to OrchestraCMS Winter 2018 will automatically generate permission sets when the system administrator first logs in to OrchestraCMS after install.

Alternately, the Salesforce system administrator can also select the ‘Configure’ link on OrchestraCMS Installed Package detail page in order to generate or refresh any permission sets missing from an OrchestraCMS profile and display status of the OrchestraCMS Permission Generator. This is the recommended action.

1. Under App Setup, click Installed Packages.
2. On the Installed Packages page, you will see your installed package.
3. To generate or refresh OrchestraCMS permissions, click Configure.

Set remote site access

To sync OrchestraCMS licenses with your Salesforce organization, and to enable OrchestraCMS caching and other scheduled jobs, you must configure four remote sites in Salesforce Setup.

The name for each remote site can only contain alphanumeric characters and underscores; names cannot begin or end with an underscore or contain two or more consecutive underscores. Suggested names are provided for the required remote sites.

OrchestraCMS license sync

OrchestraCMS automatically syncs any allocated OrchestraCMS licenses with your Salesforce organization. You can then assign these licenses to users in OrchestraCMS Setup.

Enabling the license sync is a one-time process. You do not need to repeat this process each time you create a new site.

To enable OrchestraCMS license sync

1. In Salesforce Setup, under Security Controls, click Remote Site Settings.
2. Click New Remote Site.
3. Enter a name in the Remote Site Name box. We recommend OrchestraCMSSync.
4. Enter the following URL in the Remote Site URL box: https://stantive.secure.force.com
5. Optionally, enter a description in the Description box.
6. Make sure the Active check box is selected.
7. Click Save or Save & New.

OrchestraCMS Scheduler API

The OrchestraCMS Scheduler is used to schedule jobs, such as sending emails from OrchestraCMS pages and caching pages and content.

To enable the OrchestraCMS Scheduler API

1. In Salesforce Setup, under Security Controls, click Remote Site Settings.
2. Click New Remote Site.
3. Enter a name in the Remote Site Name box. We recommend OrchestraCMSSchedulerAPI.
4. Enter the following URL in the Remote Site URL field:
5. https://salesforceinstance-api.salesforce.com. For example, if your Salesforce instance is “na14”, the URL will be https://na14-api.salesforce.com. Most of the time, you can locate your Salesforce instance in the URL when you are logged into Salesforce. However, you will not see it there if your organization has custom domains enabled. In this case, you can return to this step in Salesforce Setup (under Company Profile > Company Information, see "Instance") after your site is installed to OrchestraCMS. When you have OrchestraCMS open, you can locate your Salesforce instance in OrchestraCMS Setup on the Site Details page or in the URL of the application, and then you can return to this procedure to complete it.
   •  Optionally, enter a description in the Description box.
6. Make sure the Active check box is selected.
7. Click Save or Save & New.

OrchestraCMS SchedulerREST

The OrchestraCMS SchedulerREST is required to execute any OrchestraCMS job.

To enable the OrchestraCMS SchedulerREST

1. In Salesforce Setup, under Security Controls, click Remote Site Settings.
2. Click New Remote Site.
3. Enter a name in the Remote Site Name box. We recommend OrchestraCMSSchedulerREST.
4. Enter the following URL in the Remote Site URL field: https://salesforceinstance.salesforce.com. (In Salesforce Setup under  Company Profile > Company Information, see "Instance".)
5. Optionally, enter a description in the Description box.
6. Make sure the Active check box is selected.
7. Click Save or Save & New.

Remote login site

Remote login site is required for executing OrchestraCMS batch jobs.

To enable remote login site

1. In Salesforce Setup, under Security Controls, click Remote Site Settings.
2. Click New Remote Site.
3. Enter a name in the Remote Site Name field. We recommend OrchestraCMSRemoteLogin.
4. If you are working in a production environment, enter https://login.salesforce.com in the Remote Site URL field; otherwise, enter https://test.salesforce.com if you are in a sandbox environment.
5. Optionally, enter a description in the Description box.
6. Make sure the Active check box is selected.
7. Click Save.

Create and install a Force.com site

Each public site that you create and manage with OrchestraCMS requires a Force.com site. There is no charge to activate Force.com Sites. If you do not have access, contact your Salesforce representative to have Force.com Sites enabled for your organization.

After you create a Force.com site, it must be installed to OrchestraCMS.

Create a Force.com site

Before you create a Force.com site for the first time, you need to register a Force.com domain name. This name does not have to match your branded domain name. Later, you can configure your branded domain name to point to this site through your domain name registrar.

Register a Force.com domain

1. In Salesforce Setup, expand Develop, and then click Sites.
2. Enter the Force.com domain name you want in the http:// box, and then click Check Availability. Repeat until you find a name that is available.
3. Click Sites Terms of Use to read the terms of use, and if you accept them, click to select the check box to confirm.  
4. Click Register My Salesforce Site Domain. This step may take a few minutes to complete.

After you have a Force.com domain registered, you can create a Force.com site. The following procedure must be completed in its entirety for every Force.com site you create that will be managed with OrchestraCMS.

Create a new Force.com site

1. In Salesforce Setup, expand Develop, and then click Sites.
2. In the Sites area, click New. 
3. On the Site Edit page, complete the following fields:
   1. Site Label. A descriptive label that will identify the site in OrchestraCMS. For example, a general corporate website could be labeled “Corporate.” A site dedicated to support could be labeled “Support.”
   2. Site Name. OrchestraCMS calls this name using the Force.com API; the name can’t be changed after the site is created. As a best practice, the site name should be the same as the site label, but this is normally auto-populated from the Site Label.

3. Site Description. A description of the site used by Salesforce administrators to identify it (optional).
4. Site Contact. The Salesforce user that will be sent an email notification if a site visitor experiences any errors. Click the lookup icon beside the field to select the Salesforce user.  
5. Default Web Address. The first portion of the web address is already populated, and if this is your first site, you do not need to enter a second part to the address. For subsequent sites, you are required to add a second part to the URL to distinguish it from the first site.
6. Active. Select this option to activate the site. This step can be completed later, but under most circumstances, the site is activated when it is created.
7. Active Site Home Page. Click the lookup icon beside the field, and in the Lookup dialog, search for “main”. In the search results, click to select the Visualforce page with the name and label Main (namespace prefix “cms”).
8. Inactive Site Home Page. Click the lookup icon beside the field, and in the Lookup dialog, search for “ErrorMaintenance”. In the search results, click to select the Visualforce page with the name and label ErrorMaintenance (namespace prefix “cms”).
9. Site Template. Clear the contents of this field.  
10. Site Robots.txt. This file tells web crawlers and robots which pages of your site should be indexed. Click the lookup icon beside the field, and in the Lookup dialog, search for “OrchestraCMSRobots”. In the search results, click to select OrchestraCMSRobots.
11. Site Favorite Icon. The icon that appears in the browser’s address bar or section when a user visits your site. This file must be uploaded as a static resource to Salesforce before you can select it from this screen. To do this, go to Setup > Develop > Static Resources and upload a new file. The file must have an .ico extension. Once the file is uploaded as a static resource, you can click the lookup icon beside the Site Favorite Icon field, and in the Lookup dialog, search for and select your icon file.  
12. Analytics Tracking Code. If you are using Google Analytics, this field is populated with the UA number provided by Google Analytics. For Google Analytics to work, the appropriate code must also be added to the page templates you are using to build your site.
13. URL Rewriter Class. This field is populated with the OrchestraCMS Rewriter Apex class, which generates clean URLs for your site. Click the lookup icon beside the field, and in the Lookup dialog, search for “OrchestraCMSRewriter”. In the search results, click to select OrchestraCMSRewriter. Without the OrchestraCMS Rewriter enabled, the URLs for pages include cms__Main?name= immediately following the domain name, such as in the following example: www.example.com/cms__Main?=name=page-URL When the OrchestraCMS Rewriter is enabled, this portion of the URL is eliminated, such as in the following example: www.example.com/page-URL
14. Clickjack Protection Level. The appropriate setting for this field depends on whether your site will display content using iframe elements. There are three options:
15. Allow framing by any page (no protection). Use this option if your site will display content from external sources (i.e., content not stored in Salesforce) in iframe elements.
16. Allow framing by the same origin only (Recommended). Use this option if your site will display content from Salesforce in iframe elements (e.g., the Salesforce Dashboard content type in OrchestraCMS Extensions uses iframe elements to display Salesforce Dashboards).
17. Don’t allow framing by any page (most protection). Use this option if you do not intend to use iframe elements to display content. You can change this option at any time if you need to.

4. Click Save.
5. On the Site Details page, scroll down to Error Pages, and then click Page Assignment.
6. For each of the error page fields listed, click the lookup icon next to the field, and in the Lookup dialog, search for “Error”. Click to select the name of the error page that matches the field you selected. For example, the Authorization Required Page field will be set to the ErrorAuthorizationRequired page.
   
7.  Click Save.

Site Guest User permissions

On installation or upgrade, OrchestraCMS automatically generates ocms_SiteViewer permissions, providing access to objects, fields and Visualforce pages for guest users who are listed as Active.

If the guest user is not active but is activated later, and the administrator clicks on OrchestraCMS Site Details (under Setup), a message will appear to say the permission set doesn’t exist, or the guest user doesn’t have the required permission.

In that case, the “Validate Permissions” option should be used.

Validate permissions for a Site Guest User

1. In OrchestraCMS Setup, under Site, click Details.
2. Click Edit.
3. Click Validate Permissions.

The SiteViewer permission set is shared among all guests in the organization.

If you want to create additional Visualforce pages for your public website users, you will have to go to the Available Visualforce Pages list in the Salesforce guest profile, select your additional pages, click Add, and then Save.

If your public website users will be submitting forms, do the following:

• Make modifications to permissions for standard or custom objects that will be used in forms. For example, if you build a web-to-lead form using fields from the Leads object, you must grant Create access to that object under Standard Object Permissions. If you want your forms to be able to update existing records, you also need to grant Edit access to the appropriate objects.

Install your Force.com site to OrchestraCMS  

The next step is to install your Force.com site to OrchestraCMS. The following procedure must be completed every time you create a new site.

To install your Force.com site to OrchestraCMS

1. From the Force.com app menu, select OrchestraCMS.
   
2. Do one of the following:
   • If this is your first site, you will see the OrchestraCMS welcome screen. Click set up new site wizard.
   • For each site, you will be prompted to set a default language.
   • You can change the default language after it is set.
     
3. If this is not your first site, select Create New Site from the Current Site menu.
   
4. In Salesforce, click Salesforce Site.
   
5. Select your site from the Site Label list. (Clicking Salesforce Site will include the Site Guest User.)
6. In the Default Language box, enter the name of your site’s default language, and choose that language from the picklist. Optionally, you can also add a description for the language.
7. Click Install, and wait for a message that confirms the installation is complete.

Your site is now installed in OrchestraCMS. If your site’s Guest User is active, the OrchestraCMS SiteViewer permission set will be assigned.

Some configuration is still required. You can now open OrchestraCMS from the Force.com app menu.