Solving Transport-Related Problems

Sometimes it is necessary to transport a service from one system to another. A common use case, for example, is when a fully developed service is moved from the development system to the production system.

If one of the following points applies to your service, you must take action.

Transporting Services with File Upload or Image Elements

As explained on page Going Live with a Designer Service, we recommend that you do not run the Designer on a production system. Therefore, the compiled service (.rep file) is deployed in the PAS Administration of the target system.

If your service contains forms that include upload elements (File Upload or Image elements), there is one thing you need to bear in mind:

Files that are uploaded during runtime are loaded into the profile (“sandbox”) in which the service was originally created. If this profile is missing, the file upload fails and the form elements remain empty.

If such a service is transported from one system to the next, you need to perform the following tasks:

• On the source system, export the profile in which the service has been created.
  Refer to Exporting User Data in the Administration Guide for details.

• Import the profile on the target system.
  Refer to Importing User Data in the Administration Guide for details.

• Assign the profile to all users that should be able to execute the application.
  Refer to Editing a User in the Administration Guide for details.

Expert Advice

Before you start developing a service, you should give some thought to the name of the profile in which you are developing.

Transporting Resources

Resources likes images or documents that you use in the forms of your services are included in a service export.
For example: If you have uploaded a logo to an Image element in a form to display it in the form header, or if you have pre-populated a File Upload element with a PDF file to be available for users to download, these resources will be part of the .zip folder when you export the service from Designer.

Exception: CSS Files

CSS files are uploaded to the File Manager and only referenced in the Designer service. You must therefore also upload every CSS file that you have assigned in the Designer service to the file manager of the target system.

The reference to the used CSS file(s) is part of the service export, so you don’t need to assign the CSS to your Designer service again.

Keep the name of the CSS file when you upload it to the target system.

Transporting Role-Based Services

Each role has a unique ID. If you want to use the same roles in the service on the target system that you are using on the source system, you must also transport these roles from the source system to the target system. The easiest way to transfer roles from one User Management to the other is to use the import/export functionality of the User Management.

Refer to Administration Guide > Reusing Central Roles for a detailed description how to transport identical roles from one system to another.

In some special use cases, you do not want to use identical roles on different systems, for example if several customers want to run the same service. In that case, you can exchange the role's UUIDs in the settings of the xUML service.

Refer to Administration Guide > Reusing Central Roles for a detailed description how and where to change the role's UUIDs.

Related Content