(SM) Support Tip : How to handle more request’s coming from OMi
Configure multiple queue in SM - BSM
To create multiple “connected servers” in SM please follow the below steps:
1. First create multiple entries in the HOSTS file pointing same IP (SM server) as below:
For example: 10.80.12.15 is the SM server IP
10.80.12.15 group1 group2 group3
10.80.12.15 group4 group5
Now when we ping group1 it will reach SM server 10.80.12.15
This needs to be updated in the HOST file on all GW and DPS servers environment and the SM server as well.
2. Open 5 ports on the SM side to be able to use them in “connected server” configuration.
This will make sure that traffic will be diverted through 5 ports.
a. Example of sm.cfg file :
sm -httpPort:13081 -debugnode:1 -log:../logs/SMOMiIntegration13081.log
sm -httpPort:13082 -debugnode:1 -log:../logs/SMOMiIntegration13082.log
sm -httpPort:13083 -debugnode:1 -log:../logs/SMOMiIntegration13083.log
sm -httpPort:13084 -debugnode:1 -log:../logs/SMOMiIntegration13084.log
sm -httpPort:13085 -debugnode:1 -log:../logs/SMOMiIntegration13085.log
b. Now we can create 5 “connected servers” in Omi using each of the five hostnames mentioned above
- Use the integration name as group_1 (just to know that it contains host name as group1)
- Use FQDN is SM server as group1
- Then use one of the 5 ports which is configured for this first configuration
- For “Incoming properties” only 1 of these five connections will be used in SMOMI (SM Integration Manager) for backsync to Omi. Therefore we can populate this for only 1 of the 5 connections.
- Similarly repeat the steps for the other four connections.
3. After that we could configure forwarding rules based on groups.
We can divide all events into say 5 groups. Some commonly used groups are:
- All Major events
- All Minor events
The above are just examples, However this depends on the actual requirement as to how one would like to divide event traffic.
Create 5 events filters and use them to create 5 Forwarding rules.
And that should be it!!