Coco notebooks - Integration connector configuration fails when run from assembly.

[planetf1]

Configuring exchangeDL01 integration connectors ...
   ... configuring the files-integrator integration service in exchangeDL01 integration daemon ...
{'class': 'IntegrationServiceRequestBody', 'omagserverPlatformRootURL': 'https://localhost:9444', 'omagserverName': 'cocoMDS1', 'integrationServiceOptions': {}, 'integrationConnectorConfigs': [{'class': 'IntegrationConnectorConfig', 'connectorName': 'OakDeneLandingAreaFilesMonitor', 'connectorUserId': 'onboardDL01npa', 'connection': {'class': 'Connection', 'connectorType': {'class': 'ConnectorType', 'connectorProviderClassName': 'org.odpi.openmetadata.adapters.connectors.integration.basicfiles.DataFilesMonitorIntegrationProvider'}, 'endpoint': {'class': 'Endpoint', 'address': 'data/landing-area/hospitals/oak-dene/clinical-trials/drop-foot'}}, 'metadataSourceQualifiedName': 'HospitalLandingArea', 'refreshTimeInterval': 10, 'usesBlockingCalls': 'false'}, {'class': 'IntegrationConnectorConfig', 'connectorName': 'OldMarketLandingAreaFilesMonitor', 'connectorUserId': 'onboardDL01npa', 'connection': {'class': 'Connection', 'connectorType': {'class': 'ConnectorType', 'connectorProviderClassName': 'org.odpi.openmetadata.adapters.connectors.integration.basicfiles.DataFilesMonitorIntegrationProvider'}, 'endpoint': {'class': 'Endpoint', 'address': 'data/landing-area/hospitals/old-market/clinical-trials/drop-foot'}}, 'metadataSourceQualifiedName': 'HospitalLandingArea', 'refreshTimeInterval': 10, 'usesBlockingCalls': 'false'}, {'class': 'IntegrationConnectorConfig', 'connectorName': 'DropFootClinicalTrialResultsFilesMonitor', 'connectorUserId': 'monitorDL01npa', 'connection': {'class': 'Connection', 'connectorType': {'class': 'ConnectorType', 'connectorProviderClassName': 'org.odpi.openmetadata.adapters.connectors.integration.basicfiles.DataFolderMonitorIntegrationProvider'}, 'endpoint': {'class': 'Endpoint', 'address': 'data/data-lake/research/clinical-trials/drop-foot/weekly-measurements'}}, 'metadataSourceQualifiedName': 'DropFootClinicalTrialResults', 'refreshTimeInterval': 10, 'usesBlockingCalls': 'false'}]}
   ...... (POST https://localhost:9445/open-metadata/admin-services/users/garygeeke/servers/exchangeDL01/integration-services/files-integrator )
   ...... Response:  {'class': 'VoidResponse', 'relatedHTTPCode': 400, 'exceptionClassName': 'org.odpi.openmetadata.adminservices.ffdc.exception.OMAGInvalidParameterException', 'exceptionCausedBy': 'org.odpi.openmetadata.frameworks.connectors.ffdc.ConnectionCheckedException', 'actionDescription': 'configureIntegrationService', 'exceptionErrorMessage': "OMAG-ADMIN-400-041 The connection passed to the configureIntegrationService method does not describe a valid connector.  Connection object is: Connection{displayName='null', description='null', connectorType=ConnectorType{displayName='null', description='null', connectorProviderClassName='org.odpi.openmetadata.adapters.connectors.integration.basicfiles.DataFilesMonitorIntegrationProvider', recognizedAdditionalProperties=null, recognizedSecuredProperties=null, recognizedConfigurationProperties=null, qualifiedName='null', additionalProperties=null, type=null, guid='null', url='null', classifications=null}, endpoint=Endpoint{displayName='null', description='null', address='data/landing-area/hospitals/oak-dene/clinical-trials/drop-foot', protocol='null', encryptionMethod='null', qualifiedName='null', additionalProperties=null, type=null, guid='null', url='null', classifications=null}, userId='null', encryptedPassword='null', clearPassword='null', configurationProperties=null, securedProperties=null, assetSummary='null', qualifiedName='null', additionalProperties=null, meanings=null, securityTags=null, searchKeywords=null, confidentialityGovernanceClassification=null, confidenceGovernanceClassification=null, criticalityGovernanceClassification=null, retentionGovernanceClassification=null, type=null, GUID='null', URL='null', classifications=null, extendedProperties=null, headerVersion=0}.  The resulting exception org.odpi.openmetadata.frameworks.connectors.ffdc.ConnectionCheckedException had message of OCF-CONNECTION-400-005 Unknown Connector Provider class org.odpi.openmetadata.adapters.connectors.integration.basicfiles.DataFilesMonitorIntegrationProvider passed in connection <Unknown>, system action of The system is unable to create the requested connector instance because the Connector Provider's class is not known to the JVM.  This may be because the Connector Provider's jar is not installed in the local JVM or the wrong Java class name has been configured in the connection. and user action of Verify that the Connector Provider and Connector jar files are properly configured in the process.  Update the connection configuration to include a valid Java class name for the connector provider in the connectorProviderClassName property of the connection's connectorType. Then retry the request.", 'exceptionErrorMessageId': 'OMAG-ADMIN-400-041', 'exceptionErrorMessageParameters': ['configureIntegrationService', "Connection{displayName='null', description='null', connectorType=ConnectorType{displayName='null', description='null', connectorProviderClassName='org.odpi.openmetadata.adapters.connectors.integration.basicfiles.DataFilesMonitorIntegrationProvider', recognizedAdditionalProperties=null, recognizedSecuredProperties=null, recognizedConfigurationProperties=null, qualifiedName='null', additionalProperties=null, type=null, guid='null', url='null', classifications=null}, endpoint=Endpoint{displayName='null', description='null', address='data/landing-area/hospitals/oak-dene/clinical-trials/drop-foot', protocol='null', encryptionMethod='null', qualifiedName='null', additionalProperties=null, type=null, guid='null', url='null', classifications=null}, userId='null', encryptedPassword='null', clearPassword='null', configurationProperties=null, securedProperties=null, assetSummary='null', qualifiedName='null', additionalProperties=null, meanings=null, securityTags=null, searchKeywords=null, confidentialityGovernanceClassification=null, confidenceGovernanceClassification=null, criticalityGovernanceClassification=null, retentionGovernanceClassification=null, type=null, GUID='null', URL='null', classifications=null, extendedProperties=null, headerVersion=0}", 'org.odpi.openmetadata.frameworks.connectors.ffdc.ConnectionCheckedException', 'OCF-CONNECTION-400-005 Unknown Connector Provider class org.odpi.openmetadata.adapters.connectors.integration.basicfiles.DataFilesMonitorIntegrationProvider passed in connection <Unknown>', "The system is unable to create the requested connector instance because the Connector Provider's class is not known to the JVM.  This may be because the Connector Provider's jar is not installed in the local JVM or the wrong Java class name has been configured in the connection.", "Verify that the Connector Provider and Connector jar files are properly configured in the process.  Update the connection configuration to include a valid Java class name for the connector provider in the connectorProviderClassName property of the connection's connectorType. Then retry the request."], 'exceptionSystemAction': 'The connection was tested by the Open Connector Framework (OCF) Connector Broker and it was unable to create aconnector for this connection and returned a detailed exception. Because of this exception, the system is unable to accept an invalid connection object and so the request is rejected.  No change is made to the configuration.', 'exceptionUserAction': 'Use the detail messages from the connector broker to work out what is wrong with the connection object.  Once the connection object is corrected, retry the request.'}

Done.

The line below also fails, but is referred to in the text as an example of error handling.

So for the original error we need to verify the assembly is correct.

In my environment (currently local) LOADER_PATH is set to include server/lib from the assembly

See also #4667 for intentional upcoming changes to the assemblies

[planetf1]

Assigning this to myself. Testing in another environment worked ok, so need to debug the cause in the failing environment.
This suggests the setup is broadly correct.

[planetf1]

I have a few different scripts to launch the environment to test different aspects.
One had a typo in the loader path.
Corrected & working
-> User error
Closing.