Bridgeline Digital Logo
Menu

Set up and enable media libraries

OrchestraCMS media libraries are used to manage your digital media: the images, videos, PDFs, and other media files that you want to include on your website, portal, or intranet.

OrchestraCMS media libraries can store files using one of the following three platforms:  

  • Salesforce. By default, a single media library is automatically available for each site in OrchestraCMS, and files added to this media library are stored in the Library Content custom object in Salesforce.
    • The OrchestraCMS Media Library supports Salesforce’s 25MB file size limit.
  • Amazon Web Services. Amazon Simple Storage Service (Amazon S3) and Amazon CloudFront can integrate with OrchestraCMS. Linking an Amazon Web Services account with OrchestraCMS requires the OrchestraCMS AmazonS3 Library feature license.
  • Google Cloud Storage. Google Cloud Storage can integrate with OrchestraCMS. Linking a Google Cloud Storage account with OrchestraCMS requires the OrchestraCMS Google Cloud Storage Library feature license.

If you need to upload individual files larger than 25MB or have large storage requirements, we recommend that you use Amazon Web Services or Google Cloud Storage to meet your requirements.

 

The OrchestraCMS Private Sharing feature can’t be used to protect files in media libraries.

External media repositories

OrchestraCMS can integrate with Amazon Web Services and Google Cloud Storage to store and access media files.

If you need to upload individual files larger than 25MB or have large storage requirements, we recommend that you use one of these services to meet your requirements.

  • The OrchestraCMS AmazonS3 Library or OrchestraCMS Google Cloud Storage Library feature license is required to link to one of these external repositories.

Amazon S3 and Amazon CloudFront overview

Amazon S3 and Amazon CloudFront can integrate with OrchestraCMS:

  • Amazon S3. A scalable file storage repository that can be accessed from the web. For more information, visit http://aws.amazon.com/s3.
  • Amazon CloudFront. A content delivery web service that can be used in conjunction with Amazon S3 to distribute media files to end-users with low latency and high data transfer speeds. For more information, visit http://aws.amazon.com/cloudfront.

Before you can add a media library to OrchestraCMS that is hosted by Amazon, you need to have the following:

  • An Amazon Web Services account. Go to http://aws.amazon.com to sign up for an account.
  • An OrchestraCMS Amazon S3 Library feature license. Contact your sales representative to inquire, or visit our website at www.stantive.com.  

Adding a media library hosted by Amazon requires configuration in Amazon Web Services, Salesforce, and OrchestraCMS. These steps are different depending on whether you are using Amazon S3 on its own or in conjunction with Amazon CloudFront.

Google Cloud Storage overview

Google Cloud Storage, a scalable object storage service build on the same infrastructure as Google search, can integrate with OrchestraCMS.

Adding a media library hosted by Google requires configuration in Google Cloud Storage, Salesforce, and OrchestraCMS. Set up an Amazon S3 media library

Create an Amazon S3 bucket

The first step in setting up a media library using Amazon S3 is to create an Amazon S3 bucket that will be used to store OrchestraCMS media library files.

To create a new bucket

  1. Log in to your Amazon Web Services account and go to the S3 Management Console.
  2. Click Create Bucket.
  3. In the Create a Bucket dialog, do the following:
    • Enter a DNS-compliant name in the Bucket Name box, using the following rules:
      • Bucket names must be at least 3 and no more than 63 characters long.
      • Bucket names must be a series of one or more labels. Adjacent labels are separated by a single period. Bucket names can contain lowercase letters, numbers, and dashes. Each label must start and end with a lowercase letter or a number.
      • Bucket names must not be formatted as an IP address.
    • Choose a region for the bucket from the Region list; this decision might be based on optimizing for latency, minimizing costs, or addressing regulatory requirements.
      • For the purposes of OrchestraCMS, you can choose any region.
  4. Click Create.
  5. In the bucket properties panel, click to expand Permissions.
  6. Click Add more permissions.
  7. From the Grantee list, select Everyone, and click to select the List option; this ensures that your live site can access the files stored in the bucket via Amazon CloudFront.
  8. Click Save.

Enable remote site access in Salesforce

To be able to connect to your Amazon S3 bucket, you have to set up remote site access in your Salesforce organization for the endpoint URL of the Amazon S3 region that your bucket was created in.

There are two ways that Amazon S3 needs to be accessed:

  • From your live site. In this instance, the endpoint URL of the Amazon S3 region can be either unsecured (http) or secured (https). If your live site is a portal, community, or intranet, it should be a secured URL. For a public site, it could be either secured or unsecured.
  • From within OrchestraCMS. In this instance, the endpoint URL of the Amazon S3 region should be secured (https). If it isn’t, OrchestraCMS users might find that their browsers block them from accessing unsecured content from within a secured site.  

If you choose to use secure URLs for both of the above links, the links will be identical, and only one remote site needs to be added to your Salesforce organization. If you decide to use an unsecured URL on your live site and a secured URL for accessing the bucket from within OrchestraCMS, then you need to add both URLs as remote sites in your Salesforce organization.

The required endpoint URL depends on the Amazon S3 region that your bucket was created in. For example, if the bucket was created in the South America (Sao Paulo) region, you can use https://s3-sa-east-1.amazonaws.com or http://s3-sa-east-1.amazonaws.com. If the bucket was created in the US Standard region, you can use https://s3.amazonaws.com or http://s3.amazonaws.com.

For a complete list of Amazon S3 region endpoints, see the following URL:

http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region

To enable remote site access in Salesforce

  1. In Salesforce Setup, under Security Controls, click Remote Site Settings.
  2. On the All Remote Sites page, click New Remote Site.
  3. On the Remote Site Edit page, do the following:
    • In the Remote Site Name field, enter a descriptive name. The name must begin with a letter and contain only alphanumeric characters and underscores.
    • In the Remote Site URL field, enter the endpoint URL of the Amazon region your bucket was created in.
    • Verify that the Active check box is selected.
  4. Click Save.
  5. If you are using an unsecured URL for the Live Site Bucket Link and a secured URL for the Secure Bucket Link in OrchestraCMS, repeat steps 1–4 to enter the second URL as another remote site.

If you choose to only use unsecured URLs to connect to Amazon S3, you may find that browsers block OrchestraCMS users and site visitors (if your site is secure) from accessing content stored in Amazon S3. In this case, there are ways to disable mixed content blocking in browsers—each user will have to do this in their own browser.

Disable mixed content blocking in Firefox

  • A shield icon appears on the left side of the address bar when the browser is blocking mixed content. Click on the shield.
  • Click the More Actions arrow.
  • Select Disable Protection on this page.

Disable mixed content blocking in Chrome

  1. On the right side of the address bar, click on the shield icon that appears when the browser is blocking mixed content.
  2. Select Load Unsafe Script.

Disable mixed content blocking in Internet Explorer

  • A box with the message “Only secure content is displayed” appears at the bottom of the page when the browser is blocking mixed content; click Show all content.

Create an Amazon S3 media library in OrchestraCMS

After your bucket has been created in Amazon S3 and remote site access has been configured in your Salesforce organization, you can add your Amazon S3 bucket. There will be a folder created for OrchestraCMS. Create a second folder. In that folder you can place the files from Amazon that you want to sync with OrchestraCMS.

When files are loaded into the OrchestraCMS library and synced, they are placed in the OrchestraCMS folder. If you place folders in a second folder and then sync them, those files will also appear in the OrchestraCMS library. However, if you place files from Amazon directly into the OrchestraCMS folder, they will not come back to the OrchestraCMS library.

To create an Amazon S3 media library in OrchestraCMS

  1. In OrchestraCMS Setup, click Manage Libraries.
  2. Click Add Library. 
  3. Select one of the following repository types from the Repository list, and then click Next:
    • Amazon S3. Uses static URLs for media files stored in Amazon S3.
    • Amazon S3 – Secure. Uses query string authentication to generate pre-signed, temporary URLs with time expiration for media files stored in Amazon S3.
  4. Complete the following fields to meet your requirements:                                        
    • Name (required). This is the name users will see throughout the interface to identify the library.
    • Description. A description of the library.
    • Sharing. Choose whether you want the library to be accessible by all sites in your Salesforce organization or only the current one. Once sharing is enabled, it can’t be disabled.
    • Live Site Bucket Link (required). The link used to generate URLs for media files on your live site. This is a combination of the endpoint URL of the Amazon S3 region your bucket was created in and the bucket name. For example, if you created the bucket ourmedialibrary in the Amazon S3 Asia Pacific (Sydney) region, the secure link to the bucket would be https://s3-ap-southeast-2.amazonaws.com/ourmedialibrary. If the bucket was created in the US Standard region, you could use https://s3.amazonaws.com/ourmedialibrary. The Live Site Bucket Link should use https if the site is a portal, community, or intranet; it can be https or http if it is an unsecured public site.
    • Secure Bucket Link (required). The link used to connect to Amazon S3 to manage files from within OrchestraCMS. This link follows the same format as the Live Site Bucket Link, but it should always use https.
    • Access Key ID (required). Your Amazon Web Services Access Key ID. This can be accessed from the Security Credentials page of your Amazon Web Services account.
    • Secret Access Key (required). Your Amazon Web Services Secret Access Key. Until April 21, 2014, this can be accessed from the legacy Security Credentials page of your Amazon Web Services account. After that date, the secret access key will not be accessible from the Amazon Web Services interface. If you lose your secret access key, you must generate a new access key.
    • Allow Uploads. This option allows users to upload files from the OrchestraCMS interface to Amazon Web Services. We recommend that all uploads are initiated from OrchestraCMS rather than Amazon Web Services. This is because uploads initiated from OrchestraCMS automatically sync with Amazon Web Services, whereas uploads initiated from Amazon Web Services must be manually synced with OrchestraCMS.
  5. Click Test to verify that OrchestraCMS can connect to the Amazon bucket.
  6. Click Save.

Set up an Amazon CloudFront media library

This section provides instructions for setting up an OrchestraCMS media library using Amazon S3 in conjunction with Amazon CloudFront.

Create an Amazon S3 bucket

The process for setting up an Amazon S3 bucket is the same whether you are using Amazon S3 on its own or in conjunction with Amazon CloudFront.

Set up an Amazon CloudFront distribution

To use Amazon CloudFront in conjunction with Amazon S3, you need to set up a CloudFront distribution for your Amazon S3 bucket.

To set up an Amazon CloudFront distribution

Log in to your Amazon Web Services account and go to the CloudFront Management Console.

  1. Click Create Distribution. 
  2. On Step 1: Select delivery method, select one of the following options, and then click Continue:
    • Web. Used for most scenarios.  
    • RTMP. Used specifically to speed up distribution of your streaming media files using Adobe Flash Media Server’s RTMP protocol.
  3. On Step 2: Create distribution, click in the Origin Domain Name box, and select the domain of the Amazon S3 bucket you created.
  4. Click Create Distribution.

Enable remote site access in Salesforce

To be able to connect to the files stored in Amazon S3 and distributed with Amazon CloudFront, you have to set up remote site access in your Salesforce organization.

There are two ways that Amazon needs to be accessed:

  • From your live site. The live site will access files stored in your Amazon S3 bucket through Amazon CloudFront. This URL uses the Amazon CloudFront domain name that was created for the Amazon S3 bucket when the CloudFront distribution was configured. The URL is found in the CloudFront Management Console; for example, https://d1jgip5yxyxyxy.cloudfront.net. If your site is a portal, community, or intranet, the URL should use https; a public site can use either https or http (depending on your CloudFront distribution settings).
  • From within OrchestraCMS. When OrchestraCMS users want to work with media files in your Amazon S3 bucket, they can connect to the bucket directly and securely. This URL uses the endpoint URL of the Amazon S3 region that your bucket was created in. For example, if the bucket was created in the South America (Sao Paulo) region, the URL is https://s3-sa-east-1.amazonaws.com. If the bucket was created in the US Standard region, you can use https://s3.amazonaws.com. This URL should always use https; otherwise, OrchestraCMS users might find that their browser blocks them from accessing unsecured content from within a secured site.

For a complete list of Amazon S3 region endpoints, see the following URL:

http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region

To enable remote site access in Salesforce

  1. In Salesforce Setup, under Security Controls, click Remote Site Settings.
  2. On the All Remote Sites page, click New Remote Site.
  3. On the Remote Site Edit page, do the following:
    • In the Remote Site Name field, enter a descriptive name. The name must begin with a letter and contain only alphanumeric characters and underscores.
    • In the Remote Site URL field, enter the Amazon CloudFront URL for the Amazon S3 bucket.
  4. Verify that the Active check box is selected.
  5. Click Save.
  6. Repeat steps 1–4 using the Amazon S3 region endpoint URL for the Remote Site URL field.

If you choose to only use unsecured URLs to connect to Amazon, you may find that browsers block OrchestraCMS users and site visitors (if your site is secure) from accessing content stored in Amazon S3. In this case, there are ways to disable mixed content blocking in browsers—each user will have to do this in their own browser.

Disable mixed content blocking in Firefox

  1. A shield icon appears on the left side of the address bar when the browser is blocking mixed content; click on the shield.
  2. Click the More Actions arrow.
  3. Select Disable Protection on this page.
  4. To disable mixed content blocking in Chrome
  5. A shield icon appears on the right side of the address bar when the browser is blocking mixed content; click on the shield.
  6. Select Load Unsafe Script.

Disable mixed content blocking in Internet Explorer

A box with the message “Only secure content is displayed” appears at the bottom of the page when the browser is blocking mixed content; click Show all content.

Create an Amazon CloudFront library in OrchestraCMS

After your bucket has been created in Amazon S3, a CloudFront distribution has been created, and remote site access has been configured in your Salesforce organization, you can create an Amazon CloudFront media library in OrchestraCMS.  

To create an Amazon CloudFront media library in OrchestraCMS

  1. In OrchestraCMS Setup, click Manage Libraries.
  2. Click Add Library.
  3. Select one of the following repository types from the Repository list, and then click Next:
    • Amazon CloudFront. Uses static URLs for media files.
    • Amazon CloudFront – Secure. Uses CloudFront key pairs to create signed URLs; key pairs consist of a public and private key, where the private key is used to create a digital signature, and Amazon Web Services uses the corresponding public key to validate the signature.
  4. Complete the following fields to meet your requirements:
    • Name (required). This is the name users will see throughout the interface to identify the library.
    • Description. A description of the library.
    • Sharing. Choose whether you want the library to be accessible by all sites in your Salesforce organization or only the current one. Once sharing is enabled, it can’t be disabled.
    • Live Site Bucket Link (required). The link used to generate URLs for media files on your live site. This URL uses the Amazon CloudFront domain name that was created for the Amazon S3 bucket when the CloudFront distribution was configured. The URL is found in the CloudFront Management Console; for example, https://d1jgip5yxyxyxy.cloudfront.net. If your site is a portal, community, or intranet, the URL should use https; a public site can use either https or http (depending on your CloudFront distribution settings).
    • Secure Bucket Link (required). The link used to connect to Amazon S3 to manage files from within OrchestraCMS. This is a combination of the endpoint URL of the Amazon S3 region your bucket was created in and the bucket name. For example, if you created the bucket ourmedialibrary in the Amazon S3 Asia Pacific (Sydney) region, the secure link to the bucket would be https://s3-ap-southeast-2.amazonaws.com/ourmedialibrary. If the bucket was created in the US Standard region, you could use https://s3.amazonaws.com/ourmedialibrary This URL should always use https; otherwise, OrchestraCMS users might find that their browser blocks them from accessing unsecured content from within a secured site.
    • Access Key ID (required). Your Amazon Web Services Access Key ID. This can be accessed from the Security Credentials page of your Amazon Web Services account.
    • Secret Access Key (required). Your Amazon Web Services Secret Access Key. This key is only available at the time that the access key is created. If you lose your secret access key, you must generate a new access key.
    • CloudFront Access Key ID (required for the secure option only). The public portion (Access Key ID) of your CloudFront Key Pair. This can be accessed from the Security Credentials page of your Amazon Web Services account.
    • CloudFront Secret Access Key (required for the secure option only). The private portion of your CloudFront Key Pair. This is saved as a .pem file when the key pair is first created; if you have lost the private portion of the key pair, a new key pair needs to be created. To retrieve the private key from the .pem file, run the following command on the file, and use the output between BEGIN PRIVATE KEY and END PRIVATE KEY as the input for the CloudFront Secret Access Key field in OrchestraCMS:

openssl pkcs8 –topk8 –nocrypt –in file_name.pem –outform PEM

  • Allow Uploads. This option allows users to upload files from the OrchestraCMS interface to Amazon Web Services. We recommend that all uploads are initiated from OrchestraCMS rather than Amazon Web Services. This is because uploads initiated from OrchestraCMS automatically sync with Amazon Web Services, whereas uploads initiated from Amazon Web Services must be manually synced with OrchestraCMS.
  • Click Test to verify that OrchestraCMS can connect to the Amazon bucket; this does not test the connection to CloudFront—you can upload an image to the library in OrchestraCMS and preview the image on a page to ensure the connection to CloudFront is working.
  • Click Save.

Set up a Google Cloud Storage media library

To set up an OrchestraCMS media library using Google Cloud Storage, you will need to have the following:

  • A Google account
  • A project created in the Google Developers Console
  • Billing set up for the project

For more information on signing up for Google Cloud Storage, see the following URL:

https://developers.google.com/storage/docs/signup

Create a Google Cloud Storage bucket

A Google Cloud Storage bucket is the place where files are stored. When you create an OrchestraCMS library to integrate with Google Cloud Storage, the bucket is associated with the library to allow you to access and upload files from OrchestraCMS.

There are several restrictions on the names you can give Google Cloud Storage buckets, including the following:

  • Bucket names must be unique across the entire Google Cloud Storage namespace.
  • Bucket names must contain only lowercase letters, numbers, dashes, underscores, and dots (periods); names containing dots require validation as a domain name that is owned by your organization.
  • Bucket names must start and end with a number or letter.
  • Bucket names must contain 3–63 characters; names containing dots can contain up to 222 characters, but each dot-separated component must be 63 characters or less.
  • Bucket names can’t be in the form of an IP address.
  • Bucket names can’t begin with the “goog” prefix.

For a complete list of restrictions, see the following URL:

https://developers.google.com/storage/docs/bucketnaming

To create a Google Cloud Storage bucket

  1. In the Google Developers Console, select the project you want to use for OrchestraCMS media storage.
  2. Click to expand Storage and then Cloud Storage.
  3. Click Storage Browser.
  4. Click New Bucket.
  5. In the New Bucket dialog, enter a name that complies with the restrictions noted earlier in the section and click Create.

Enable remote site access in Salesforce

To be able to connect to your Google Cloud Storage bucket, you have to set up remote site access in your Salesforce organization to Google Cloud Storage. The URL to set up remote site access to Google Cloud Storage is storage.googleapis.com.

There are two ways that Google Cloud Storage needs to be accessed:

  • From your live site. In this instance, the remote site URL can be either unsecured (http) or secured (https). If your live site is a portal, community, or intranet, it should be a secured URL. For a public site, it could be either secured or unsecured.
  • From within OrchestraCMS. In this instance, the remote site URL should be secured (https). If it isn’t, OrchestraCMS users might find that their browsers block them from accessing unsecured content from within a secured site.

If you choose to use secure URLs for both of the above links, the links will be identical, and only one remote site needs to be added to your Salesforce organization. If you decide to use an unsecured URL on your live site and a secured URL for accessing the bucket from within OrchestraCMS, then you need to add both URLs as remote sites in your Salesforce organization.

To enable remote site access in Salesforce

  1. In Salesforce Setup, under Security Controls, click Remote Site Settings.
  2. On the All Remote Sites page, click New Remote Site.
  3. On the Remote Site Edit page, do the following:
    • In the Remote Site Name field, enter a descriptive name. The name must begin with a letter and contain only alphanumeric characters and underscores.
    • In the Remote Site URL field, enter one of the following URLs depending on whether you want secured or unsecured access:
    • Verify that the Active check box is selected.
  4. Click Save.
  5. If you are using an unsecured URL for the Live Site Bucket Link and a secured URL for the Secure Bucket Link in OrchestraCMS, repeat steps 1–4 to enter the second URL as another remote site.

If you choose to only use an unsecured URL, and your site is a secure site, you may find that browsers block OrchestraCMS users and site visitors from accessing content stored in Google Cloud Storage. In this case, there are ways to disable mixed content blocking in browsers—each user will have to do this in their own browser.

Disable mixed content blocking in Firefox

  1. A shield icon appears on the left side of the address bar when the browser is blocking mixed content; click on the shield.
  2. Click the More Actions arrow.
  3. Select Disable Protection on this page.

Disable mixed content blocking in Chrome

  1. On the right side of the address bar, click on the shield icon that appears when the browser is blocking mixed content.
  2. Select Load Unsafe Script.

Disable mixed content blocking in Internet Explorer

  • A box with the message “Only secure content is displayed” appears at the bottom of the page when the browser is blocking mixed content; click Show all content.

Create a Google Cloud Storage media library in OrchestraCMS

After your bucket has been created in the Google Developers Console and remote site access has been configured in your Salesforce organization, you can add your bucket as an OrchestraCMS media library.

To create an Google Cloud Storage media library in OrchestraCMS

  1. In OrchestraCMS Setup, click Manage Libraries.
  2. Click Add Library.
  3. Select one of the following repository types from the Repository list, and then click Next:
    • Google Cloud Storage. Uses static URLs for media files stored in Google Cloud Storage.
    • Google Cloud Storage - Secure. Uses query string authentication to generate signed, temporary URLs for media files stored in Google Cloud Storage.
  4. Complete the following fields to meet your requirements:
    • Name (required). This is the name users will see throughout the interface to identify the library.
    • Description. A description of the library.
    • Sharing. Choose whether you want the library to be accessible by all sites in your Salesforce organization or only the current one. Once sharing is enabled, it can’t be disabled.
    • Live Site Bucket Link (required). The link used to generate URLs for media files on your live site. This is the endpoint URL for the bucket you created in the format

http://storage.googleapis.com/bucketname or https://storage.googleapis.com/bucketname. The Live Site Bucket Link should use https if the site is a portal, community, or intranet; it can be https or http if it is an unsecured public site.

  • Secure Bucket Link (required). The link used to connect to your Google Cloud Storage bucket to manage files from within OrchestraCMS. This link follows the same format as the Live Site Bucket Link, but it should always use https (i.e., https://storage.googleapis.com/bucketname).
  • Access Key ID (required). Your Access Key for your Google Cloud Storage project. To access this key from the Google Developers Console, expand Storage and then Cloud Storage, and click Project dashboard. On the project dashboard page, expand Google Cloud Storage, and then click Interoperable Access. Copy the key listed under the Access Key column.
  • Secret Access Key (required). Your Secret Access key for your Google Cloud Storage project. To access this key from the Google Developers Console, expand Storage and then Cloud Storage, and click Project dashboard. On the project dashboard page, expand Google Cloud Storage, and then click Interoperable Access. Under the Secret column, click Show, and copy the key that is displayed.
  • Allow Uploads. This option allows users to upload files from the OrchestraCMS interface to Google Cloud Storage. We recommend that all uploads are initiated from OrchestraCMS rather than the Google Developers Console. This is because uploads initiated from OrchestraCMS automatically sync with Google Cloud Storage, whereas uploads initiated from the Google Developers Console must be manually synced with OrchestraCMS.
  1. Click Test to verify that OrchestraCMS can connect to the Google Cloud Storage bucket.
  2. Click Save.

Manually synchronize an external library

We recommend that you always upload media files to a library through the OrchestraCMS interface, because this method automatically syncs files with your external repositories.

If you upload media files from external interfaces (e.g., Amazon Web Services or Google Cloud Storage), you have to perform a manual synchronization before users can access those files from OrchestraCMS.

To manually synchronize your external repository with OrchestraCMS

  1. In OrchestraCMS Setup, under Utilities, click Manage Libraries.
  2. Next to the library name, click Synchronize Now.

After you initiate the synchronization, a message displays confirming that an Apex job has been set up. You can monitor the progress of the synchronization from the Apex Jobs page in Salesforce Setup.  

Enable, disable, or remove a media library

When a media library is added, it is automatically enabled. You can disable the media library at any time. Disabling a library means that the settings for the library remain in OrchestraCMS, but users can’t access the library. You can’t disable the original media library that is automatically created when the site is installed to OrchestraCMS.

Disable a media library

  1. In OrchestraCMS Setup, under Utilities, click Manage Libraries.
  2. Next to the media library name, toggle the Enabled/Disabled control. (The status switches between Enabled and Disabled.)

If a library is disabled, it can be enabled to restore user access to the library.

Enable a media library

  1. In OrchestraCMS Setup, under Utilities, click Manage Libraries.
  2. Next to the media library name, click Disabled. The status switches to Enabled.

Libraries other than the original library can be removed; however, you should consider disabling the library instead of removing it if there is a chance you might add it again in the future. Removing a library means that users can’t access it and an administrator must add the library again to restore access.

Remove a library

  1. In OrchestraCMS Setup, under Utilities, click Manage Libraries.
  2. Next to the media library name, click Remove.
  3. In the verification dialog, click OK.

Edit a media library

Most media library properties can be edited after a library is created, other than the following:

  • For Amazon libraries, you can’t modify the Live Site Bucket Link or Secure Bucket Link fields after the library is created; if these need to be changed, you can remove the existing library and create a new one.
  • If the option to share a library with other sites in your Salesforce organization is enabled, this option can’t be subsequently disabled.  

Change media library records of inactive users

Being able to create a permission set allowing users to edit inactive user records is required for any OrchestraCMS users with an OrchestraCMS System Administrator or OrchestraCMS Site Administrator profile.

Important

We strongly recommend that you create a permission set specifically for this purpose before you attempt to convert a media library, and that you do not apply it to auto-generated OrchestraCMS permission sets.

Create permissions to edit inactive user records

  1. In Salesforce App setup, under Customize, select User Interface.
  2. In User Interface, under Setup, select the check box to Enable “Set Audit Fields upon Record Creation” and “Update Records with Inactive Owners” User Permissions.
  3. Click Save.
  4. In Salesforce Administration Setup, under Manage Users, select Permission Sets. On the Permission Sets page, click New.
  5. Create a new Permission Set, such as OrchestraCMS Library Media Conversion.
  6. Click Save.
  7. In the interface for your new Permission Set, under System, click System Permissions.
  8. Enable “Update Records with Inactive Owners”.

Change the name or description of a media library

You can change the name and description of any media library. The name of each media library is shown in the Media section and in the Browse Media Library dialog.

Edit the name and description of a media library

  1. In OrchestraCMS Setup, under Utilities, click Manage Libraries.
  2. To edit a library, click Edit. On the Edit Library page, change the text in the Name and Description fields as required.
  3. Click Save.
    • “Allow Uploads” is selected by default, but you can choose to deselect it.
    • Publish on Upload is automatic by default.

Establish a versioned media library

You can add a new Salesforce or Amazon library that automatically becomes a versioned library.

Establish a versioned library or libraries

  1. In OrchestraCMS Setup, under Utilities, click Manage Libraries.
  2. Click Add Library.
  3. Choose the relevant repository from the Repository drop-down menu. This automatically enables a versioned library.
  4. Optionally, click Edit on your default (non-versioned) Salesforce or Amazon library.
  5. Click Convert. This will enable the non-versioned Salesforce library to become versioned.
 

Once a library is converted to a versioned library, it can’t be undone.

You can share a media library so it appears in the media library list for all of your sites installed to OrchestraCMS. OrchestraCMS users can then work with the media library and access its files regardless of the site they currently have opened in OrchestraCMS.

 

Once a library is shared with other sites, it can’t be unshared.  

Share a media library with other sites in OrchestraCMS

  1. In OrchestraCMS Setup, under Utilities, click Manage Libraries.
  2. Click Edit next to the media library you want to share.
  3. On the Edit Library page, next to Sharing, select Yes.
  4. Click Save.

Now that you have shared the library, you can enable it in your other sites.

Enable a shared media library in another site

  1. In OrchestraCMS Setup, under Utilities, click Manage Libraries.
  2. Click Disabled next to the media libary you shared to enable it.
  3. Click Profiles.
  4. Click Edit beside the OrchestraCMS System Administrator profile. Click Save.
  5. Click Edit beside a profile to which you want to assign permission.
  6. On the Edit OrchestraCMS Profile page, under Library Permissions, check the boxes to assign the permissions you want. Click Save.
  7. Repeat the above steps for each OrchestraCMS profile to which you want to assign permissions.

Enable or disable file uploads from OrchestraCMS

We recommend that file uploads are always permitted for OrchestraCMS media libraries. By default, new media libraries allow uploads. However, you can disable the ability to upload files from OrchestraCMS. You might want to do this if:

  • All the required files are already uploaded and you do not want OrchestraCMS users to add more files.
  • Files are uploaded directly to an Amazon S3 or Google Cloud Storage bucket and are manually synchronized with OrchestraCMS.

To enable or disable media file uploads from OrchestraCMS

  1. In OrchestraCMS Setup, under Utilities, click Manage Libraries.
  2. Click Edit next to the media library you want to modify.
  3. On the Edit Library page, do one of the following:
    • To disable uploads, click to clear the Allow Uploads check box.
    • To enable uploads, click to select the Allow Uploads check box.
  4. Click Save.

If you disable uploads to a media library, the OrchestraCMS profile permission, which grants the ability to upload to that library, has no effect.

Edit an access key and secret access key

  1. If your security credentials change for your Amazon Web Services account or Google Cloud Storage project, you need to update the access key and secret access key in OrchestraCMS.
  2. To edit the access key and secret access key for an Amazon or Google media library
    • In OrchestraCMS Setup, click Manage Libraries. 
    • Click Edit next to the media library that requires updated security credentials.
    • On the Edit Library page, enter the new access key in the Access Key ID field.
    • Enter the new secret access key in the Secret Access Key field.
    • Click Test to verify that a connection can be made to the external bucket.
    • Click Save.
 

You can’t modify the Live Site Bucket Link or Secure Bucket Link fields after a library is created; if these need to be changed, you can remove the existing library and create a new one.