Resolution:
When importing a BC protocol into Designer with the BusinessConnect connector, the connector will try to resolve any file references in XML schemas on the machine that is is running on rather than the machine where the schemas actually reside.   For example, if you are running Designer on machine A, and the repository, schemas, and BC engine are on machine B, and you try to import a SOAP configuration that has file references to schemas rather than the schemas themselves, the import will fail.  You will see this in the Designer by clicking on Window&gtShow console which will display a number of exceptions.

To work around this issue, create a directory structure on the machine running Designer identical to the directory structure on the machine where the schemas are located, and populate it with the desired schemas.  The BC Connection should be able to do the import after this is created.

When doing an import of a protocol schema in Designer, the protocol does not show up, and the BC Connection seems to hang.Why is this?