How the file reference path will be managed for nested schemas when the BC server is running on Solaris and the Designer is running on Windows

How the file reference path will be managed for nested schemas when the BC server is running on Solaris and the Designer is running on Windows

book

Article ID: KB0088200

calendar_today

Updated On: 01-14-2017

Products Versions
TIBCO BusinessConnect -
Not Applicable -

Description

Resolution:
Description:

In a multiple machine environment, after uploading a schema in BC as file references with nested schemas, Designer is not able to load the schema because the reference path is different between machines.

Environment:

Designer and BC running on different machines

Resolution:

If nested schemas are configured as file references, their location should not change compared to the configured location in the operations editor. This is due to the fact that the content of the schema components are loaded into the BusinessConnect schema cache on-demand from the specified location. In addition, if the BC palette-based private process imports operations that have been configured with such referenced schemas, the original location - with the same path - must be accessible from the importing project only for the duration of the update. After the update on the palette-based project is complete there is no further correlation between the original schema file resources and the imported schemas.

When using nested schemas in BusinessConnect, use the file reference option and make sure that all dependant schemas are present within the same directory. This way the BC palette will also be able to import the mentioned schemas in Designer.

1.  Set up the schema as a file reference in BC.
2.  Import it into BW.
3.  Import the rest of the nested schemas into a subdirectory in your BW project.
4.  Open the root schema in BW.  When it asks for the reference to a sub-schema, select the appropriate file in the imported BW directory.

Issue/Introduction

How the file reference path will be managed for nested schemas when the BC server is running on Solaris and the Designer is running on Windows