WHile testing a connection of USS its failing. Although i m login with CASMAdmin account but keeps failing to integrate with sdm.
# Have you checked if SDM webservice URL is working.. You can validate it by running this url from USS server.http://<servername>:8080/axis/services/USD_R11_Webservice?WSDL # Check if the webservice policy is pointing to correct contact SDM UI -> administration tab->SOAP Webservice policy ->policies->DEFAULT-> " Set the proxy contact " to Servicedesk user.
Also check if CASM policy has proper proxy contact.
As the error states "Please make sure the credentials are right".
Can you please check if you have CASMAdmin user in SDM?
Then try to cross verify with the following screenshot for all the fields:
I have CASMAdmin in sdm and i also can login with that account in sdm as well as in uss. But while test connection in data source its failing.
Check if you can find any errors in the liferay logs of USS.
Logs can be found at the following location:
E.g. C:\Program Files\CA\Self Service\OSOP\logs
Hi Junaid i checked the logs. But there is nothing like any credentials error.
let me explain little about my environment
we have sdm with high availability. And configured USS on all the server BG, Standby and Application
Try to bump up the logging to debug here;
USS Log levels can be increased on a specific class via http://server:8686/group/control_panel if needed. (via control panel URL in the left bottom pane: Server --> Server Administration --> Log Levels tab, Update Categories) --> the first five there (com.ca.**) can all be set to ALL. Hit save towards the bottom of the page and reproduce the issue again.
Now liferay logs should have some clues. Associated SDM logs (stdlogs) should have some clues too.
Did you get a chance to increase the USS logging level as suggested by Raghu.Rudraraju and retry the integration.And noted any sort of errror messages in either liferay logs or stdlogs.
When authenticating to web services the integration isn't testing using the CASMAdmin user you are logged into USS with, it's testing with the policy file. Have you attempted to generate a new policy P12 from the application server and using that?
if webservice url is not working. How can we enable it then?
uss auto integration is failing with eem and sdm 17.0. checked the osop logs. not reaching to webservice url. also in casm policy. there is already proxy contact available casmadmin. please advise
19:49:05,524 INFO [SessionImpl:204] Requester UserID of: 10196 Screen name: casmadmin19:49:05,551 WARN [ExternalSourceData:313] Error reaching the Data Source End Point URI.java.io.FileNotFoundException: http://abp-sdm-app:80/axis/services/USD_R11_WebService?wsdl at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1624)
Web services is deployed by default on any non-Background server. Are you certain that Tomcat is running on port 8080?
THanks for you input ALexender
does the following output show webservice enable? the screenshot below is one of my another environment on which uss is integrated with sdm n eem.
But in the other environment, i could able to see this output by putting wsdl url.
Yes i Believe the tomcat is running 8080. how to more confirm it?
The page in the screenshot you provided shows the wsdl working. Can you configure USS to point to this server?
No i cant configure uss to this environment. this environment already has uss running.
i still not able to to integrate.. just increase log level and reproduced the error.. in osop log.it also showing
moreover, can u tell me table name in USS db in which eem hostname save?
10,765 TRACE [EEMAutoLogin:232] Auto Login initiated...11:56:11,452 TRACE [EiamNtlmFilter:232] EIAM NTLM Filter Started. Company ID1015411:56:11,453 TRACE [EiamNtlmFilter:232] EEM or NTLM is not enabled. Hence returning from the EiamNtlmFilter 11:56:11,553 TRACE [EiamNtlmFilter:232] EIAM NTLM Filter Started. Company ID1015411:56:11,554 TRACE [EiamNtlmFilter:232] EEM or NTLM is not enabled. Hence returning from the EiamNtlmFilter
Thank you for that information.
1. To confirm the port that Tomcat is using, review the pdm_tomcat.log file and find a line like:
INFO: Starting ProtocolHandler [http-nio-8080]
after "http-nio" it will list the port in use. It is possible for multiple ports to be used by Tomcat. If you see any errors regarding the port those will need to be addressed.
2. USS stores the EEM host name information in the "PortalPreferences", most of the settings are stored in a single long string. In my system the information is stored in the "preferences" column for portalPreferencesID 10160. Make certain you make a backup prior to editing the database.
Thanks for you prompt response
i checked tomcat log. I guess no issue for webservice port. See below
More over... do u see any thing stang in the following value from my uss portal preference table?
You may also check this Technical document : https://www.ca.com/us/services-support/ca-support/ca-support-online/knowledge-base-articles.tec618553.html
This Thread will be of good help : https://communities.ca.com/thread/241739999
Thanks for all the help
My issue has been resolved now.
Retrieving data ...