Versions Compared

Old Version 1

changes.mady.by.user Former user

Saved on

compared with

New Version 2

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Re-doing Tharindu's changes related to JMS Event Publishing Parameters

...

<JMSEventPublisherParameters> <java.naming.factory.initial>org.wso2.andes.jndi.PropertiesFileInitialContextFactory</java.naming.factory.initial> <java.naming.provider.url>repository/conf/jndi.properties</java.naming.provider.url> <transport.jms.DestinationType>topic</transport.jms.DestinationType> <transport.jms.Destination>throttleData</transport.jms.Destination> <transport.jms.ConcurrentPublishers>allow</transport.jms.ConcurrentPublishers> <transport.jms.ConnectionFactoryJNDIName>TopicConnectionFactory</transport.jms.ConnectionFactoryJNDIName> </JMSEventPublisherParameters>
Expand
titleClick here for information on starting the Gateway nodes.

Step 5.1 - Start the Gateway Manager

  • Comment the following configurations in the <API-M_HOME>/repository/conf/api-manager.xml file.

    Code Block
    <JMSEventPublisherParameters>
   <java.naming.factory.initial>org.wso2.andes.jndi.PropertiesFileInitialContextFactory</java.naming.factory.initial>
   <java.naming.provider.url>repository/conf/jndi.properties</java.naming.provider.url>
   <transport.jms.DestinationType>topic</transport.jms.DestinationType>
   <transport.jms.Destination>throttleData</transport.jms.Destination>
   <transport.jms.ConcurrentPublishers>allow</transport.jms.ConcurrentPublishers>
   <transport.jms.ConnectionFactoryJNDIName>TopicConnectionFactory</transport.jms.ConnectionFactoryJNDIName>
</JMSEventPublisherParameters>


    • Start the Gateway Manager by typing the following command in the command prompt.



    Code Block
    sh <API-M_GATEWAY_MANAGER_HOME>/bin/wso2server.sh



    Step 5.2 - Start the Gateway Worker

    Tip

    It is recommendation to delete the <API-M_HOME>/repository/deployment/server directory and create an empty server directory in the worker node. This is done to avoid any SVN conflicts that may arise. Note that when you do this, you have to restart the worker node after you start it in order to avoid any errors from occurring.

    Update the <API-M_HOME>/repository/conf/api-manager.xml file by commenting out the following configurations.

    Code Block

    Start the Gateway Worker by typing the following command in the command prompt.

    Code Block
    sh <GATEWAY_WORKER_HOME>/bin/wso2server.sh -Dprofile=gateway-worker

    The additional -Dprofile=gateway-worker argument indicates that this is a worker node specific to the Gateway. You need to use this parameter to make a server read-only. Changes (i.e., writing or making modifications to the deployment repository, etc.) can not be made in the Gateway worker nodes. Furthermore, starting a node as a Gateway worker ensures that the Store and Publisher related functions are disabled in the respective node. This parameter also ensures that the node starts in the worker profile, where the UI bundles are not activated and only the backend bundles are activated when the server starts up. For more information on the various product profiles available in WSO2 API Manager, see API Manager product profiles.