IBM PEM integration deployment

The IBM PEM is a community management portal and it is accessed by System Administrators, Sponsor users, and Partner users.

IBM PEM requires the following accesses:
  • an email server to send email registration invitations and various other notifications,
  • a database to store customer and system information,
  • IBM WebSphere MQ to enable communication between PEM Partner Repository and PEM Partner Provisioner.

IBM PEM uses REST based APIs to establish communication between the PEM Portal, PEM Partner Repository, PEM Partner Provisioner, and PEM Community Manager.

For a production environment, multiple instances of service components such as PEM Portal, PEM Partner Repository, PEM Partner Provisioner, and PEM Community Manager are supported that can be load balanced. Load balancing is done by using sticky session, which is a method that is used with Application Load Balancing to achieve server-affinity. Multiple instances of scan and certificate update agents can also be run at the same time in parallel.

deployment Deploy Agent Deploy Agent Deploy IBM PEM Portal API Gateway Deployment Reverse Proxy Deploying the Purge tool Creating the database objects Deploy PEM Partner Repository Deploy PEM Partner Provisioner Mail server Configuring Topologies Partner management Sponsor user management High availability architecture