IBM PEM integration deployment

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

IBM PEM requires access to an email server to send email registration invitations and various notifications. A database is also required to store customer and system information. IBM MQ is required 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, and PEM Partner Provisioner.

For a production environment, multiple instances of service components such as PEM Portal, PEM Partner Repository, and PEM Partner Provisioner 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.

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