This guide covers installing adapters and custom applications on Platform 6, including how to migrate them from a previous Platform version.
Before you proceed, note the following differences in Platform 6:
Use this procedure to migrate adapters from a legacy Platform installation to Platform 6.
Compress each adapter using zip, gzip, or tar, then transfer the compressed file to the Platform 6 system.
On the Platform 6 system, decompress each adapter into:
The services directory should contain individual adapter directories directly — not a namespace directory wrapping them.
For each adapter, complete the configuration steps in the Install an adapter section below.
Repeat this procedure for all adapters on the legacy system, including custom adapters in non-standard namespaces.
In the Admin Essentials GUI, create a new service instance for the adapter.
In the Admin Essentials GUI, open the service instance configuration for the adapter.
Copy the properties from sampleProperties.json in the adapter directory and paste them into the inner (second) properties object in the service instance configuration. Update host, port, authentication method, credentials, and any other environment-specific values.
In a high availability (HA) cluster, you must install the adapter source code on every node before creating the adapter instance. This ensures the adapter can run on any node in the cluster.
On every node in the cluster, follow the Install an adapter steps above.
From any node, open Admin Essentials and create a new adapter instance. See Adapters for instructions.
In the Configuration tab, edit the service config to match your environment, then click Save. Saving automatically restarts the adapter on that node.
The auto-restart in the previous step only affects the node where you saved the config. On each remaining node, restart Itential Platform so that it loads the new adapter instance from the shared database:
The adapter instance is now running on all nodes in the cluster.
Adapter debug logging captures three event types:
Most adapter issues relate to configuration and authentication. Check the adapter’s sampleProperties.json for documented authentication approaches, and the AUTH.md file for a description of the login process and requirements.
When using SSL/TLS, enable SSL in the service instance configuration and provide a CA file. Accepting invalid certificates is not recommended for production environments.
For missing or outdated API calls, use the adapter’s generic methods to continue work while a formal update is added. Generic adapter calls let you define custom endpoints and parameters directly.
For additional support, contact the Itential Adapters Team: Here to Help.