URGENT: Error while deploying ear with weblogic service control

Question

We have build an ear within workshop and deployed to another server. When accessing the application we are getting the following error:
'com.bea.control.ServiceControlException: Could not find service ref in jndi: java:comp/env/service/hhs_wc_controls_SearchServiceControl[javax.naming.NameNotFoundException: While trying to look up comp/env/service/hhs_wc_controls_SearchServiceControl in /app/webapp/WCWeb/5120123.; remaining name 'comp/env/service/hhs_wc_controls_SearchServiceControl'] '
The service control is connecting a WSDL to consume a web service.
Does the service control create a JNDI entry or some file is not getting built into the ear?
We are using WLP 10.3
Your help is much appreciated.
Thanks,
- Shankar
Edited by: user1269940 on Nov 6, 2009 12:39 PM

Answer 1

Hi Shankar
When a WebService Control is created based on .wsdl file, it generates a .JAR file with all jaxb generated classes and .java files with service and port classes. This .jar file will be under web-inf/lib folder. Then I guess you are using this WebService control in your Pageflow and invoke webservice operations. So do you have like a portlet for this pageflow and testing from a portal. I have a similar scenario but I did not get any error that you are seeing. I consume SOA BPEL webservices in one of my pageflows using Service Controls.
To debug, first test if the wsdl is working by directly invoking the wsdl operations using a utility servlet by name "wls_utc" which you can invoke from any of your wls/wlp domain. Start your domain assuming localhost and port is 7001. The url for testing webservices is:
http://localhost:7001/wls_utc. This works if domain is in Dev Mode only. This page opens a jsp page, where you can type your wsdl url (http://host:port/context/a/b/xyx?wsdl). This page parses that wsdl and shows all operations and for each operation the fields for input parameters. See if this wsdl works fine.
As for deployment, there is no additional step required. Just ear your application that has .war file and that has web-inf/lib folder with actual webservice control generate .jar file. I did no tconfigure any additional JNDI lookups like that.
Thanks
Ravi Jegga