Services Registry for WSDL created in SAP XI3.0

Hi,
I know that there was a services registry in PI7.1 but is that any services registry in XI3.0 in order for me to public my created WSDL file to third party developer?
Thanks

Hi,
>>but is that any services registry in XI3.0 in order for me to public my created WSDL file to third party developer?
There is no service registry but you can publish your wsdl in uddi server. Check these blogs
/people/sap.user72/blog/2005/11/16/webas-a-step-by-step-guide-for-configuring-uddi-registry-on-local-server
/people/sap.user72/blog/2005/11/17/xi-how-to-publish-wsdl-generated-from-xi-to-uddi
Regards
Suraj

Similar Messages

  • Exception on creation of service metadata for WSDL URL

    Hi expert,
    im consuming a wsdl file in my wdj dc , and on trying to execute im getting exception as follows .
    WsdlApp--com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL 'E:\***********\MIOS_*********_********.wsdl' and service factory configuration 'null'
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:422)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:326)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo$Cache.getModelInfo(WSModelInfo.java:199)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:1035)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:248)
    at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:41)
    at com.*****.wsdlwdj.batch.****************Batch.<init>(******************Batch.java:51)
    at com.*****.wsdlwdj.comp.*************Component.test**********Auth(************Component.java:266)
    at com.*****.wsdlwdj.comp.wdp.Internal****Component.test****Auth(Internal********Component.java:331)
    at com.*****.wsdlwdj.comp.WsdlView.wdDoInit(WsdlView.java:97)
    at com.*****.wsdlwdj.comp.wdp.InternalWsdlView.wdDoInit(InternalWsdlView.java:129)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
    at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
    at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
    at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:182)
    at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:177)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
    at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.setSpnegoParameter(RequestManager.java:963)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:157)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1064)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details.
    at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:158)
    at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:56)
    at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:92)
    at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:114)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:420)
    ... 55 more
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Problem with WSDL file parsing. See nested message.
    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:182)
    at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:155)
    ... 59 more
    Caused by: com.sap.engine.lib.xml.util.NestedException: IO Exception occurred while parsing file:/usr/sap/*****/JC**/j2ee/cluster/server1/E:/****/FolderName/WSDLNAME.wsdl (No such file or directory) -> java.io.FileNotFoundException: /usr/sap/***/JC**/j2ee/cluster/server1/E:/WSDL FILE/FolderName/wsdlname.wsdl (No such file or directory)
    at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1039)
    at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadWSDLDocument(WSDLDOMLoader.java:1126)
    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:178)
    ... 60 more
    Caused by: java.io.FileNotFoundException: /usr/sap/***/JC**/j2ee/cluster/server1/E:/WSDL FILE/FolderName/wsdlname.wsdl (No such file or directory)
    at java.io.FileInputStream.open(Native Method)
    at java.io.FileInputStream.<init>(FileInputStream.java:106)
    at java.io.FileInputStream.<init>(FileInputStream.java:66)
    at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:69)
    at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:156)
    at java.net.URL.openStream(URL.java:913)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:201)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:263)
    at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:260)
    at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:271)
    at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
    at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
    at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1023)
    ... 62 more
    Regards
    Govardan

    im using 7.01 and here we have options to use No Logical Destinations , but now i created destinations at visual admin at Server>Services>Web Service Security>WebService Clients>Sap.com-->Dynamic WS Proxies., as WS_METADATA_DEST and WS_MODELDATA_DEST     and have filled in other details too like url  , user name , password etc
    now im getting another error like as shown below please help
    com.****.wsdlwdj.applicaiton.WsdlApp
    [EXCEPTION]
    com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WS metadata destination 'WS_METADATA_DEST' and WS interface '{http://****.com/****}MIOS_Matrix***********'. One possible reason is that the metadata destination 'WS_METADATA_DEST' has not been properly configured; check configuration.
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:440)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:326)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo$Cache.getModelInfo(WSModelInfo.java:199)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:1035)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:248)
    at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:41)
    at com.****.wsdlwdj.model.test.TestModel.<init>(TestModel.java:51)
    at com.****.wsdlwdj.comp.VcWsdlComponent.matrixAuthExecut(VcWsdlComponent.java:448)
    at com.****.wsdlwdj.comp.wdp.InternalVcWsdlComponent.matrixAuthExecut(InternalVcWsdlComponent.java:280)
    at com.****.wsdlwdj.comp.VcWsdlComponent.wdDoInit(VcWsdlComponent.java:132)
    at com.****.wsdlwdj.comp.wdp.InternalVcWsdlComponent.wdDoInit(InternalVcWsdlComponent.java:225)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
    at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.setSpnegoParameter(RequestManager.java:963)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:157)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1064)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by: com.sap.engine.services.webservices.espbase.discovery.BaseIOException: Invalid Response Code 500 while accessing URL: http://devpid:8000/sap/xi/engine?type=entry&version=3.0&Sender.Service=BS_****_PORTAL&Interface=http%3A%2F%2F****.com%2Fbank_report%5EMIOS_Authorizers_List_Portal&sap-user=xi_portal&sap-password=****1234. Response Message: Empty HTTP request received. Content Type: text/xml. Body Content: <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP:Header>
    </SOAP:Header>
    <SOAP:Body>
    <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Empty HTTP request received</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIProtocol</SAP:Category><SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code><SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Empty HTTP query received; message processing not possible
    </SAP:Stack></SAP:Error></detail></SOAP:Fault>
    </SOAP:Body>
    </SOAP:Envelope>
    at com.sap.engine.services.webservices.server.management.discovery.DestinationsResolver.resolveURL(DestinationsResolver.java:246)
    at com.sap.engine.services.webservices.server.management.discovery.DestinationsResolver.resolveEntity(DestinationsResolver.java:130)
    at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.initialize(WSQueryImpl.java:184)
    at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.findWSInterfaces(WSQueryImpl.java:151)
    at com.sap.engine.services.webservices.server.management.discovery.ServiceDiscoveryImpl.getWSDLUrl(ServiceDiscoveryImpl.java:71)
    at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:134)
    at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:429)
    ... 49 more

  • Exception on creation of service metadata for WSDL

    trying to access webservice (generated on Oracle applic. Server)  as Adaptive WebServiceModel i get the following error:
    Exception on creation of service metadata for WSDL
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory
    Initialization problem. Could not load web service model. See nested exception for details.
         at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:150)
         at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:50)
         at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:88)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:412)
         ... 53 more
    Caused by: java.lang.UnsupportedOperationException: Type {http://schemas.xmlsoap.org/soap/encoding/}Array is not supported!
         at com.sap.engine.services.webservices.espbase.client.dynamic.types.impl.MetadataLoader.loadMetadata(MetadataLoader.java:129)
    So, the code in WSDL is like:
    targetNamespace="http://com.rwe.lis.webservices/IWSFidLis.xsd"
             xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns="http://www.w3.org/2001/XMLSchema">
    <complexType name="ArrayOfcom_rwe_lis_model_Flurstueck" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
                <complexContent>
                   <restriction base="SOAP-ENC:Array">
                      <attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="ns1:com_rwe_lis_model_Flurstueck[]"/>
                   </restriction>
                </complexContent>
             </complexType>
    generated by JDeveloper on Ora Server.
    So - how to get access to this WebService?!?
    Bernhard

    Hi,
       The use of SOAP-ENC:Array is not supported in NW because it is not WS-I compliant. For a possible solution check [this|Re: unknown namespace error when generating a client proxy; link.
    Regards,
    Satyajit

  • OSR - Oracle Service Registry won't create database datasource

    Current configuration:
    Oracle 10g database
    Oracle Service Registry 10gR3
    Oracle Weblogic application server 10.1.3
    I have tried many ways to install the registry (GUI, command prompt, config file) but my datasouce is not getting created. In the /log/install.log the flag to create the datasource is set to "yes" and the name is also set. I don't see any kind of msg/error in the install.log or in the weblogic log. One other thing the registry deploys just fine during installation so all the information seems to be ok. Since the datasource is not created, i get the following exception which is expected since there's no connection to the database:
    ERROR: account.com.systinet.uddi.account.database.DBAccountApiImpl - DatabaseCoreException: (12021) Cannot obtain new connection.
    ERROR: account.com.systinet.uddi.account.AccountCoreApiImpl - Initialization of accounts has failed in the database. Database is not running.
    ERROR: group.com.systinet.uddi.group.database.DBGroupApiImpl - DatabaseCoreException: (12021) Cannot obtain new connection.
    ERROR: group_core.com.systinet.uddi.group.GroupCoreApiImpl - Initialization of groups has failed in the database. The database is not running.
    The only way to make it work is to create the datasouce manually. In the environment that I'm running the less steps the better.
    So thank you for any ideas/help that you can give me!

    Oracle Service Registry Installation to Weblogic
    1. Run installation
    java -jar oracle-service-regisry-10.3.jar
    2. In the Oracle Service Registry installer proceed through the following screens
    * Installation Type screen: select 'Standalone' or other type of installation
    * Installation Directory screen: enter folder where OSR will be installed i.e:-
    /home/oracle/OSR/osrregistry_10_1_3
    * SMTP Configuration screen: (optional) accept defaults
    * Administrator Account Configuration screen: admin user account details
    * Database Setup screen: create new New Schema / Database or connect to existing schema
    * Database Selection screen: select Oracle or other database you may be using
    * Oracle screen: enter database details and schema information.
    3. Data Source screen: IGNORE this for Weblogic servers. Only affects Oracle Application Servers.
    4. JDBC Driver Selection screen: search and select JDBC driver i.e. JDBC 1.6 for Weblogic:-
    $WEBLOGIC_HOME/wlserver_10.3/server/ext/jdbc/oracle/11g/ojdbc6.jar
    5. Account Provide Selection screen: select 'Database'.
    6. Application Server Selection screen: MUST SELECT 'Oracle Weblogic 9.2 or 10.3'
    7. Deployment to Oracle Weblogic Application Server screen: enter correct Weblogic details such as:-
    * Weblogic HTTP Port: AdminServer port i.e. 7001 or a managed server port i.e. 7003
    * SSL Ports (optional): i.e. 7002
    * Hostname where WLS resides.
    * Application Server Context (name of application).
    8. Also on this screen there is the option "Deploy at the end of the installation" which will either deploy the OSR application to Weblogic after it is installed (selected option) or just deploy a WAR file to the command line and get deployed to Weblogic at a later stage (de-select option).
    9. Deployment Details screen: If selected Deploy at the end of the installation in the above screen, then the following screen will be displayed which allows you to enter details of where to deploy the application in Weblogic. Enter all relevant details:
    * Weblogic home: enter the folder where Weblogic resides (WebLogic server installation directory) i.e.
    $WEBLOGIC_HOME/wls_servber1013
    $WEBLOGIC_HOME/weblogic92
    * Java Home: enter the path of the JDK i.e.
    $WEBLOGIC_HOME/jdk160_05
    * Hostname: host of where to deploy application.
    * Admin Username | Password: admin details for weblogic server.
    10. The summary screen is shown regardless of if deployed to Weblogic or not. Press [Next] to install OSR.
    11. After successfully installing OSR a screen will detail that the installation has been successfully installed and with what tasks that need to be completed.
    Deploy OSR to Weblogic
    1. If in the installer the Deploy at the end of the installation option was not selected, then the OSR application needs to be deployed via the Weblogic console. So log into the Weblogic console, press Deployments and then Install.
    2. Install Application Assistant screen:
    * Enter the path where the OSR deployment WAR file (registry.war) resides. It is found in the following path:
    $OSR_HOME/conf/porting/weblogic/build
    * Select file file registry.war.
    3. Complete the rest of the installation/deployment whilst selecting a target server.
    POST INSTALLATION
    The following MUST be done to be able to log into the Oracle Service Registry consoles.
    1. Edit the following Weblogic file:-
    Linux
    $WEBLOGIC_HOME/user_projects/domains/<domain_name>/bin/startWebLogic.sh
    Windows
    %WEBLOGIC_HOME%/user_projects/domains/<domain_name>/bin/startWebLogic.cmd
    2. Modify the following line
    JAVA_OPTIONS="${SAVE_JAVA_OPTIONS}"
    to
    Linux
    JAVA_OPTIONS="${SAVE_JAVA_OPTIONS} -Djava.security.auth.login.config=$OSR_HOME/conf/jaas.config"
    Windows
    set JAVA_OPTIONS=%SAVE_JAVA_OPTIONS% -Djava.security.auth.login.config=%OSR_HOME%\conf\jaas.config
    OSR Console
    1. Go to the Oracle Service Registry on Weblogic
    Service Registry
    http://<host>:<port>/registry/uddi/web
    Business Service Registy
    http://<host>:<port>/registry/uddi/web
    2. Press Login and enter login credentials and should be able to successfully login.

  • Multi Language support for universes created on SAP BW/BI

    Dear Gurus,
    When I am going through the document "using SAP BW in Designing OLAP universes"
    http://help.sap.com/businessobject/product_guides/boexir31/en/xi3-1_sap_olap_universes_en.pdf
    in 13 th page under the heading "SAP BW Multilingual universes" I found the below statements.
    "With Web Intelligence, it is possible to leverage the multilingual capabilities
    of SAP BW. In order to implement a multilingual environment, the BW system
    must include multilingual metadata and multilingual data.
    You must create a universe for each language supported by the solution.
    The language in which the universe connection is created determines the
    language in which the universe is generated.
    The user's SAP authentication determines the language of the data returned
    to the query. The user must log into InfoView using SAP authentication and
    specify the desired language for results returned from the SAP server.
    The result-set language is dependent on SAPu2019s Unicode support. If the SAP
    system does not contain the data in the desired language, the data is not
    available in Web Intelligence in this language. Web Intelligence reverts to
    displaying technical names instead of descriptions when the descriptions
    are not translated in SAP BW."
    After reading the above statements i got the impression that if i want to see the report in 10 languages then i need to create the universe in each language with seperate connection in each language.
    if my understanding is correct. it araises below questions.
    1. if i am creating one universe for each language will it not increase maintainance?
    2. or is there any option available in universe designer which takes the replica of the universe into the desired language?
    Please clarify me the above doubts.
    Many thanks in Advance
    Jagadeesh Ambati

    Hi,
    when you read it you will recognize it does make a difference between the actual data that you retrieve and the meta-data being retrieved from BW.
    Meta-Data:
    >>The language in which the universe connection is created determines the
    >>language in which the universe is generated
    Data:
    The user's SAP authentication determines the language of the data returned
    to the query. The user must log into InfoView using SAP authentication and
    specify the desired language for results returned from the SAP server.
    The result-set language is dependent on SAPu2019s Unicode support. If the SAP
    system does not contain the data in the desired language, the data is not
    available in Web Intelligence in this language
    The user can set a Preferred Viewing language in the Preferences in InfoView.
    Ingo

  • Generate Service Control for WSDL: NullPointerException

    Steps to demonstrate the problem: in Platform Workshop (8.1.4) in Integration mode, create a Tutorial Process Application, then for RequestQuote.jpd, Generate WSDL file, then for that WSDL, Generate Service Control.
    <pre>ERROR: requestquote/RequestQuoteContract.wsdl Line 0, Col 0: java.lang.NullPointerException
    </pre>
    The WSDL is valid (Axis WSDL2Java and Eclipse-Webtools are both okay with it, assuming I delete some cw and http namespaces they don't understand).
    The problem is when the XSD is too deeply nested giving XML like /one/two/three, whereas /one/two is okay for WLI. This is valid XSD, but apparently too deep for WLI to understand.
    Any help debugging this more or working around it would be appreciated. Is there a way to run this process from the command line, so I might debug this more on my own? I'd like to give the stackTrace for the NPE, but WLI Workshop doesn't show that.
    Thanks,
    Mike

    Hi guys,
    I had the same problem and what I had to do was import the Schema project that holds all schemas included in the WSDL that I was trying to generate a control from. In my case I had the Schema project because I was the one that developed the WebService too, in your case it's possible that you have to create an Schema project and somehow extract the schemas from de WSDL and create .xsd files to put in the project.
    After doing this you will see the popup window (when you try to generate a service control from the WSDL file) asking if you want to use the XMLBeans generated from the xsd files in your Schema project otherwise it will generate inner classes based in the WSDL's schemas, you must choose YES (use the existing XMLBeans) and that should be it for creating a Service Control based on a WSDL file.
    Hope this helps in most cases.
    Regards,
    Israel Williams
    Software Architect
    JWM Solutions
    [email protected]

  • Shared Services Framework for HR - Integration with SAP ERP - SAP Library

    To add a comment, please log in or register on the top of this page and choose Reply. Please write your comment in English.
    You can also go back to the SAP help page.

    Is there any training for the SAP HR SSF in SAP Education in London for July/Aug 2014

  • Create adaptive web service model for a web dynpro project

    I have been trying to create a new new adaptive web service model for a web dynpro project.I am using the URL of the wsdl file to create the model. I have copied the url link of the wsdl from the overview tab of the web services navigator. The web service works fine when tested through the Netweaver Navigator. This web service has also been used successfully through the Visual Composer. But when I try to create a model for this web service URL, when I click the Next button after entering the URL in the model creation wizard  step 4 , I get "Error loading wsdl file. Check error log for details" Given below is the exception recorded in the error log: (Infact, I get this for all wsdl URLs)
    !MESSAGE Jun 6, 2007 9:44:59 AM           com.sap.ide.webdynpro.ui.service.ServicesUI          [Thread[main,5,main]] Error: Internal error
       Plugin name: Web Dynpro Model Editor
       Plugin ID  : com.sap.ide.webdynpro.modeleditor
       Class      : com.sap.ide.webdynpro.modeleditor.wizards.model.creation.PageRenameWS
       Method     : loadNameSpacesAndModelClasses
       Message    : Cannot load NameSpaces and ModelClasses
    Class Path: C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi_1.0.0/_cmi_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.exception_2.0.0/lib/exception.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/boot.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/iq-lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/util.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/tc_sec_wssec_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.runtime_2.0.0/lib/SapDictionaryTypesRuntime.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.services_2.0.0/lib/SapDictionaryTypeServices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/logging.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/loggingStandard.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/jARM.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0/lib/sapxmltoolkit.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/activation.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxm-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/saaj-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxrpc-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jnet.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jsse.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/mail.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.webdynpro.model.webservice_2.0.0/lib/_webdynpro_model_webservice.jar;
    java.home: C:\java\j2sdk1.4.2_09
    proxyHost:
    proxyPort:
    nonProxyHosts:
    Temporary Directory: C:\DOCUME1\E51914\LOCALS1\Temp\
    WSDL URL: http://etcvpcod108:50100/UserService/Config5?wsdl
       Exception  : com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL http://etcvpcod108:50100/UserService/Config5?wsdl and service factory configuration {DynamicProxy.ClassPath=C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi_1.0.0/_cmi_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.exception_2.0.0/lib/exception.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/boot.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/iq-lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/util.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/tc_sec_wssec_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.runtime_2.0.0/lib/SapDictionaryTypesRuntime.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.services_2.0.0/lib/SapDictionaryTypeServices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/logging.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/loggingStandard.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/jARM.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0/lib/sapxmltoolkit.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/activation.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxm-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/saaj-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxrpc-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jnet.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jsse.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/mail.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.webdynpro.model.webservice_2.0.0/lib/_webdynpro_model_webservice.jar;, DynamicProxy.INetProxy.Bypass=, DynamicProxy.INetProxy.Port=, DynamicProxy.Javac.path=C:\java\j2sdk1.4.2_09, DynamicProxy.TempDir=C:\DOCUME1\E51914\LOCALS1\Temp\, DynamicProxy.INetProxy.Host=}
    !STACK 0
    com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL 'http://etcvpcod108:50100/UserService/Config5?wsdl' and service factory configuration '{DynamicProxy.ClassPath=C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi_1.0.0/_cmi_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.exception_2.0.0/lib/exception.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/boot.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/iq-lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/util.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/tc_sec_wssec_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.runtime_2.0.0/lib/SapDictionaryTypesRuntime.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.services_2.0.0/lib/SapDictionaryTypeServices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/logging.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/loggingStandard.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/jARM.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0/lib/sapxmltoolkit.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/activation.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxm-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/saaj-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxrpc-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jnet.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jsse.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/mail.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.webdynpro.model.webservice_2.0.0/lib/_webdynpro_model_webservice.jar;, DynamicProxy.INetProxy.Bypass=, DynamicProxy.INetProxy.Port=, DynamicProxy.Javac.path=C:\java\j2sdk1.4.2_09, DynamicProxy.TempDir=C:\DOCUME1\E51914\LOCALS1\Temp\, DynamicProxy.INetProxy.Host=}'
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:413)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:371)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:341)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:305)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:315)
         at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.PageRenameWS.loadNameSpacesAndModelClasses(PageRenameWS.java:435)
         at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelDialog.nextPressed(ModelDialog.java:105)
         at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:316)
         at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
         at org.eclipse.jface.window.Window.open(Window.java:563)
         at com.sap.ide.webdynpro.modeleditor.ModelEditorCallback.createModel(ModelEditorCallback.java:52)
         at com.sap.ide.webdynpro.service.modeleditor.ModelService.createModelWithUI(ModelService.java:70)
         at com.sap.ide.webdynpro.service.modeleditor.ServiceWithUI.createModel(ServiceWithUI.java:49)
         at com.sap.ide.webdynpro.tsmodel.application.provider.ModelNodeProvider.createUniqueName(ModelNodeProvider.java:55)
         at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntityUin(EntityImpl.java:936)
         at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntity(EntityImpl.java:502)
         at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.runInternal(CreationAction.java:76)
         at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.access$000(CreationAction.java:24)
         at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction$1.run(CreationAction.java:51)
         at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
         at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.run(CreationAction.java:57)
         at com.sap.ide.webdynpro.projectbrowser.actions.PBCreateModelAction.run(PBCreateModelAction.java:95)
         at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:224)
         at com.tssap.util.ui.menu.MenuFactory$MuSiAction.saveRunAction(MenuFactory.java:1425)
         at com.tssap.util.ui.menu.MenuFactory$MuSiAction.run(MenuFactory.java:1407)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:616)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:586)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:716)
         at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:610)
         at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
         at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
         at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
         at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
         at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
         at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
         at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details.
         at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:149)
         at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:49)
         at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:71)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:411)
         ... 53 more

    Hi Srikanth,
    My version was
    Version: 7.0.09
    Build id: 200608262203
    I was able to successfully import the model after I did the following
    1. Re intsall Studion (same version , same build)
    2. Reset the proxy settings to not use Proxy server
    Thanks for looking into it though...
    -Lakshmi

  • Regarding  the Service Registry in SAP  PI 7.1 and non SAP System ....!

    Hi All ,
    I  need to know answers for the below Question ...hope to get some answers frm Experts ....
    1) How to publish service from non-SAP systems?
    2)  How to use discovered service in the Service Registry for consumer/provider scenario? With some examples.
    Thanks in Advace ...!
    Regards ,
    Aziz khan .
    Edited by: Aziz khan on Sep 16, 2009 11:43 AM

    Hi,
    1) How to publish service from non-SAP systems?
    Publish Service is nothing but making WSDL of that service available. For that you need to Publish the WSDL of the web Service to UDDI. For Non SAP system, Lik .net , Java they have there oun APIs to do so. U can search on net to get it.
    For Ex. below link.
    http://www.startvbdotnet.com/web/publish.aspx
    2) How to use discovered service in the Service Registry for consumer/provider scenario? With some examples.
    Once you discover the services, you get the WSDL of that Service. Then You can import this WSDL in IR and you it.
    See the below links.
    http://help.sap.com/saphelp_nw04/helpdata/en/43/ce993b45cb0a85e10000000a1553f6/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/EN/26/9e97b0f525d743882936c2d6f375c7/frameset.htm
    Shweta

  • Service Registry

    Hi all,
    1. How to create WSDL for existed BAPI , Function Modules in ECC 6.0
    2. how to assign the webservices to Service Registry either inbound, outbound in SAP PI 7.1  Please explain in Detail.
    3. how to develop the scenario Webservice to webservice using service registry in SAP PI 7.1 please expalin in Detail
    Thanks
    Anil

    >
    > 1. How to create WSDL for existed BAPI , Function Modules in ECC 6.0 .
    Import BAPI in to PI,there you can get WSDL for same BAPI,no need to create your self.
    > 2. how to assign the webservices to Service Registry either inbound, outbound in SAP PI 7.1  Please explain in Detail.
    You have to publish the web service in servicee registry,search in sdn you wil find how to publish and consume services in SR.
    > 3. how to develop the scenario Webservice to webservice using service registry in SAP PI 7.1 please expalin in Detail
    >
    Search in SDN ,in this case SR role is very minimal,using two SOAD Adapters we can develo web service to web service scenario using PI.
    rEGARDS,
    rAJ

  • Error publishing service in Service Registry

    Hi experts.
    I've configured Service Registry in a SAP PI 7.11. Everything seems to work correctly but I can't publish services there. When I try to publish from Directory or directly in Service Registry by wsdl I'm getting this error:
    com.sap.aii.ib.core.uddi.RegistryClientException: Services registry is not available; for more information, see the log
         at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:440)
         at com.sap.aii.ibdir.server.wsquery.WSQUDDIPSPublishTB.execute(WSQUDDIPSPublishTB.java:91)
         at com.sap.aii.ibdir.core.simulation.DefaultTaskBroker.execute(DefaultTaskBroker.java:171)
         at com.sap.aii.ibdir.server.simulation.TaskQueryService.specialQuery(TaskQueryService.java:33)
         at com.sap.aii.ib.server.query.SpecialQueryServiceProvider$SpecialQueryServiceImpl.specialQuery(SpecialQueryServiceProvider.java:63)
         at com.sap.aii.ib.server.query.QueryServiceImpl.specialQuery(QueryServiceImpl.java:443)
         at com.sap.aii.ib.server.query.QueryServiceBean.specialQuery(QueryServiceBean.java:112)
         at sun.reflect.GeneratedMethodAccessor762.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:592)
         at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
         at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
         at $Proxy1646.specialQuery(Unknown Source)
         at sun.reflect.GeneratedMethodAccessor761.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:592)
         at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:362)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:977)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)
    I think is a authorization problem but I have role to read and write in service registry. I can see this error in Service Registry Trace
    Invalid Response code (401). Server [http://xxxxxx:50000/uddi/api/publish/] returned message [Unauthorized].
    Any idea? Maybe the user you have to fill in Service Registry Configuration Wizard?
    Regards
    Edited by: Christian  Abad Chico on Feb 20, 2012 1:00 PM

    Hi,
    It looks like you are missing some Services Registry preconfiguration. Please find a description how to configure the Services Registry under the SAP Help document below:
    http://help.sap.com/saphelp_nwce711/helpdata/en/47/d391d7b8fc3c83e10000000a42189c/frameset.htm
    There is also a wizard that you can use for this purpose:
    http://help.sap.com/saphelp_nwce711/helpdata/en/f7/6182bd68434595ba5105a0a346efcc/frameset.htm
    Hope this helps,
    Greg

  • Export/Import classification categories/values in PI 7.11 Service Registry

    Hello,
    We are currently using SAP PI 7.11 EhP3.  I have created a number of custom classification entries in our PI Development environment's Service Registry, for use in classifying services within the Registry.  I need to apply the same categories and values into the Service Registry of our Quality and Production environments.  Is there any export/import capability enabling that capability in this version?
    Thanks,
    -- Chris

    Hello Gourav,
    Thank you for this information; it is very helpful.
    However - the export appears to only include the entries in the namespace http://uddi.sap.com/classification.  Since that is a protected namespace I am not able to create my custom classification values there.  (I'm also going to assume that this namespace gets overwritten during system upgrades, so I would not want my custom values in it anyway.)  Subsequently my custom values are in a separate namespace that does not seem to be included in the export process.
    Is there a way to configure this export utility so that it retrieves the data from my namespace, rather than (or in addition to) the standard SAP namespace?
    Thanks again,
    -- Chris

  • Web Service Error get wsdl via URL

    Hi,
    I try to import a Webservcie as new  Model (via URL), but I get everytime following error:
    Feb 28, 2007 10:55:59 AM com.sap.ide.webdynpro.ui.service.ServicesUI [Thread[main,5,main]] ERROR: Internal error
       Plugin name: Web Dynpro Model Editor
       Plugin ID  : com.sap.ide.webdynpro.modeleditor
       Class      : com.sap.ide.webdynpro.modeleditor.wizards.model.creation.PageRenameWS
       Method     : loadNameSpacesAndModelClasses
       Message    : Cannot load NameSpaces and ModelClasses
    Class Path: D:/SAP/JDT/eclipse/plugins/com.sap.tc.cmi/_cmi_api.jar;D:/SAP/JDT/eclipse/plugins/com.sap.exception/lib/exception.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/boot.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/iq-lib.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/util.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/webservices_lib.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/webservices.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/webservices_api.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/tc_sec_wssec_lib.jar;D:/SAP/JDT/eclipse/plugins/com.sap.dictionary.runtime/lib/SapDictionaryTypesRuntime.jar;D:/SAP/JDT/eclipse/plugins/com.sap.dictionary.services/lib/SapDictionaryTypeServices.jar;D:/SAP/JDT/eclipse/plugins/com.tssap.sap.libs.logging/lib/logging.jar;D:/SAP/JDT/eclipse/plugins/com.tssap.sap.libs.logging/lib/loggingStandard.jar;D:/SAP/JDT/eclipse/plugins/com.tssap.sap.libs.logging/lib/jARM.jar;D:/SAP/JDT/eclipse/plugins/com.tssap.sap.libs.xmltoolkit/lib/sapxmltoolkit.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/activation.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/jaxm-api.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/saaj-api.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/jaxrpc-api.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/jnet.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/jsse.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/mail.jar;D:/SAP/JDT/eclipse/plugins/com.sap.tc.webdynpro.model.webservice/lib/_webdynpro_model_webservice.jar;
    java.home: D:\j2sdk1.4.2_06
    proxyHost: http://webproxy.deutsche-boerse.de
    proxyPort: 8080
    nonProxyHosts: http://sapdephr.deutsche-boerse.de:50000|sapdephr.deutsche-boerse.de:50000|
    Temporary Directory: c:\temp\
    WSDL URL: http://sapdephr.deutsche-boerse.de:50000/WSCheckUser/Config1?wsdl
       Exception  : com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL http://sapdephr.deutsche-boerse.de:50000/WSCheckUser/Config1?wsdl  and service factory configuration {DynamicProxy.ClassPath=D:/SAP/JDT/eclipse/plugins/com.sap.tc.cmi/_cmi_api.jar;D:/SAP/JDT/eclipse/plugins/com.sap.exception/lib/exception.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/boot.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/iq-lib.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/util.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/webservices_lib.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/webservices.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/webservices_api.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/tc_sec_wssec_lib.jar;D:/SAP/JDT/eclipse/plugins/com.sap.dictionary.runtime/lib/SapDictionaryTypesRuntime.jar;D:/SAP/JDT/eclipse/plugins/com.sap.dictionary.services/lib/SapDictionaryTypeServices.jar;D:/SAP/JDT/eclipse/plugins/com.tssap.sap.libs.logging/lib/logging.jar;D:/SAP/JDT/eclipse/plugins/com.tssap.sap.libs.logging/lib/loggingStandard.jar;D:/SAP/JDT/eclipse/plugins/com.tssap.sap.libs.logging/lib/jARM.jar;D:/SAP/JDT/eclipse/plugins/com.tssap.sap.libs.xmltoolkit/lib/sapxmltoolkit.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/activation.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/jaxm-api.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/saaj-api.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/jaxrpc-api.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/jnet.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/jsse.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/mail.jar;D:/SAP/JDT/eclipse/plugins/com.sap.tc.webdynpro.model.webservice/lib/_webdynpro_model_webservice.jar;, DynamicProxy.HTTPPassword=, DynamicProxy.INetProxy.Bypass=http://sapdephr.deutsche-boerse.de:50000|sapdephr.deutsche-boerse.de:50000|, DynamicProxy.INetProxy.Port=8080, DynamicProxy.HTTPUserName=, DynamicProxy.Javac.path=D:\j2sdk1.4.2_06, DynamicProxy.TempDir=c:\temp\, DynamicProxy.INetProxy.Host=http://webproxy.deutsche-boerse.de}
    com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL 'http://sapdephr.deutsche-boerse.de:50000/WSCheckUser/Config1?wsdl ' and service factory configuration '{DynamicProxy.ClassPath=D:/SAP/JDT/eclipse/plugins/com.sap.tc.cmi/_cmi_api.jar;D:/SAP/JDT/eclipse/plugins/com.sap.exception/lib/exception.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/boot.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/iq-lib.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/util.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/webservices_lib.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/webservices.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/webservices_api.jar;D:/SAP/JDT/eclipse/plugins/com.sap.engine.webservices/lib/tc_sec_wssec_lib.jar;D:/SAP/JDT/eclipse/plugins/com.sap.dictionary.runtime/lib/SapDictionaryTypesRuntime.jar;D:/SAP/JDT/eclipse/plugins/com.sap.dictionary.services/lib/SapDictionaryTypeServices.jar;D:/SAP/JDT/eclipse/plugins/com.tssap.sap.libs.logging/lib/logging.jar;D:/SAP/JDT/eclipse/plugins/com.tssap.sap.libs.logging/lib/loggingStandard.jar;D:/SAP/JDT/eclipse/plugins/com.tssap.sap.libs.logging/lib/jARM.jar;D:/SAP/JDT/eclipse/plugins/com.tssap.sap.libs.xmltoolkit/lib/sapxmltoolkit.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/activation.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/jaxm-api.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/saaj-api.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/jaxrpc-api.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/jnet.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/jsse.jar;D:/SAP/JDT/eclipse/plugins/com.sap.ext.libs.webservices/lib/mail.jar;D:/SAP/JDT/eclipse/plugins/com.sap.tc.webdynpro.model.webservice/lib/_webdynpro_model_webservice.jar;, DynamicProxy.HTTPPassword=, DynamicProxy.INetProxy.Bypass=http://sapdephr.deutsche-boerse.de:50000|sapdephr.deutsche-boerse.de:50000|, DynamicProxy.INetProxy.Port=8080, DynamicProxy.HTTPUserName=, DynamicProxy.Javac.path=D:\j2sdk1.4.2_06, DynamicProxy.TempDir=c:\temp\, DynamicProxy.INetProxy.Host=http://webproxy.deutsche-boerse.de}'
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:413)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:371)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:341)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:305)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:315)
         at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.PageRenameWS.loadNameSpacesAndModelClasses(PageRenameWS.java:435)
         at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelDialog.nextPressed(ModelDialog.java:105)
         at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:316)
         at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
         at org.eclipse.jface.window.Window.open(Window.java:563)
         at com.sap.ide.webdynpro.modeleditor.ModelEditorCallback.createModel(ModelEditorCallback.java:52)
         at com.sap.ide.webdynpro.service.modeleditor.ModelService.createModelWithUI(ModelService.java:70)
         at com.sap.ide.webdynpro.service.modeleditor.ServiceWithUI.createModel(ServiceWithUI.java:49)
         at com.sap.ide.webdynpro.tsmodel.application.provider.ModelNodeProvider.createUniqueName(ModelNodeProvider.java:55)
         at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntityUin(EntityImpl.java:936)
         at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntity(EntityImpl.java:502)
         at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.runInternal(CreationAction.java:76)
         at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.access$000(CreationAction.java:24)
         at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction$1.run(CreationAction.java:51)
         at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
         at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.run(CreationAction.java:57)
         at com.sap.ide.webdynpro.projectbrowser.actions.PBCreateModelAction.run(PBCreateModelAction.java:95)
         at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:224)
         at com.tssap.util.ui.menu.MenuFactory$MuSiAction.saveRunAction(MenuFactory.java:1425)
         at com.tssap.util.ui.menu.MenuFactory$MuSiAction.run(MenuFactory.java:1407)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:616)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:586)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:716)
         at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:610)
         at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
         at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
         at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
         at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
         at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:286)
         at com.sap.ide.eclipse.startup.Main.run(Main.java:795)
         at com.sap.ide.eclipse.startup.Main.main(Main.java:602)
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details.
         at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:149)
         at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:49)
         at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:71)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:411)
         ... 53 more
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Problem with WSDL file parsing. See nested message.
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:182)
         at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:146)
         ... 56 more
    Caused by: com.sap.engine.lib.xml.util.NestedException: IO Exception occurred while parsing file:Cannot connect to http://sapdephr.deutsche-boerse.de:50000/WSCheckUser/Config1?wsdl , passing via http proxy: http://webproxy.deutsche-boerse.de:8080, used user to connect: : http://webproxy.deutsche-boerse.de -> java.io.IOException: Cannot connect to http://sapdephr.deutsche-boerse.de:50000/WSCheckUser/Config1?wsdl , passing via http proxy: http://webproxy.deutsche-boerse.de:8080, used user to connect: : http://webproxy.deutsche-boerse.de
         at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1038)
         at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadWSDLDocument(WSDLDOMLoader.java:1125)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:178)
         ... 57 more
    Caused by: java.io.IOException: Cannot connect to http://sapdephr.deutsche-boerse.de:50000/WSCheckUser/Config1?wsdl , passing via http proxy: http://webproxy.deutsche-boerse.de:8080, used user to connect: : http://webproxy.deutsche-boerse.de
         at com.sap.engine.services.webservices.tools.WSDLDownloadResolver.resolveEntity(WSDLDownloadResolver.java:161)
         at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1018)
    I have configured in preferences the proxy. (Try it also without a proxy) . If I call the url in IE - the IE shows the wsdl.
    Thanks Stefan

    Hai Stefan,
    Down load the WSdl from Navigator, and then browse it for the web service model.
    NWDS 04s giving some problem while creating webservice model via URL.
    Regards,

  • Problem with the Browsing of Services Registry in Visual Composer

    Hi,
    I have tried to connect Visula Composer of CE 7.1 to the Services Registry for ES Workplace by configuring 3 Web Service destination on my local server:
    1. UDDI_DESTINATION
    2. CLASSIFICATION_DESTINATION
    3. Backend destination "HU2"
    as stated in the tutorial "How to Browse an Enterprise Services Registry in Visual Composer" (https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/605303db-9d5f-2a10-e0a2-c0e1c8af9e96&overridelayout=true).
    After the configuration, I opened up the "Search" dialog in Visual Composer and selected "Service Registry" for the "Search in" drop down list and then clicked on the link "Advanced Search". An error message "XMSG_COULD_NOT_LOAD_CLASSIFICATIONS" was then displayed. I have tried to google the error message but to my surprise there wasn't even a single result for that.
    Could anyone please help me on this?
    Thanks in advance.
    Regards,
    Joon Meng

    Hi Mike,
    Thanks for your reply. It is actually my intention to try out with the Services Registry for ES Workplace. The thing is, I was able to connect my NWDS to the SR, but not in Visual Composer.
    Below are the URLs for both destination.
    1. UDDI_DESTINATION: http://sr.esworkplace.sap.com/uddi/wsdl/uddi_v3_service.wsdl
    2. CLASSIFICATION_DESTINATION: http://sr.esworkplace.sap.com/ClassificationService/CS?wsdl
    I tried to open the first URL in my browser and a WSDL document was displayed, but for the second URL an error message "503 Service Unavailable" was returned.
    Does this mean that the second URL "http://sr.esworkplace.sap.com/ClassificationService/CS?wsdl" might be the cause of the problem?
    Regards,
    Joon Meng

  • Service Registry: why do i need two bindings (wsdlDeployment and endPoint)

    based on the technical note of Clemens Utschig "Enabling a Dynamic, Reusable SOA with Oracle BPEL Process Manager and Oracle Service Registry" i have one question:
    why do i need two bindings (wsdlDeployment and endPoint) in my service in the service registry. if i only define the wsdlDeployment if get this messages:
    <2006-12-07 09:39:02,559> <FATAL> <default.collaxa.cube.ws> no endpoint found - nothing to adjust
    <2006-12-07 09:39:02,559> <WARN> <default.collaxa.cube.ws> Could not lookup base endpoint!
    the problem of defining two bindings is that the url to my partner is redundant.

    Hi Clemens,
    The UDDI Version 3.0.2 Specification (http://www.uddi.org/pubs/uddi_v3.htm) say this:
    B.1.2 Using the "wsdlDeployment" value
    Instead of directly providing the network address in the accessPoint, it is occasionally useful or necessary to provide this information through indirect means. One common scenario for such a behavior is when the accessPoint is embedded within a WSDL file. In such a scenario, the UDDI accessPoint contains the address of the WSDL file, and the client then must retrieve the WSDL file and extract the end point address from the WSDL file itself.
    In this case, decorating the UDDI accessPoint with a useType="wsdlDeployment" is appropriate. A sample of such behavior is as follows:
    <bindingTemplate bindingKey="uddi:example.org:catalog">
       <description xml:lang="en">
           Browse catalog Web service
       </description>
       <accessPoint useType="wsdlDeployment">
           http://www.example.org/CatalogWebService/catalog.wsdl
       </accessPoint>
       <categoryBag>
           <keyedReference keyName="uddi-org:types:wsdl"
           keyValue="wsdlDeployment"
           tModelKey="uddi:uddi.org:categorization:types"/>
       </categoryBag>
    </bindingTemplate>In the example above, a client would be able to parse the result of the bindingTemplate and determine the end point of the Web service within the WSDL file discovered in the accessPoint element. Note that the bindingTemplate has also been categorized with the "wsdlDeployment" value from the uddi.org:categorization:types scheme so that it can be discovered through a find_binding API call.
    1) This means for me that providing one binding with useType=wsdlDeployment should be enough.
    2) Sadly the "Business Service Control" of the Service Registry (Publish new WSDL service) does not create the correct structure needed by the bpel-engine. The "Publish new WSDL service" wizard just creates one service with one binding with useType=other (http). So if i want to reuse this published service from bpel (as a service consumer) i have to switch to the "Service Registry Admin Control" and create a second binding with useType=wsdlDeployment. But i don't want the developers to get inside the "Service Registry Admin Control"! They should only work with the "Business Service Control".
    All this makes the usage of the service-registry very unhandy and reduce the acceptance for developers because of unnecessary manual steps and broken security principles.
    My wish for this issue is that the "Publish new WSDL service" inside the "Business Service Control" of the Service Registry would additionlly create this needed binding with useType=wsdlDeployment.
    Best Regards,
    Harald Reinmueller

Maybe you are looking for

  • WILL AIM iChat work with AIM Triton for PC?

    I see RALPH's how to and his summary notes advising that AIM PC will not work the AIM Chat. But is this the case for AIM's new TRITON? My friend has downloaded TRITON. He is able to invite me to chat with AUDIO. Triton activates my iChat asking me to

  • Image Displays Differently in PS and Br CS4

    I have a gs tif file that I converted to cmyk. In PS the cmyk version looks virtually identical on screen to the gs version although when you hold the eyedropper over the image, cyan displays as a higher percentage than m or y, with k lowest in both

  • Unable to use class in same directory

    I am not really new to java. But havent worked with these environment variables for a long time. I am not able to use my public classes in the same directory. I know it is perfectly legal but I am not able to solve the problem. My environment variabl

  • Phone replaced, unable to add/register replacement iphone5s - "According to our records, this serial number is registered with to another Apple ID!"

    Hello everyone, A month ago, I had several dark pixels on brand new iphone5s, went to shop to have it replaced. Waited 15 days and finally got replacemnt phone, luckly working fine. I loaded backup of the previous phone to it, and noticed that each t

  • Flash player/shockwave crashing

    using windows 7, the latest mozilla, flash n shockwave... games crash on facebook and also here on the adobe site when i've been toubleshooting... from what i can see i'm not the only person having these problems yet no fix... i have uninstalled and