Integration Cloud 6.1.0 | Applications | Predefined Applications | Siemens MindSphere
 
Siemens MindSphere
Integration Cloud connects to Siemens MindSphere using the API version 2.0 and allows you to create aspects and post data into a MindSphere asset.
Note:
The fields displayed may vary according to the version of the Application.
Field
Description
Server URL
Provide the login endpoint to initiate communication with the SaaS provider. For example, https://mindconnectcom.apps.mindsphere.io/
Response Timeout
The number of milliseconds Integration Cloud waits for a response before canceling its attempt to connect to the back end. In case the network is slow or the back end processing takes longer than usual, increase the Response Timeout value. It is recommended to specify a value other than 0. If you specify 0, Integration Cloud will wait indefinitely for a response.
Retry Count on Response Failure
The number of times Integration Cloud attempts to connect to the back end to read a response if the initial attempt fails. If an I/O error occurs, it will retry only if you have selected the Retry on Response Failure option.
Retry on Response Failure
Whether Integration Cloud should attempt to resend the request when the response has failed, even though the request was sent successfully. Select this option if you want to re-establish the connection.
Keystore Alias
Select the alias for the Integration Cloud key store configuration. This is a text identifier for the keystore alias. A keystore file contains the credentials (private key/signed certificate) that a client needs for authentication. You can also add a new Keystore from this field.
Client Key Alias
Alias to the private key in the keystore file specified in the Keystore Alias field. The outbound connections use this key to send client credentials to a remote server. To send the client’s identity to a remote server, you must specify values in both the Keystore Alias and the Client Key Alias fields.
Hostname verifier
Select a hostname verifier implementation. Guards against man-in-the-middle (MITM) attacks. The default is org.apache.http.conn.ssl.DefaultHostnameVerifier, which will enable hostname verification. Select org.apache.http.conn.ssl.NoopHostnameVerifier to disable hostname verification.
MSU Limit
MindSphere Unit (MSU) limit for an asset. MSU is the basis for fees invoiced monthly per asset and as per a used application.
Security Profile
The type of security profile/algorithm used for token generation. Default is SHARED_SECRET.
Agent Id
The ID of the agent managing a MindSphere asset.
Schemas
Schemas used by the MindSphere platform. Default is urn:siemens:mindsphere:v1.
IAT
Initial access token for agent onboarding.
Tenant
The tenant ID of the onboarded agent.
Links
Links returned upon successful agent onboarding.
JWT Signing Algorithm
The JSON Web Token (JWT) signing algorithm. Default is HS256 (HMAC with SHA 256).
JWT Token Expiration (msec)
The JWT token expiration time in milliseconds. Default is 600000.
JWT Audience
The JWT Audience. Default is MindSphere AS.
Enable SNI
Server Name Indication (SNI) is an extension to the TLS protocol by which a client indicates which host name it is attempting to connect to at the start of the handshaking process. Enable this option if the SaaS provider offers SNI-based TLS connectivity, and if you want to connect to an SNI enabled SAAS provider to send the host name specified in the Server URL field, as part of the TLS SNI Extension server_name parameter.
SNI Server Name
If you want to explicitly specify a host name to be included as a part of the SNI extension server_name parameter, in case the host name is other than the host name specified in the Server URL field, specify the host name value in the SNI Server Name field.