EMCECS Adapter Configuration
This section will provide you details on how to configure a storage endpoints connection string to utilize the EMCECS Adapter, which is standard with StoragePoint. Please refer to the StoragePoint Reference Guide for information on managing Storage Endpoints.
For more information on the EMCECS implementation, see the EMC documentation.
On the Application Management page, click Storage and Backup Endpoints.
Click Create New Endpoint or click the name of an existing storage endpoint that you want to edit.
Click the Show link next to the Advanced Adapter Settings to see the additional fields.
![EMCECS2](/ja-jp/technical-documents/image/8d8c2822-4501-4d7e-8991-2dda27e820b0)
![EMCECS3](/ja-jp/technical-documents/image/231bfe02-841a-4ff6-a58a-711bbf2f82ea)
EMCECS Adapter Connection String Parameters
Setting
Value/Options |
Name Enter the unique name of the Storage or Backup Endpoint. |
Type
![fs2](/ja-jp/technical-documents/image/70c452a1-416a-41a3-8a81-d6dba5c64c99) Primary this endpoint will be available for externalization when creating storage profiles.
Backup this endpoint will be in the Backup Services dropdown on the profile page.
The selection is locked down when saving.
See Backup Services Settings in the Reference Guide for more information on how Backup Endpoints are used. |
Status
![fs3](/ja-jp/technical-documents/image/3f62b903-4d5a-4db7-8189-2853d12f3fc1) Online Storage Endpoint should be available to associate to a Storage Profile and accept BLOBs. (default)
Offline (Read Only) A storage endpoint can be configured, but not made available for externalizing content. The BLOBs already on the endpoint are still read only. |
![EMCECS4](/ja-jp/technical-documents/image/76b42396-680f-47c1-bb43-c7828bb54218) Select the adapter for the endpoint that is being created.
|
![EMCECS5](/ja-jp/technical-documents/image/ac31dedd-c2a2-491f-9e69-e144cbcf96eb) After selecting the Adapter EMCECS, an additional dropdown selection must be made to designate if Atmos or S3 protocol will be used for the endpoint configuration.
|
![atmos5](/ja-jp/technical-documents/image/f13f5f1e-1679-4dd9-8c21-d6a1854e0406) ATMOS: The username to use when connecting to the server. This is equivalent to the Token ID provided with your Atmos online account.
|
![atmos6](/ja-jp/technical-documents/image/4f3e494c-208a-44ba-8a00-24e6585272ab) ATMOS: The base64 encoded shared secret to use when signing requests to the server.
|
![atmos7](/ja-jp/technical-documents/image/5342de93-766c-4e74-9a39-5dfb5f85dbe9) ATMOS: IP address or host name that represents the Atmos instance or specific node to be used. Default = accesspoint.emccis.com.
|
![atmos8](/ja-jp/technical-documents/image/1e366a78-55fc-4024-9214-af194b86e3f4) ATMOS: The starting folder/container within your Atmos namespace under which all folders and files will be created.
|
![atmos9](/ja-jp/technical-documents/image/adcd705b-b5bf-412b-9e71-ff97de29edba) ATMOS: (yes/no) Determines whether or not the adapter negotiates an SSL connection for all data (and metadata) transfers. Default = No.
|
![emcecsAtmosPort](/ja-jp/technical-documents/image/06cedefa-d8c5-495f-bc99-c35166e4657c) ATMOS: The port on the server to communicate with. Default = 80 (443 if UseSSL is Yes).
|
![atmos11](/ja-jp/technical-documents/image/d6aa6dc4-c5e7-4031-b348-065070ac81a3) ATMOS: (yes/no) Includes a check-sum operation after each blob transfer. Allows the adapter to detect and log data integrity errors immediately. Default = No.
|
![EMCECS6](/ja-jp/technical-documents/image/023712d3-4a3f-4570-87cb-de3266c1e860) S3 Options
![info](/ja-jp/technical-documents/image/031af330-de78-4d63-a969-7649bf54c9f8)
|
NOTE: The EMCECS adapter can be used with the Dell ECS device, using the EMCECSS3 Adapter Settings. | |
![amazon5](/ja-jp/technical-documents/image/fe671892-ca40-457f-a172-cf89f8d9b458) S3: The Access Key ID provided when you signed up for the S3 service. Required.
|
![amazon6](/ja-jp/technical-documents/image/4499846d-f18b-4749-a186-f12e7680853d) S3: The Secret Access Key provided when you signed up for the S3 service. Required.
|
![amazon7](/ja-jp/technical-documents/image/5be42150-0efa-4778-a60b-457d26438b63) S3: The container within your S3 account where content associated with a storage profile will be stored. Bucket names are case sensitive and unique across the entire S3 service namespace.
|
![amazon8](/ja-jp/technical-documents/image/68e5ede3-af07-4383-8a96-8cf17f6a426e) S3: (true/false) Determines whether or not the adapter negotiates an SSL connection for all data (and metadata) transfers. Default = True.
|
![amazon9](/ja-jp/technical-documents/image/a786392f-f734-4bf3-8899-ef45997b7888) S3: Used to take the URL (optionally including a port) of a simple non-authenticating proxy that will be used when communicating with EMCECS services.
|
![amazon10](/ja-jp/technical-documents/image/cfe2f332-fc7b-4614-97bb-54b93077f3eb) IP or DNS name that represents the access point for the Amazon AWS service.
![info](/ja-jp/technical-documents/image/031af330-de78-4d63-a969-7649bf54c9f8)
|
NOTE: If a Fully Qualified Domain Name (FQDN) is used in "S3 Host", the IP address which points to the primary DELL EMC ECS storage node needs to be associated with a bucket; either via DNS record or via local OS "hosts" file:
<primary DELL EMC ECS storage node> <bucket name>.<FQDN>
It is also required to provide a new "Base URL" containing an FQDN (example below):
![EMCECSBaseURL](/ja-jp/technical-documents/image/3d36261b-afcd-4734-b016-817f518eb260)
| |
![amazon11](/ja-jp/technical-documents/image/e58691fe-caa5-4bd5-8e08-b700adb15bb8) Port used to access the S3 service. Default = 9020 for http and 9021 for https.
|
![clversafe9](/ja-jp/technical-documents/image/25f3c45e-9d51-4595-ba32-82da5ef5a3ed) (Yes/No) If UseSSL is Yes, the StrictSSL flag controls whether or not the use of "self-issued" or otherwise suspicious certificates on the system will be tolerated.
|
![clversafe10](/ja-jp/technical-documents/image/1d55328e-5f34-4396-8cb4-695ff4679924) Used in AWS4 request signing, this is an optional property; change it only if the region cannot be determined from the service endpoint.
For custom or private clouds or where StoragePoint cannot automatically retrieve the region because of security or permission reasons. |
Example Storage Endpoint using EMCECS Adapter
![emcECSS3example](/ja-jp/technical-documents/image/b426c7b8-4b8c-4e5f-9aea-c612fe451c3b)
![emcecsAtmosExample](/ja-jp/technical-documents/image/ddd09be4-f715-4e8a-9f30-2e89dffcde29)
Click the Show Connection String checkbox to edit the connection string. Otherwise, fill in the connection fields shown for the adapter selected. Notice that the connection string parameters are name/value pairs separated by semi-colons.
![emcECSS3exampleConnectionString](/ja-jp/technical-documents/image/93efe050-dd4a-469d-bc11-a7f39d32eeb9)
![emcecsAtmosExampleConnectionString](/ja-jp/technical-documents/image/b8fc1be2-b95e-45d6-8fb8-8db1b9b2814d)
![info](/ja-jp/technical-documents/image/031af330-de78-4d63-a969-7649bf54c9f8)
|
NOTE: Adapter parameters are not case-sensitive. |
![info](/ja-jp/technical-documents/image/031af330-de78-4d63-a969-7649bf54c9f8)
|
NOTE: You should always use a passphrase when generating encryption keys. The passphrase gives you a means of re-creating keys should they become unrecoverable or corrupt. It is very important to remember or record the passphrase outside of StoragePoint. Otherwise, encrypted content could become irretrievable in the event of a database failure. |
If you choose to externalize content you should test the storage profile settings by clicking the Test Storage Settings button. A message under the button will indicate whether or not the test was successful. If the test fails the message will include the error that was the root cause of the failure.
![info](/ja-jp/technical-documents/image/031af330-de78-4d63-a969-7649bf54c9f8)
|
NOTE: When testing access to an endpoint from within Central Administration, the Identity of the Application Pool hosting the Central Administration Site is the one that is being used for the test. If there are different Identities used for other Web Applications in the Farm then those identities will also need access but cannot be tested from within Central Admin itself. See BLOB Store Security and StoragePoint Required Privileges in the StoragePoint Reference Guide. |
Appendix: Troubleshooting