Establishing a Connection to the Device Portal

Requirements

• Existing Internet connection
• Login with your Bosch ID
• Tenant ID

Process

1. In the browser, call up the following URL with the appropriate Tenant ID: https://deviceportal.bosch.com/?=tenantId

   The Tenant ID is a unique identifier of an organization.

The Device Portal is loaded and the Device Overview view appears.

Requesting a Separate Artifact Repository for the Tenant or Connecting an Existing One

An Artifact Repository must be requested to be able to roll out your own software or configurations to your devices. This Artifact Repository is available either in the form of a Private Artifact Repository or Managed Artifact Repository.

The Private Artifact Repository must be set up and operated in its own Azure subscription, while the Managed Artifact Repository is available as part of the Device Portal solution and only has to be connected to the tenant.

The software, configurations, backups and diagnostic files for the Managed Artifact Repository are stored in the Nexeed Device Portal solution.

There is a separate additional Rexroth AG software repository for the ctrlX CORE. This solution from Rexroth AG can only be connected directly when creating the tenant and cannot be requested via the Artifact Repository configuration window.

For more information, see the performance specification, the Developer Guide or the Artifact Management Guide.

1. Log in to the relevant tenant.
2. Click on any device in the Device Overview, (e.g. ctrlX CORE) that has the software category Software Management.

   

3. Click Configuration.

   

   The Your connected Artifact Repositories dialog opens.

   

   • (1) Displays all connected Private Artifact Repositories and Managed Artifact Repositories .
   • (2) Request to connect a Managed Artifact Repository if it is not yet connected.
   • (3) Request to create and connect a Private Artifact Repository.

   Up to 3 Private Artifact Repositories can be connected to one tenant.

   The Private Artifact Repository must be operated in a separate Azure subscription to the Managed Artifact Repository.

4. Click on Connect Managed Artifact Repository (2) to connect a Managed Artifact Repository.

   An email template opens.

   

5. List in the email under Artifact Types (2) for which functionality the Managed Artifact Repository is to be used.

   The artifact are only visible in the Device Portal if the artifact types have been saved when the Artifact Repository is connected. Therefore, we recommend that you request all artifact types immediately before using them for the first time. Artifacts with the risk level (1) stable, edge, candidate and beta should also be requested.
   
   The significance of the Artifact Types and Risk Levels is explained in the How to Manage Artifacts guide. This is available to the customer on request.

   • Backup/restore and diagnostics: Enter BACKUP and DIAGNOSTIC_DATA.
   • Software and setup file management: Enter SOFTWARE and SETUP.
6. After receiving the feedback from Device Portal Support, check whether the requested Artifact Repository is connected correctly:
   • In the Device Overview in the Software tab , check whether the artifacts are marked with a yellow or red icon.

     After connecting a Managed Artifact Repository, the icons are yellow.

     After connecting a Private Artifact Repository, the icons are red.

   

   • If a Rexroth AG Repository is connected for ctrlX CORE, the icons are blue.

   

   • Open the configuration again and check in the Your Connected Artifact Repositories dialog whether the Managed Artifact Repository, including the configured artifacts, which are visible in the Device Portal and can be used by the devices, is displayed.

     The screenshot shows backups, diagnostic files, setup files and software. The documentation page of the Artifact Repository is also displayed for the Managed Artifact Repository.

   

The Private or Managed Artifact Repository is now connected to the tenant. See Deploying Your First Own Software for a description of how artifacts can now be managed in the Artifact Repository