Implementation Guide › Optimizing Identity Manager › Runtime Components Tuning › JMS Settings › Tuning JMS Settings

Tuning JMS Settings

The following application server JMS tuning parameters define Queue connections and Message Driven Bean instance pools.

• WebSphere JMS Tuning

  WebSphere provides two parameters that you can configure to improve performance of event state transactions:

  • The number of connections in the Queue Connection Factory that are available for posting JMS messages
  • The number of instances of Message Driven Bean objects for processing the posted messages

  Use the WebSphere Administration Console to set the following properties:

  • Set the maximum session pool connections for the EventMsgQueue Queue Connection Factory to 128
  • Set the maximum sessions for the SubscriberMessageEJBPort Listener Port in the Message Listener Service to 128
• WebLogic Tuning

  In WebLogic application servers, Queue Connection Factories obtain connection-handling threads from the server's JMS Thread Pool or the default execute pool, depending on the JMS Thread Pool size. If the JMS Thread Pool size is 0, then WebLogic uses the threads in the execute pool.

  CA recommends setting the number of JMS Thread Pool threads equal to the maximum Bean Pool size for the Identity Manager Event Message Driven Bean, which is set to 128 by default.

  You use the WebLogic Server Console to set the JMS Thread Pool size in the JMS Services properties for the domain and server where CA Identity Manager is installed.

  The Identity Manager Event Message Driven Bean pool size is set by modifying the max-beans-in-free-pool setting in the descriptor file in the following location:

  WebLogic_home\domain\applications\IdentityMinder.ear\identityminder_ejb_jar\META-INF\weblogic-ejb-jar.xml

  <weblogic-enterprise-bean>
          <ejb-name>SubscriberMessageEJB</ejb-name>
          <message-driven-descriptor>
              <pool>
                  <max-beans-in-free-pool>128</max-beans-in-free-pool>
                  <initial-beans-in-free-pool>16</initial-beans-in-free-pool>
              </pool>
              <destination-jndi-name>com.netegrity.ims.msg.queue</destination-jndi-name>
          </message-driven-descriptor>
      </weblogic-enterprise-bean>
  

• JBoss Tuning

  In JBoss application servers, Queue Connection Factories obtain connection-handling threads from the server’s Standard JMS Pool session factory. By default, the number of maximum threads is set to 15.

  CA recommends setting this value to match the maximum size value of the Standard Message Bean Container.

  The JMS Session Pool section factory is set in the MaximumSize element of the JMSContainerInvoker in the following file:

  jboss_home\server\default\conf\standardjboss.xml

  <invoker-proxy-binding>
           <name>message-driven-bean</name>
           ….
           <proxy-factory-config>
              <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI>
              <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
              <MaximumSize>128</MaximumSize>
              <MaxMessages>1</MaxMessages>
              ….
           </proxy-factory-config>
       </invoker-proxy-binding>
  

  The Identity Manager Event Message Driven Bean pool size is set by modifying the maximum size value in the following descriptor file:

  jboss_home\server\default\conf\standardjboss.xml

  <container-configuration>
           <container-name>Standard Message Driven Bean</container-name>
           <call-logging>false</call-logging>
           <invoker-proxy-binding-name>message-driven-bean</invoker-proxy-binding-name>
          ……
           <container-pool-conf>
              <MaximumSize>128</MaximumSize>
           </container-pool-conf>
     </container-configuration>