Overview
A user may experience issues with the Business Support System (BSS) service for Live Bill, which may manifest as the service being unresponsive or not functioning as expected. This problem typically requires a service restart to resolve.
Solution
To address the issue with the BSS service for Live Bill, a service restart is necessary. This action can be performed by L2 team upon request. Follow the steps below:
Prerequisites
Ensure you have the necessary credentials and access to the server and JBoss services.
Procedure
Step 1: Login and Check User
- Log into the respective server with the
crestel
user:su - crestel
- Verify the logged-in user:
id
Step 2: Navigate to JBOSS Directory
- Change directory to JBOSS home:
cd /opt/crestelsetup/CRESTEL-JBoss-6.1.0.Final/bin/
- Check running services:
jps -m
Step 3: Stop JBoss Services
Execute the following commands one by one, waiting for each to complete:
- Stop Billing BSS:
sh killBillingBss.sh
- Stop Billing Engine:
sh killBillingEngine.sh
- Stop Provisioning:
sh killProvisioning.sh
Step 4: Clean JBoss System
Run the following cleaning scripts:
- Clean Billing BSS:
sh cleanBillingBss.sh
- Clean Billing Engine:
sh cleanBillingEngine.sh
- Clean Provisioning:
sh cleanProvisioning.sh
Step 5: Restart JBoss Services
Allow a few minutes for JBoss to gracefully drop connections, then start the services using the commands below and monitor the logs. Press Ctrl + C
when “Started in” is displayed on the screen.
- Start Provisioning:
sh startupProvisioning.sh ; tail -f ../server/provisioning/log/jboss.log | grep 'Started in'
Logs path:/opt/crestelsetup/CRESTEL-JBoss-6.1.0.Final/server/provisioning/log
- Start Billing Engine:
sh startupBillingEngine.sh ; tail -f ../server/billingengine/log/jboss.log | grep 'Started in'
Logs path:/opt/crestelsetup/CRESTEL-JBoss-6.1.0.Final/server/billingengine/log
- Start Billing BSS:
sh startupBillingBss.sh ; tail -f ../server/billingbss/log/jboss.log | grep 'Started in'
Logs path:/opt/crestelsetup/CRESTEL-JBoss-6.1.0.Final/server/billingbss/log
Step 6: Reload Cache
After restarting, reload the cache for PM, RM, and OM:
- For Product Manager, access
http://5bb.bss.com:9080/Login.zul
then go toSystem Configuration -> Reload Cache
- For Rating Manager, navigate to
Utilities -> Reload Rating Cache -> Select All Instance -> Click Reload
- For Operation Manager, go to
System -> Server Administrator -> Web Cache Manager -> Reload All
Notes
- Ensure that each step is completed successfully before proceeding to the next.
- Monitor the logs for any errors or warnings.
Comments
0 comments
Please sign in to leave a comment.