When you deploy WSO2 BAM in production, you often need to deploy it behind a proxy server or load balancer. We will see how to configure BAM behind Apache HTTP Server as reverse proxy.
Now you should be able access the BAM using following URLs
Management console - https://bamproxy.example.com/bamcarbon
Message console - https://bamproxy.example.com/messageconsole
Activity monitoring - https://bamproxy.example.com/activitymonitoring
BAM dashboards - https://bamproxy.example.com/bamdashboards
Apache HTTP Server Configuration
- Install and configure Apache HTTP server
- Enable following modules using a2enmod
- Run the following command
- Create a certificate and a key for Apache HTTP server. You will use these when you define a new virtual host
- Add the following entries to your */etc/hosts* file
- Create a virtual host like below. You can add this to /etc/apache2/sites-available/default-ssl.conf file
- Restart Apache HTTP server
BAM Configuration
- Uncomment and modify both HostName and MgtHostName in $BAM_HOME/repository/carbon.xml
- Uncomment and modify ProxyContextPath in $BAM_HOME/repository/carbon.xml
Now you should be able access the BAM using following URLs
Management console - https://bamproxy.example.com/bamcarbon
Message console - https://bamproxy.example.com/messageconsole
Activity monitoring - https://bamproxy.example.com/activitymonitoring
BAM dashboards - https://bamproxy.example.com/bamdashboards
