Useful Tips for API Connect Liberty Collective

Useful Tips

Here are some useful tips to prevent some common user configuration issues.

All the Host machines in the collective and the machines where you publish application using the APIC Toolkit must have the same architecture, OS, node version and npm versions.

Examples of not to have APIC Toolkit installed on a windows machine while your collectives are on linux . Controller installed on Linux and members and APIC Toolkit on Mac. Make sure the controllers, members can communicate to each other.
When perform the setup , always use Fully qualified host name. In some environment
with dynamic IP, IP will change, therefore IP is not reliable to use. In production, the goal is to avoid single point of failure.

The collective members should be on a separate machine as your controller.

You should have more than one members and each one should be on separate machine.

If you want High Availability, (HA), you should have at least 3 controllers, each installed on a different machine.

Utilize the Help commands apic apps:publish h wlpn-controller help wlpn-controller help setup wlpn-collective help wlpn-collective help registerHost wlpn-collective help updateHost

Logging

Enable the tracing in server.xml in ~/.liberty/wlp/usr/servers/controller/

<logging tracespecification="com.ibm.ws.collective.command.internal.*=all:Scaling=all:com.ibm.ws.imf.*=all:com.ibm.ws.collective.deploy.*=all:com.ibm.ws.scaling.manager.stack.internal.*=all" />

Ports information: Default controller adminCenter https port: 9443 The application port information:
join.json under wlpn folder in the member Host machine Refrain from manually modify the ports When your collective is totally messed up and you want to start over To scrap controller from controller machine killall -9 java killall -9 node rm -R ~/.liberty npm uninstall -g apiconnect-collective-controller To scrap the members from machine killall -9 node rm -R ~/wlpn npm uninstall -g apiconnect-collective-member Prior to contact support

Before contacting support, validate your configuration by using the wlpn-diagnostic tools

Install the diagnostic tools on the controller machine.

npm install g wlpn-diagnostics
wlpn-diagnostic checkAll Information to provide when contact support Versions of the Products and and environment
apic --ext-version
wlpn ext-version
wlpn-controller version
node v
npm v Where did you install the Toolkit and collective member code from?
npmjs.org or From fix-central Topology on your environment OS/architecture of the controller, member , APIC toolkit machines How many Remote members or local members? How many controllers? Reproducible Steps. How often is the failure? Has it ever worked before? When does the failure start to to occur? Logs: Controller machine server logs location:
~/.liberty/wlp/usr/servers/controller/logs apic log location:
~/.apiconnect/apic.log wlpn-diagnostics information Useful References:

removing application from collective

logging microgateways and apic