Hi Everyone
I have been really busy with my last assignment and couldn't post any blogs off-late.
But, now when I have gotten some time, thought of sharing one of the issues in this post as it is related to missing configuration and difficult to figure out with.
I faced this issue wherein the emails were being sent to few users and not to all users configured with Active Directory. It was observed that the section containing default email address i.e. Messaging Channel under Preferences in the Oracle BPM worklist was missing for these users.
When I looked in the database, Table : USER_DEVICE and DEVICE_ADDRESS under ORASDPM schema, it had only few entries of some users and not for all.
These entries are created by default when a user logon to BPM worklist for the first time.
After researching on the same, I found out that the issue was with the way AD Authenticator was configured. Weblogic was not able to communicate properly with AD Server because of the missing configuration and the issue was being faced at OPSS layer. Hence , the messaging channel preferences were not being populated by default.
To fix the same, perform the following steps :
1) Take a backup of config.xml and jps-config.xml
2) Add a new ADAuthenticator under Providers to configure weblogic with your Active Directory . Let's call it as YourAD
3) Set the Control Flag as "SUFFICIENT" and re-order the Provider to bring the ADAuthenticator(YourAD)at the top
4) Make sure that before re-ordering, the Control Flag for DefaultAuthenticator is also set as "SUFFICIENT"
4) Restart the Weblogic and other managed servers to make sure servers come up fine.
5) This will add an entry of the ADAuthenticator(YourAD) in the jps-config.xml
6) Take a backup of config.xml and jps-config.xml again after it has been configured
7) Open jps-config.xml file in word editor and search for following :
8) Replace the same with following :I have been really busy with my last assignment and couldn't post any blogs off-late.
But, now when I have gotten some time, thought of sharing one of the issues in this post as it is related to missing configuration and difficult to figure out with.
I faced this issue wherein the emails were being sent to few users and not to all users configured with Active Directory. It was observed that the section containing default email address i.e. Messaging Channel under Preferences in the Oracle BPM worklist was missing for these users.
When I looked in the database, Table : USER_DEVICE and DEVICE_ADDRESS under ORASDPM schema, it had only few entries of some users and not for all.
These entries are created by default when a user logon to BPM worklist for the first time.
After researching on the same, I found out that the issue was with the way AD Authenticator was configured. Weblogic was not able to communicate properly with AD Server because of the missing configuration and the issue was being faced at OPSS layer. Hence , the messaging channel preferences were not being populated by default.
To fix the same, perform the following steps :
1) Take a backup of config.xml and jps-config.xml
2) Add a new ADAuthenticator under Providers to configure weblogic with your Active Directory . Let's call it as YourAD
3) Set the Control Flag as "SUFFICIENT" and re-order the Provider to bring the ADAuthenticator(YourAD)at the top
4) Make sure that before re-ordering, the Control Flag for DefaultAuthenticator is also set as "SUFFICIENT"
4) Restart the Weblogic and other managed servers to make sure servers come up fine.
5) This will add an entry of the ADAuthenticator(YourAD) in the jps-config.xml
6) Take a backup of config.xml and jps-config.xml again after it has been configured
7) Open jps-config.xml file in word editor and search for following :
where YourAD is the name of your ADAuthenticator in weblogic under Providers
9) Restart Managed and weblogic server
10) Ask the users to logon to BPM worklist and the messaging channel would be populated by default.
Note* The backups are taken to revert to the old configuration if servers don't come up after integration.
I hope this post will be useful in case anyone encounters a similar issue with Messaging Channel. Trust me, no client would like to manually populate this piece of information manually as it is a major inconvenience to the Business Users.
Keep following.. I will be coming up with new posts soon!!!