Configuring the iConnector URL

You need to update Admin Panel to your iConnector configuration URL. This is the URL where the CumulusPro Clients need to upload the documents to.

 

 

In the Admin Panel – Organisation click on ‘Organisation Settings’The organisation settings should look like this:

 

Where the red arrow is, insert the URL where you will run your iConnector Server. A typical URL looks like this:

https://<servername>/<directory>/ConnectorService.svc/json

 

For the Straatos platform, select the followin Server Connector URL:
Europe Data Center: https://effektif-connector-europe.cumuluspro.net/ConnectorService.svc/json
Asia Data Center:  https://effektif-connector-asia.cumuluspro.net/ConnectorService.svc/json

 

Additional Information available for the use in your iConnector

Custom Configuration

The Custom Configuration can be used to pass any data to the backend with the Metadata Upload; for example, a JSON data structure with routing information specific to this Configuration. The value will not travel through the Web Browser / JavaScript, but is directly forwarded from the Configuration Repository to the upload.

 

OAuth2 Client Credential Grant

Requests from the Scan clients to the backend can be protected using OAuth 2 Client Credentials Grant (http://tools.ietf.org/html/draft-ietf/oauth-v2-31). If this option is enabled, the OAuth2 Access Token URL, the Access Token and the Client Secret must be specified for this Configuration. The Access Token URL should point to your own OAuth 2 Token Server (see Architectural Diagram in API - Extended Scenario).

 

Unique (Configuration) ID

The Unique ID is your configuration ID and a unique identifier for your Clients to know to which configuration to refer to. The Links created for the Client Configuration are also using the Configuration ID to retrieve the settings from the Admin Panel.

 

Web Service Key

A unique Web Service Key is also generated for each Configuration. If the Document Type Service is used to add, modify or delete Document Types using an automated Web Service, the Web Service Key has to be specified to authorize the requests (see Appendix 6 – Architecture Overview – Advanced Scenarios).

Create your own Knowledge Base