WSDL of WebService

Hi,
I have a problem with the generated WSDL of a WebService, created in the NDS.
First I created a stateless SessionBean in a EJB-module-project (and then a ear-application...). Then I generated with the WebService-wizard a WebService and deployed it on the J2EE engine. So far so good, I'm able to test the Service in the WebService Navigator and it works fine.
Now, when I try to download the wsdl-file i miss the methods in the wsdl-description and also the Message I want to send and receive (for this I'm not able to generate my client-proxy-classes; in my special case I want to import the wsdl-description in XI). Can anybody explain me how to generate a wsdl-file, where I get the messages and methods-interfaces I need to call the service?
Regards Thomas

In the WS Navigator you will see a link that looks like ...
http://hostname:50000/WS_Name/Config1?wsdl
If you open that link then you will see that it has a reference to another URL using <wsdl:import> tag. If you open this another URL it will reference one more 'import' URL.
These imports when all added together complete the whole wsdl that will show your EJB methods. Most of the WS test/build tools are able to resolve these types of imports automatically.

Similar Messages

How to publish WSDL as Webservice in XI 3.0

Hello,
My Scenario is SOAP --XI -- R/3(Proxy). XI version is XI 3.0 and SAP R/3 4.7
Generated a WSDL for SOAP Sender(ID>Tools>Define webservice)
I want to know how can i publish this WSDL as webservice.
Appericiate your help.
Srinivas
Edited by: Srinivas on Apr 20, 2010 11:42 AM

Generating the WSDL file (as you have already done) and then providing it to the sender application so that they send the message according to the format and to the target URL (your PI system) means that you have published your WSDL.....and this logic remains the same till the latest available version of SAP XI/ PI.....just that when you say SAP PI7.1 it is only addition of functionality on how the WSDLs are published.
the application team is not required to publish the WSDL....they are required to consume it.
Regards,
Abhishek.

Error trying to generate WSDL of webservice in JDeveloper 11.1.1.3

Hey,
Everytime I try to generate a WSDL of a webservice I get the following stack trace:
java.lang.NullPointerException
     at oracle.jdeveloper.webservices.model.java.JavaWebServiceValidator.getTypeReasons(JavaWebServiceValidator.java:882)
     at oracle.jdeveloper.webservices.model.java.JavaWebServiceValidator.getInvalidValueTypes(JavaWebServiceValidator.java:1060)
     at oracle.jdeveloper.webservices.model.java.JavaWebServiceValidator.getValidationErrors(JavaWebServiceValidator.java:241)
     at oracle.jdeveloper.webservices.model.CoreHashStructureModel.validate(CoreHashStructureModel.java:187)
     at oracle.jdeveloper.webservices.model.generator.Validation.action(Validation.java:65)
     at oracle.jdeveloper.webservices.model.generator.GeneratorAction.run(GeneratorAction.java:143)
     at java.lang.Thread.run(Thread.java:619)
I'm able to run this webservice via run and debug as well as "Test this webservice." It's just when I try to generate the WSDL from within jdeveloper that I get this message. I'm even able to view the WSDL file within the browser by adding ?WSDL at the end of the url for the web service endpoint. Any ideas?

So, I need to have the @XmlSeeAlso() for this service to work since it relies on outside classes to run. But, I did remove the @XmlSeeAlso() from the class just to see if this would allow JDeveloper to generate the WSDL and when I do this I get the following stack trace:
oracle.jdeveloper.webservices.tools.WsdlValidationException: java.lang.NullPointerException
     at oracle.jdevimpl.webservices.tools.wsa.WsaAdaptor.newWsdlValidationException(WsaAdaptor.java:825)
     at oracle.jdevimpl.webservices.tools.wsa.WsaAdaptor.createWsdl(WsaAdaptor.java:376)
     at oracle.jdeveloper.webservices.tools.WebServiceTools.createWsdl(WebServiceTools.java:388)
     at oracle.jdeveloper.webservices.model.java.generator.CreateWSDL.createWSDL(CreateWSDL.java:281)
     at oracle.jdeveloper.webservices.model.generator.CommonCreateWSDL.action(CommonCreateWSDL.java:59)
     at oracle.jdeveloper.webservices.model.generator.GeneratorAction.run(GeneratorAction.java:143)
     at java.lang.Thread.run(Thread.java:619)
Caused by: oracle.j2ee.ws.common.tools.api.ValidationException: java.lang.NullPointerException
     at oracle.j2ee.ws.tools.wsa.JavaToWsdlTool.genWSDL(JavaToWsdlTool.java:1079)
     at oracle.j2ee.ws.tools.wsa.Util.genWSDL(Util.java:1559)
     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:597)
     at oracle.jdevimpl.webservices.tools.wsa.Assembler$2$1.invoke(Assembler.java:218)
     at $Proxy42.genWSDL(Unknown Source)
     at oracle.jdevimpl.webservices.tools.wsa.WsaAdaptor.createWsdl(WsaAdaptor.java:372)
     ... 5 more
Caused by: java.lang.NullPointerException
     at oracle.j2ee.ws.common.jaxws.wsdl.WSDLTypesGenerator.generateGlobalElement(WSDLTypesGenerator.java:308)
     at oracle.j2ee.ws.common.jaxws.wsdl.WSDLTypesGenerator.generateWrapperGlobalElements(WSDLTypesGenerator.java:226)
     at oracle.j2ee.ws.common.jaxws.wsdl.WSDLTypesGenerator.generateTypes(WSDLTypesGenerator.java:134)
     at oracle.j2ee.ws.common.jaxws.wsdl.WSDLGenerator.generateTypes(WSDLGenerator.java:236)
     at oracle.j2ee.ws.common.jaxws.wsdl.WSDLGenerator.generateWsdlForOnePortType(WSDLGenerator.java:190)
     at oracle.j2ee.ws.common.jaxws.wsdl.WSDLGenerator.generate(WSDLGenerator.java:157)
     at oracle.j2ee.ws.tools.wsa.JavaToWsdlTool.genWSDL(JavaToWsdlTool.java:1074)
     ... 13 more
Edited by: user12883803 on Jun 25, 2010 7:02 AM

Working with wsdl files (webservices)

Hi All,
Im working with webservices (ie. wsdl files)
I need to automate the process, where in the Source is Oracle table and end target is wsdl file
I thought of the approach like : Table to XML then use this XML to populate the wsdl file
but the Issue here is if I try to generate the XML from Table it doesnt have SOAP envelope enclosed (tried with OdiSqlUnload)
version : 11.1.1.5
Pls share your ideas how to achieve this
Regards,
M

HI Himanshu,
Thanks for your reply, I've been trying the same as I mentioned in me first post itself.
But I am stuck with the XML load itself... it has got around 15 to 18 elements/tags and 5 extra elements like LoadDate,Message,Source like that which holds default data (standard)
I followed the link : https://s3.amazonaws.com/Ora/XML_5_db_to_Complex_XML.swf, but still confused as the Interface i failing at those 5 element mappings.
The package ran fine but the XML doesnt hold data, the individual datastores has data when checked under the Models.
Regards,
M

Testing WSDL through webservice navigator

HI All,
Please elaborate on how to test the WSDL link though webservice navigator.
Di we require some different installations or what exactly is webservice navigator
Edited by: solutionProvider on Dec 24, 2010 8:43 PM

HI All,
Please elaborate on how to test the WSDL link though webservice navigator.
Di we require some different installations or what exactly is webservice navigator
Edited by: solutionProvider on Dec 24, 2010 8:43 PM

Pragmatically Reload WSDL for WebService

Hey everyone,
I'm new here and i'm starting to try out RIA. I'm currently
working against a little test web service. Pretty simple and trim.
Here's my problem.
I want to seemlessly handle when the web service goes down.
The senario is like this:
1.) WebService goes offline at the web server.
2.) User executes an operation with returns with a ioError
fault.
3.) This error is captured and identified as a
"Disconnection"
4.) Now the user is presented with a modal popup informing
them the web service is down.
5.) A time was started that will test if the web service is
online at a set interval.
6.) When the service is back online, the modal popup is
removed, and the user can continue with their work
My reconnection code is pretty simple. It's:
myWebService.disconnect();
myWebService.loadWSDL();
My assumption is that when you execute the loadWSDL, it will
go out to the server and attempt to download and reload the WSDL.
There is a fault capture on the main webservice so i can detect
when the loadWSDL fails. If it fails, the webserivce is offline so
i keep the modal up. If the loadWSDL can be loaded, the "load"
event is fired for the webservice. I detect this event and remove
the modal popup.
However, the loadWSDL does not go back to the server. It
detects that it has already been loaded, and fires the "load" event
for the webservice.
So my main goal here is to have a way to test if the
webservice is online. I *could* develop a simple webservice
function that simply returns a string if it's online. But i want to
avoid having odd calls like that in my webservice. There has to be
a way you can do this.
Any help would be hugely appreciated.

Still looking for a response on this. So far we've
implemented a webservice call to check if the webservice is active.
But i'd be interested if there's an answer.
I'm hopeing the answer will help me understand why the
WebService object needs to download the WSDL everytime in the first
place.

Auto deploy of ALSB/OSB artifacts - Proxy, WSDL and webservices...

Would like to know if there are any leads on how to automate the deployment of artifacts within OSB in an automated manner using WLST or any other method

Hi,
One can use offline WLST scripts for automated deployment. The script (python scripts) can be invoked using Ant. In summary, the steps are:
1. Copy the relevant files in a folder (preferably <DOMAIN_HOME>). The files are
a. import.py: The actual python script that does the deployment process
b. import.properties: A properties file used by the import script. It contains information about the deployment jar file (sbconfig.jar), any customization file, host and port information of the OSB server and credential information
c. sbconfig.jar(Or any other name): OSB deployable artifacts bundled using the editor or exported from another OSB environment
d. build.xml: Defines the import task executed by ant
e. OSB customization xml file
2. Open a command prompt (Windows environment), navigate to <DOMAIN_HOME>/bin and execute setDomainenv.bat
3. Additionally add the follwing jar files to the classpath. These files are used by the APIs used in the python script. These were not needed prior to the 3.0 version of OSB (ALSB). The files are: +<BEA_HOME>/modules/com.bea.common.configfwk_1.1.0.0.jar+ and +<OSB_HOME>/lib/sb-kernel-api.jar+
4. Using the same command prompt, navigate to the folder where the files in step 1 had been placed and exeute the import task using ant (something like ant import)
Plese find a sample of the import.py, build.xml and import.properties files as follows:
*================= import.py =============================*
from java.util import HashMap
from java.util import HashSet
from java.util import Map
from java.util import Set
from java.util.Map import Entry
from java.util import ArrayList
from java.util import Hashtable
from java.lang import System
from java.io import FileInputStream
from weblogic.management.mbeanservers.domainruntime import DomainRuntimeServiceMBean
from javax.management.remote import JMXConnector
from weblogic.management.jmx import MBeanServerInvocationHandler
from com.bea.wli.sb.management.configuration import ALSBConfigurationMBean
from com.bea.wli.sb.management.configuration import SessionManagementMBean
from com.bea.wli.config.customization import Customization
from javax.management import ObjectName;
from com.bea.wli.config.resource import Diagnostics
from javax.management.remote import JMXConnectorFactory
from javax.management.remote import JMXServiceURL
from javax.naming import Context
from com.bea.wli.config import Ref
from com.bea.wli.sb.management.importexport import ALSBImportPlan
from com.bea.wli.sb.management.importexport import ALSBImportOperation
import sys
#=======================================================================================
# Entry function to deploy project configuration and resources
# into a OSB domain
#=======================================================================================
def importToALSBDomain(importConfigFile):
try:
print 'Loading Deployment config from :', importConfigFile
exportConfigProp = loadProps(importConfigFile)
host = exportConfigProp.get("host")
port = exportConfigProp.get("port")
intPort = int(port)
print "Connecting to: " + host + ":" + port
importUser = exportConfigProp.get("importUser")
importPassword = exportConfigProp.get("importPassword")
importJar = exportConfigProp.get("importJar")
 customFile = exportConfigProp.get("customizationFile")
# passphrase = exportConfigProp.get("passphrase")
# project = exportConfigProp.get("project")
 print "Initiate Connection"
 conn = initConnection(host, intPort, importUser, importPassword)
 print "Connection successful"
 mbconn = conn.getMBeanServerConnection()
 obname = DomainRuntimeServiceMBean.OBJECT_NAME
 domainService = MBeanServerInvocationHandler.newProxyInstance(mbconn, ObjectName(obname))
 name = SessionManagementMBean.NAME
 type = SessionManagementMBean.TYPE
 sm = domainService.findService(name, type, None)
 bytes = readBinaryFile(importJar)
 sessionName = "ScriptImport"
 print "sessionName: ", sessionName
 sm.createSession(sessionName)
 alsbSession = domainService.findService(ALSBConfigurationMBean.NAME + "." + sessionName, ALSBConfigurationMBean.TYPE, None)
 alsbSession.uploadJarFile(bytes)
 jarInfo = alsbSession.getImportJarInfo()
 importPlan = jarInfo.getDefaultImportPlan()
 result = alsbSession.importUploaded(importPlan);
 # list of created references
 createdRef = ArrayList()
 operationMap = importPlan.getOperations()
 set = operationMap.entrySet()
 for entry in set:
 ref = entry.getKey()
 createdRef.add(ref)
# Print out status and build a list of created references. Will be used for customization
 if result.getImported().size() > 0:
 print "The following resources have been imported: "
 for successEntry in result.getImported():
 print successEntry.toString()
# Check for error and discard session in any resource fails
 failCount = result.getFailed().size()
 if failCount > 0:
 print ""
 print "Failed for: " + failCount + " resources"
# print "The following resources failed to import"
# for entry in result.getFailed().entrySet():
# ref = entry.getKey()
# diagnostics = entry.getValue().toString()
# print ref + " Reason: " + diagnostics
# abort = true
# raise
#=================================================
# Apply Customizations
#=================================================
#customize if a customization file is specified
#affects only the created resources
 if customFile != None :
 print "Loading customization File: " + customFile
 print "Customization applied to the created resources only" + createdRef.toString()
 iStream = FileInputStream(customFile)
 customizationList = Customization.fromXML(iStream)
 filteredCustomizationList = ArrayList()
 setRef = HashSet(createdRef)
# apply a filter to all the customizations to narrow the target to the created resources
 for customization in customizationList:
 newcustomization = customization.clone(setRef)
 filteredCustomizationList.add(newcustomization)
 alsbSession.customize(filteredCustomizationList)
#=========================
# Activate Session
#=========================
 sm.activateSession(sessionName, "Imported Configuration")
 print "Project imported"
 conn.close()
except:
print "Unexpected error:", sys.exc_info()[0]
 print "Discarding the session."
 sm.discardSession(sessionName)
 conn.close()
 raise
#==================================================
# Utility function for initiating connection
#================================================
def initConnection(hostname, port, username, password):
 serviceURL = JMXServiceURL("t3", hostname, port,"/jndi/" + DomainRuntimeServiceMBean.MBEANSERVER_JNDI_NAME)
 h=Hashtable()
 h.put(Context.SECURITY_PRINCIPAL, username)
 h.put(Context.SECURITY_CREDENTIALS, password)
 h.put(JMXConnectorFactory.PROTOCOL_PROVIDER_PACKAGES, "weblogic.management.remote")
 return JMXConnectorFactory.connect(serviceURL, h)
#=======================================================================================
# Utility function to print the list of operations
#=======================================================================================
def printOpMap(map):
set = map.entrySet()
for entry in set:
op = entry.getValue()
print op.getOperation(),
ref = entry.getKey()
print ref
print
#=======================================================================================
# Utility function to print the diagnostics
#=======================================================================================
def printDiagMap(map):
set = map.entrySet()
for entry in set:
diag = entry.getValue().toString()
print diag
print
#=======================================================================================
# Utility function to load properties from a config file
#=======================================================================================
def loadProps(configPropFile):
propInputStream = FileInputStream(configPropFile)
configProps = Properties()
configProps.load(propInputStream)
return configProps
#=======================================================================================
# Connect to the Admin Server
#=======================================================================================
def connectToServer(username, password, url):
connect(username, password, url)
domainRuntime()
#=======================================================================================
# Utility function to read a binary file
#=======================================================================================
def readBinaryFile(fileName):
file = open(fileName, 'rb')
bytes = file.read()
return bytes
#=======================================================================================
# Utility function to create an arbitrary session name
#=======================================================================================
def createSessionName():
sessionName = String("SessionScript"+Long(System.currentTimeMillis()).toString())
return sessionName
#=======================================================================================
# Utility function to load a session MBeans
#=======================================================================================
def getSessionMBean(sessionName):
SessionMBean = findService("Session","com.bea.wli.config.mbeans.SessionMBean")
SessionMBean.createSession(sessionName)
return SessionMBean
# IMPORT script init
try:
# import the service bus configuration
# argv[1] is the export config properties file
importToALSBDomain(sys.argv[1])
except:
print "Unexpected error: ", sys.exc_info()[0]
dumpStack()
raise
*=================================================================*
*================ import.properties ======================================*
# OSB Admin Security Configuration #
host=localhost
port=7001
importUser=weblogic
importPassword=weblogic
# OSB Jar to be exported, optional customization file #
importJar=ALSBSampleProject.jar
#Use the following if you have any customization xml file#
#customizationFile=ALSBSampleProject_Customization.xml
# Optional passphrase and project name #
#passphrase=
#project=
*===================================================================*
*============================== build.xml===============================*
<project default="import">
<property name="domain.import.script" value="import.py"/>
<property name="import.config.file" value="import.properties"/>
<target name="import">
 <echo message="Importing configuration"/>
 <echo message="importscript: ${domain.import.script}"/>
 <java classname="weblogic.WLST" fork="true">
<arg line="${domain.import.script} ${import.config.file}"/>
 </java>
</target>
</project>
*=====================================================================*
Hope this helps
Thanks & Regards,
Vivek

WSDL SOAP Webservices

Hi Guys,
I am looking for information and tutorials in creating
websites using SOAP
services, if anyone knows of any links or good information on
using web
services to create website I would be most grateful.
I am looking to create in ASP.NET vb with mySQL
I have read the info in DW8 but it is very limited and can
only find a
tutorial for CFM
Many Thanks
Lez

If you don't post your code and the error messages, we can't help you ...

Error in WebDynpro with WebServices

Hi all,
Im getting some errors using applications deployed in WEB AS SP9 that runs as a WebDynpro IView in EP.
Running the application as standalone (out of EP) this works fine.
NetWeaver Developer Studio 2.0.9
WebDynpro application using WebServices that access Oracle 8i database in the follow sequence:
WebServices -> Session Bean stateless -> Entity Bean CMP (manage connections; generate sql code, etc.)
In WebDynpro application we import WebService Model by the follow sequence:
New Model - Import Web Service Model - Local Server for WSDL Source - <WebService deployed>
In each WebServices we have created these methods:
findByID(ID);
getAll();
insert(parameters);
remove(ID);
update(parameters);
We guess that the error is generated in Entity Bean because all WebServices generate these errors.
Error 1 - Application with WebServices Model
Error stacktrace:
com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Repository Object br.com.xxx.fluxo.Fluxo/ComponentInterface:FluxoInterface/InterfaceViews:CadastroSituacaoFluxoInterfaceView/InboundPlugs:Default associated via relation RepositoryObjectRelation(br.com.xxx.fluxo.application.CadastroSituacaoFluxoApp, StartupPlug) does not exist.
 at com.sap.tc.webdynpro.repository.RelationToOne.resolveTargets(RelationToOne.java:124)
 at com.sap.tc.webdynpro.repository.RelationToOne.mergeTargets(RelationToOne.java:108)
 at com.sap.tc.webdynpro.repository.RelationToOne.mergeTargets(RelationToOne.java:72)
 at com.sap.tc.webdynpro.repository.RelationToOne.getTarget(RelationToOne.java:174)
 at com.sap.tc.webdynpro.repository.RepositoryObject.getRelatedModelObject(RepositoryObject.java:349)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getStartupPlugInternal(IWDApplicationInfo.java:319)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:355)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
 at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
 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:385)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 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:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
-- end --
Error 2 - Application with WebServices Model
An error has occurred:
"Failed to process the request."
Please contact your system administrator.
Hide details
Web Dynpro client:
HTML Client
Web Dynpro client capabilities:
User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
Web Dynpro runtime:
Vendor: SAP, Build ID: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-19:21:48:59[UTC], changelist=290362, host=PWDFM026)
Web Dynpro code generators of DC local/Apontamentos:
SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:31:53[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:36:19[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:00[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
SapWebDynproGenerationCTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:25:03[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:01[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:29:01[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:11[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:33[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates: (unknown)
Web Dynpro code generators of DC sap.com/tcwddispwda:
No information available
Web Dynpro code generators of DC sap.com/tcwdcorecomp:
No information available
J2EE Engine:
6.40 patchlevel 87037.313
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_06-b03, vendor: Sun Microsystems Inc.
Operating system:
Windows 2000, version: 5.0, architecture: x86
Error stacktrace:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Did not find repository information for controller NotProductiveEventController
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.createCustomController(DelegatingComponent.java:55)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:428)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:371)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:400)
 at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:138)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:746)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
 at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
 at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:374)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
 at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
 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:385)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 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:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Error 3 - Application with RFC Model
An error has occurred:
"Failed to process the request."
Please contact your system administrator.
Hide details
Web Dynpro client:
HTML Client
Web Dynpro client capabilities:
User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
Web Dynpro runtime:
Vendor: SAP, Build ID: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-19:21:48:59[UTC], changelist=290362, host=PWDFM026)
Web Dynpro code generators of DC local/Apontamentos:
SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:31:53[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:36:19[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:00[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
SapWebDynproGenerationCTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:25:03[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:01[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:29:01[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:11[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:33[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates: (unknown)
Web Dynpro code generators of DC sap.com/tcwddispwda:
No information available
Web Dynpro code generators of DC sap.com/tcwdcorecomp:
No information available
J2EE Engine:
6.40 patchlevel 87037.313
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_06-b03, vendor: Sun Microsystems Inc.
Operating system:
Windows 2000, version: 5.0, architecture: x86
Error stacktrace:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Did not find repository information for controller ZMANPP012Controller
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.createCustomController(DelegatingComponent.java:55)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:428)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:371)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:400)
 at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:138)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:746)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
 at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
 at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:374)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
 at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
 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:385)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 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:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)

Hi,
I feel this error is nothing to do with webservice model.
Please check your application properties like startupPlug,Interface View etc. Set the properties correctly and deploy once again.
Regards, VIP

Issue with provided message for WSDL of SAP PI sender interface

Hi,
as I am not familar with SOAP interfaces and use of WSDL by partners with WSDL generated in SAP PI there are some issues that I have with a scenario:
1. Import of external xsd for message is done
2. Enterprise Repository and Integration Directory objects are completely created and activated
3. WSDL was generated from ID Sender agreement (This is PI 7.1)
4. Partner got the WSDL
The partner provided now some test messages by mail that I would like to test in the mapping as the message is really complex.
But the result is strange...
1. The header of the partner message is this:
<XJustiz_Daten xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Grunddaten xmlns="http://www.xjustiz.de">
(Some german words are in that example. But this doesn t matter!)
This is different to the xml that PI generates in mapping:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:XJustiz_Daten xmlns:ns0="http://www.xjustiz.de">
 <ns0:Grunddaten>
 <ns0:Grunddaten XJustizVersion="">
Partner defines xsi: instead of ns0 and PI fails using this message!
So I had to change the message header and add ns0: to all element tags and node tags of the message.
(See for example with first node "Grunddaten").
2. There are some mandatory nodes and elements.
An example:
- Rechtsform is mandatory node (1..1) with element content (mandatory 1..1)
So it will appear in the payload like this:
 <ns0:Rechtsform>
 <ns0:content xmlns=""/>
 </ns0:Rechtsform>
But the partner provides this:
<Rechtsform xsi:nil="true" />
which is the next issue as PI doesn t understand as xsi is not mapped to a namespace. !
It would be easy to use an "exist" function to solve the issue with the not provided element but this will not help
when the node is provided with additinal information xsi:....
Can you give any help/answer why PI is not able to handle such things.
Thank you!
Best regards
Dirk

Hello Meinhard,
If you are the Service Owner, the sender system must use your wsdl message (WebService Definition).
If there're other problems or the sender system can't use your message structure, in agreement with them you need to develope a different mapping.

How to defne user mapping for a Webservice method to acheive single sign on

I all,
I have created a Web service System using a url (containing full path of my wsdl )
Now this particular wsdl(my webservice) has an authenticate method , which takes username and password.
wanted to know is there any way that i can do user mapping for it .
i.e when i create an ivew for this web service system using authenticate method , it should pick up the username and password from the user mapping. presently the ivew itself asks for username and password ?
else can anyone tellme is there a way to do user mapping for my web service system that i have created using a wsdl url. presently it works with any junk username password, i mean the connection always succeds , may be because accessing a wsdl dosent requires any user name and password.
thanks

I all,
I have created a Web service System using a url (containing full path of my wsdl )
Now this particular wsdl(my webservice) has an authenticate method , which takes username and password.
wanted to know is there any way that i can do user mapping for it .
i.e when i create an ivew for this web service system using authenticate method , it should pick up the username and password from the user mapping. presently the ivew itself asks for username and password ?
else can anyone tellme is there a way to do user mapping for my web service system that i have created using a wsdl url. presently it works with any junk username password, i mean the connection always succeds , may be because accessing a wsdl dosent requires any user name and password.
thanks

How to use Fault schema in WSDL for Error Handling in ALSB

We are not able to view the fault element in our alsb flow under body variable and when we get the error in test console the error comes in bea fault schema,but we want the error in our own defined fault schema.Pls. guide.
Below are the steps we followed to create a wsdl.
Steps:
1. We created a webservice project in workspacestudio and generated a wsdl.
2. Then we have added a fault element manually in that wsdl.
3. Now we have generated a webservice from that modified wsdl.
4. Again we have generated a wsdl from webservice created in step 3.
5. step 4 wsdl is tested and running well on server.
When we try to configure that service as Proxy/Business service in ALSB and view the XPATH Expression Editor, we are not able to view Fault element under variable structures under body variable as shown below.But when we see the design view of our running wsdl in workspace studio it shows the fault element.How to get the fault element in variable body so that we can view the error in our logs in our defined Fault schema instead of BEA fault schema.WDSL is enclosed as an attachment.
Thanks in advance

Have you tried using the "Log" action in your pipeline proxy and log for $body and $fault. This will defin return the $body and $fault if these were parsed correctly

WSDL missing xsd:annotation & xsd:appinfo tags for new field

Hi,
I was recently asked to add a new field to a service interface. I made the changes to the Data Type and Mapping as appropriate and after activating those changes went to the Sender Agreement to save the WSDL in a file so I can handle it to our business partner (I created the file on the IB under Sender Agreement-->Display WSDL). During the testing of interface using webservice navigator response gave an exception. We checked the WSDL file and the new field is there but it's missing the <xsd:annotation> & <xsd:appinfo> tags (which all of the other fields have).
Here's an extract of how the WSDL looks, the new field is URI, ORG_NM2, ORG_NM3:
<xsd:element name="IV_J_1IPANREF" type="xsd:string">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 c6a198762dd811e48dab0c84dcced6b4
 </xsd:appinfo>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="URI" type="xsd:string" />
 <xsd:element name="ORG_NM2" type="xsd:string" />
 <xsd:element name="ORG_NM3" type="xsd:string" />
As you can see the annotation and appinfo tags are missing for the new field URI ORG_NM2, ORG_NM3,. I think this might be the reason why they don't see the new field when they upload the WSDL to their system. Is there something else I need to do for the WSDL to be generated correctly?
Please suggest urgently.
Neeraj

Hi Luis,
You are right fields are coming correctly but when I am testing the wsdl using webservice navigator or SOAP UI I am getting the below exception:
com.sap.engine.services.webservices.jaxrpc.exceptions.XmlUnmarshalException: XML Deserialization Error. XML Parser has thrown exception while parsing input. See nested exception.
Error Log:

<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
 <context>XIAdapter</context>
 <code>ADAPTER.JAVA_EXCEPTION</code>
 <text><![CDATA[
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Application:EXCEPTION_DURING_EXECUTE:
at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:765)
I though that since missing of these two <xsd:annotation> & <xsd:appinfo> tag may be the ssue because after adding new fields this was the only difference in WSDL.
Regards,
Neeraj

Sender SOAP Adapter issue with webservices for authorization.

Hi All
Issue:
As we are developing a Web Service to fetch account balance from SAP(upon receiving the account no from client) and have given the wsdl file to J2EE application to call or make use of the service. But as a part of that service they expect userid/password to be entered manually from client pop-up. At this point of time, we don't want to enter userid/password manually but we want this to be hardcoded/embedded in Webservice so that there is no need of manual intervention upon calling this service.
Actual Requirement:
From Webservices to R/3-ECC6.0-IS-Banking-RFC (Synchronous Interface)
Sender: SOAP Adapter synchronous
Receiver: RFC Adapter synchronous
Note: Requesting a account number and getting response from RFC is account Balance and Date to webservice
Regards
Kiran kumar.s

Hi praveen,
Thanks for ur reply.What you said is exactly right but for time being i have to make the client not get the authorization(password--Username and password(pop-up)) when he invokes the WSDL into webservice for that u told that to write some hardcode in J2EE application,but i don't know that where to write and what to write.so, if possible can u give me the code and procedure.
This is the URL:
http://hcl3sap:50000/XISOAPAdapter/MessageServlet?channel=:BS_WEBSERVICE:CC_SOAPSENDER
Regards,
kiran kumar.

RFC to SOAP Scenario - WSDL-Import really needed?

Hey @all,
we like to feed a webservice via SAP Backend. As middleware we use SAP PI 7.1.
The planned scenario is RFC to SOAP. The wsdl of webservice (NON-SAP) has no filled soapAction-Parameter and the operation with name "process" occures three times in it with the same name, but each operation "process" has it's own Request / method (axis), like "Request1", "Request2", "Request3". Each request has it's own response.
In this case it is not possible to import the wsdl as external references correctly - the import gaves an error caused of the identical names of the three operation-parameters.
The question is:
Is it possible to work this out without the import of wsdl and without soapAction-Parameter?
How could we call the correct operation?
Thanks very much in advance,
Stefan

Hi,
Maybe you could try to editing the WSDL and import it three times e.g for process (1) here is the WSDL (1) --> Make sure you delete the other process.
Make message mapping for each process and its corresponding response. So that would be, 6 message mappings (request and response) and 3 operation mappings.
In Integration Directory, call the correct operation in Interface Determination by using xPath.
http://wiki.sdn.sap.com/wiki/display/XI/XpathConditioninReceiverDetermination
although the blog above is for receiver determination, the xPath conditions for interface determination are the same.
For the without SOAP Action parameter, I guess it is okay to leave blank. I have not used the SOAP Axis though (I used the PLAIN_HTTP adapter for that). Just to be sure, test it in SOAP UI.
Hope this helps,
Mark

WSDL of WebService

Similar Messages

Maybe you are looking for