Not able to generate Service control from WSDL in Weblogic Workshop9.2

Hi All,
I am not able to create Service control from my WSDL in Weblogic workshop9.2. It was working fine in Weblogic 8.1.
I am getting the following error. Please help me out.
Types analysis failed for both JAX-RPC and XmlBeans.
BEGIN JAX-RPC CAUSE
com.bea.control.servicecontrol.internal.validation.BindingsCheckException: Failed to generate the JSService with the endpoint builder
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.setupJsService(BindingsClassNameReference.java:573)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.loadJsService(BindingsClassNameReference.java:321)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.getJsService(BindingsClassNameReference.java:362)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.loadTypeNamesForService(BindingsClassNameReference.java:398)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.getTypeNamesForService(BindingsClassNameReference.java:383)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.getComplexTypeNamesForService(BindingsCheckUtility.java:210)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.getComplexTypeBindingTypeInfoForService(BindingsCheckUtility.java:131)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.getComplexTypeBindingInfoForServiceByBindingsDataSourceType(BindingsCheckUtility.java:104)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.initializeTypesForTheService(BindingsCheckUtility.java:273)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.findMatchingBindingsDataSources(BindingsCheckUtility.java:434)
at com.bea.wlw.controls.service.ui.util.BindingsChecker.<init>(BindingsChecker.java:55)
at com.bea.wlw.controls.service.ui.wizards.SelectSCInfoPage.checkForCompatibleBindings(SelectSCInfoPage.java:304)
at com.bea.wlw.controls.service.ui.wizards.SelectSCInfoPage.<init>(SelectSCInfoPage.java:98)
at com.bea.wlw.controls.service.ui.GenerateSCWizard.getPageList(GenerateSCWizard.java:150)
at com.bea.wlw.controls.service.ui.GenerateSCWizard.addPages(GenerateSCWizard.java:136)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:499)
at org.eclipse.jface.window.Window.create(Window.java:418)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:996)
at org.eclipse.jface.window.Window.open(Window.java:776)
at com.bea.wlw.controls.service.ui.actions.NewSCGenAction.run(NewSCGenAction.java:101)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:246)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
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:585)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
at org.eclipse.core.launcher.Main.run(Main.java:973)
at org.eclipse.core.launcher.Main.main(Main.java:948)
Caused by: java.lang.IllegalArgumentException: unable to find java type for t=String@http://www.w3.org/2001/XMLSchema
at weblogic.wsee.bind.buildtime.internal.TylarBuildtimeBindings.getClassFromXmlType(TylarBuildtimeBindings.java:693)
at weblogic.wsee.bind.buildtime.internal.TylarBuildtimeBindings.getClassFromSchemaType(TylarBuildtimeBindings.java:182)
at weblogic.wsee.tools.source.EndpointBuilder.getJavaClassName(EndpointBuilder.java:735)
at weblogic.wsee.tools.source.EndpointBuilder.addPart(EndpointBuilder.java:664)
at weblogic.wsee.tools.source.EndpointBuilder.createParams(EndpointBuilder.java:591)
at weblogic.wsee.tools.source.EndpointBuilder.addMethod(EndpointBuilder.java:521)
at weblogic.wsee.tools.source.EndpointBuilder.buildEndpoint(EndpointBuilder.java:475)
at weblogic.wsee.tools.source.EndpointBuilder.buildJsService(EndpointBuilder.java:252)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.setupJsService(BindingsClassNameReference.java:549)
... 43 more
END JAX-RPC CAUSE
BEGIN XMLBEANS CAUSE
com.bea.control.servicecontrol.internal.validation.BindingsCheckException: Could not create buildtime bindings with ClientGenUtil
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.loadBuildtimeBindings(BindingsClassNameReference.java:242)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.getBindings(BindingsClassNameReference.java:161)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.loadJsService(BindingsClassNameReference.java:307)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.getJsService(BindingsClassNameReference.java:362)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.loadTypeNamesForService(BindingsClassNameReference.java:398)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.getTypeNamesForService(BindingsClassNameReference.java:383)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.getComplexTypeNamesForService(BindingsCheckUtility.java:210)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.getComplexTypeBindingTypeInfoForService(BindingsCheckUtility.java:131)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.getComplexTypeBindingInfoForServiceByBindingsDataSourceType(BindingsCheckUtility.java:104)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.initializeTypesForTheService(BindingsCheckUtility.java:253)
at com.bea.control.servicecontrol.internal.validation.BindingsCheckUtility.findMatchingBindingsDataSources(BindingsCheckUtility.java:434)
at com.bea.wlw.controls.service.ui.util.BindingsChecker.<init>(BindingsChecker.java:55)
at com.bea.wlw.controls.service.ui.wizards.SelectSCInfoPage.checkForCompatibleBindings(SelectSCInfoPage.java:304)
at com.bea.wlw.controls.service.ui.wizards.SelectSCInfoPage.<init>(SelectSCInfoPage.java:98)
at com.bea.wlw.controls.service.ui.GenerateSCWizard.getPageList(GenerateSCWizard.java:150)
at com.bea.wlw.controls.service.ui.GenerateSCWizard.addPages(GenerateSCWizard.java:136)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:499)
at org.eclipse.jface.window.Window.create(Window.java:418)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:996)
at org.eclipse.jface.window.Window.open(Window.java:776)
at com.bea.wlw.controls.service.ui.actions.NewSCGenAction.run(NewSCGenAction.java:101)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:246)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
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:585)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
at org.eclipse.core.launcher.Main.run(Main.java:973)
at org.eclipse.core.launcher.Main.main(Main.java:948)
Caused by: weblogic.wsee.tools.WsBuildException: com.bea.xml.XmlException: Exception while compiling org apache xmlbeans: C:\R4WorkSpace\TestEWS\src\controls\EWSDeal.wsdl:0: error: src-resolve: type 'Array@http://schemas.xmlsoap.org/soap/encoding/' not found.
at weblogic.wsee.tools.clientgen.ClientGenUtil.createBuildtimeBindings(ClientGenUtil.java:217)
at weblogic.wsee.tools.clientgen.ClientGenUtil.createBuildtimeBindings(ClientGenUtil.java:174)
at com.bea.control.servicecontrol.internal.validation.BindingsClassNameReference.loadBuildtimeBindings(BindingsClassNameReference.java:228)
... 44 more
Caused by: com.bea.xml.XmlException: Exception while compiling org apache xmlbeans: C:\R4WorkSpace\TestEWS\src\controls\EWSDeal.wsdl:0: error: src-resolve: type 'Array@http://schemas.xmlsoap.org/soap/encoding/' not found.
at weblogic.wsee.bind.buildtime.internal.XmlBeansApacheBindingsBuilderImpl.createBuildtimeBindings(XmlBeansApacheBindingsBuilderImpl.java:262)
at weblogic.wsee.bind.buildtime.internal.XmlBeansBaseBindingsBuilderImpl.createBuildtimeBindings(XmlBeansBaseBindingsBuilderImpl.java:119)
at weblogic.wsee.tools.source.EndpointBuilder.setupBindingProviderWithServices(EndpointBuilder.java:836)
at weblogic.wsee.tools.clientgen.ClientGenUtil.createBindingProvider(ClientGenUtil.java:458)
at weblogic.wsee.tools.clientgen.ClientGenUtil.createBuildtimeBindings(ClientGenUtil.java:211)
... 46 more
Caused by: org.apache.xmlbeans.XmlException: C:\R4WorkSpace\TestEWS\src\controls\EWSDeal.wsdl:0: error: src-resolve: type 'Array@http://schemas.xmlsoap.org/soap/encoding/' not found.
at weblogic.wsee.bind.buildtime.internal.XmlBeansApacheBindingsBuilderImpl.compileXmlBeans(XmlBeansApacheBindingsBuilderImpl.java:361)
at weblogic.wsee.bind.buildtime.internal.XmlBeansApacheBindingsBuilderImpl.createBuildtimeBindings(XmlBeansApacheBindingsBuilderImpl.java:257)
... 50 more
END XMLBEANS CAUSE

Hi
I have not seen the wsdl yet but your xmlbean types generation looks familiar.
This is one reason why you could get the error with the xmlbeans type.
error: src-resolve: type 'Array@http://schemas.xmlsoap.org/soap/encoding/' not found.
Workaround: To allow the XmlBeans to be built from this type of WSDL correctly, add the schemaLocation attribute. For example, if the original WSDL had an import such as:
<s:import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
It should be changed to the following:
<s:import namespace="http://schemas.xmlsoap.org/soap/encoding/" schemaLocation="http://schemas.xmlsoap.org/soap/encoding/"/>
After this change you should not see the error.
Vimala-

Similar Messages

Workshop 10.0.1 - Generating service control from a WSDL file

Hi!
I've been familiarising myself with Workshop (version 10.0.1).
There is a feature that allows the generation of a web service control by right-clicking a WSDL file (Web Services > Generate Service Control).
This process creates a jar file containing the WSDL's complex type.
My only problem with this is that the jar uses the namespaces as package names (for example: www.openuri.org will be converted into an org.openuri package).
I've been searching for a way to customize the package names, but I've been unable to find it. We previously used Axis to generate a web service client, and we ran an Ant task that could map namespaces to packages.
Would there be a way to achieve this in Workshop?
Thank you!

Hi
This is a known issue and a limitation. Service controls doesn't honor xsdconfig files when generated from wsdl file.
We have an enhancement request CR307698 pending to address this issue. It looks like it's a big change in code to get this working so it is being looked at in the next release.
Also, you can call BEA support / create a case in future and request status on this CR anytime.
Vimala-

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]

Not able to generate the spool from transaction cv02n .Kindly help,urgent..

Hi ALL,
I have a problem in transaction CV02N. Actually i am an ABAPER, but i need some help of PP Guys.
The requirement is as follows:-
The client says that they have uploaded a '.PS' file into the transaction cv02n.Here in the first screen they give doc, doc type,doc part, doc version. when clicked on enter it take us to second screen , where they enter the '.PS' file path under 'originals' , in the tab 'document data'. Later they goto transaction CO01 and release an order at the operation level and save it.
Then it generates a spool. Now if we goto SP01 and check the spool with the number generated during saving CO01. We will be getting the scripts and the '.PS' file separately in a different spool in the production system in 4.6. But in my new upgraded system(6.0), i am not able to view the '.PS' file in the output spool.It seems to me that, it is not getting generated. Pls suggest me, as it is a very urgent issue. Need to close it by today at 1.00pm.
Regards,
Manasa.S

dear friend,
there would be several reasons for that.
first, check out your Output Device (your user in SU01) - goto to tab Defaults and look at Spool Control.
did you tick the 'output immediately' checkbox?
Fix it if nessesary. Just in case run SPAD to check out your device.
second, check out the 'output' config for Document Management (because you use t-code CV02N).
also make sure that relevant output condition exists.
third, ask someone to do the same - another user with another output device. does he/she have the same problem?
and the last, try to find out the functional guy or documentation.
also ask your basis guy regarding the lost transports or any other issues...
do not worry, life is good.
good luck!

Not able to create Service Contract from another svc.contract as followup

Hi,
I am trying to create a service contract from another service contract as folllow up document as a part of contract renewal process. However, when I click on follow up button, in the popup, not able to the option Service Contract. Hence I am unable to create.
Could you please let me know, what needs to be done such that Service Contract also will be shown in the popup.
Thanks for all the replies.
Thanks,
Sandeep

Hello Sandeep,
It is not possible to create a follow up service contract (BUS2000112) for another service contract (BUS2000112).
I do not know your business scenario, you can debug method GET_FOLLOWUP_CUST of class CL_CRM_UIU_BT_GET_PROCTYPES and see where the follow-up transaction types are filtered out.
I met similar case before, the solution provided at that time was
- modify FM CRM_UBB_FILTER_SUC_PROC_TYPE in line 49. You can comment out the following line:
delete ct_suc_proc_type where process_type = ls_suc_proc_type-process_type.
Hope this could be helpful.
Best regards,
Maggie

Not able to Call JDBC control from MDB

I need to call a method in the JDBC control from the Message Driven Bean(MDB). When I try to do so, Weblogic throws an error. I tried to call a Custom Control from MDB and the Custom Control called a method in the JDBC control but that does not work too. Can someone help me solve this?
Can't we call the JDBC control from MDB? There should be some way around this.
This is the error I get :
org.apache.beehive.controls.api.ControlException: Control initialization failure[org.apache.beehive.controls.api.ControlException: Contextual service org.apache.beehive.controls.api.context.ResourceContext is not available]
     at org.apache.beehive.controls.runtime.bean.ControlBean.ensureControl(ControlBean.java:326)
     at com.boehringer.supplier.control.db.ForecastJDBCControlBean.updateSpendWithCMId(ForecastJDBCControlBean.java:2879)
     at com.boehringer.supplier.control.java.SupplierControlImpl.processCustomer(SupplierControlImpl.java:1290)
     at com.boehringer.supplier.control.java.SupplierControlImpl.processSonicInboundMessage(SupplierControlImpl.java:1096)
     at com.boehringer.supplier.control.java.SupplierControlBean.processSonicInboundMessage(SupplierControlBean.java:663)
     at com.boehringer.sonic.SonicVendorInboundMDB.onMessage(SonicVendorInboundMDB.java:45)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
     at weblogic.ejb.container.internal.ContinuousJMSMessagePoller.processOneMessage(ContinuousJMSMessagePoller.java:138)
     at weblogic.ejb.container.internal.JMSMessagePoller.pollContinuously(JMSMessagePoller.java:404)
     at weblogic.ejb.container.internal.ContinuousJMSMessagePoller.pollForParent(ContinuousJMSMessagePoller.java:213)
     at weblogic.ejb.container.internal.JMSMessagePoller.run(JMSMessagePoller.java:543)
     at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.beehive.controls.api.ControlException: Contextual service org.apache.beehive.controls.api.context.ResourceContext is not available
     at org.apache.beehive.controls.system.jdbc.JdbcControlImplInitializer.initServices(JdbcControlImplInitializer.java:50)
     at org.apache.beehive.controls.runtime.bean.ImplInitializer.initialize(ImplInitializer.java:34)
     at org.apache.beehive.controls.runtime.bean.ControlBean.ensureControl(ControlBean.java:321)
     ... 12 more

Hi,
I am getting the same error. Did you got any solution for this?
Please help.
Any kind of help is appreciated.
Thanks,
Dpak

Not able to edit Service Contract from WEBUI beacause of error

Hi,
I am trying to edit Service Contract from WEB UI. But, when ever I say edit, it is giving error saying
"Document is being distributed. Changes are not possible".
Can you please let me know, why such error comes..and how to rectify that.
Thanks,
Sandeep

Hi Sandeep,
This happens when the document is distributed to ERP Systems. There are certain Item Categories that are sent to ERP System and only once the confirmations comes from those system you can further process those document.
You won't find any errors there.
You can check the BDOC Entries and then can find the target system where the document was distributed. And then logon onto that system and release that document.
Hope this helps.
Thanks,
Samantak.

Failed to generate client proxy from WSDL definition for this service

Hi,
I am using Weblogic 8.1 SP1. I created a webservice which takes a XMLBean object
as parameter and returns another XMLBean object. The web service works fine when
tested using the workshop's test browser but when i am trying to generate a client
proxy trough the workshop's test browser, it displays this warning:
Failed to generate client proxy from WSDL definition for this service
and does not generate the proxy.
I'll appreciate any thoughts on this.
Thanks
Sandeep

Hi Sandeep,
Could you try invoking clientgen [1] directly to see if this properly
consumes your WSDL?
Thanks,
Bruce
[1]
http://e-docs.bea.com/wls/docs81/webserv/anttasks.html#1080160
Sandeep wrote:
>
Hi,
I am using Weblogic 8.1 SP1. I created a webservice which takes a XMLBean object
as parameter and returns another XMLBean object. The web service works fine when
tested using the workshop's test browser but when i am trying to generate a client
proxy trough the workshop's test browser, it displays this warning:
Failed to generate client proxy from WSDL definition for this service
and does not generate the proxy.
I'll appreciate any thoughts on this.
Thanks
Sandeep

Not able to generate reports after 8.1.1.3 patch installation

Hi All,
We are not able to generate reports after 8.1.1.3 patch installtion.
and we also followed workaround as below
1) Import the sif files from Siebel\8.1\Tools_1\REPPATCH\12-1VMBCSV.zip
2) Import the 4 SIF files in the following order:
S_XMLP_REP_TMPL_02112010.sif
SBL_XMLP_REPORT_SELECTION_FLG.sif
Report Template BC.sif
Report Template Registration Applet.sif
3)Apply the DDL for table S_XMLP_REP_TMPL and compile repository
Still not able to generate Reports.
Below is error message
Please ask your systems administrator to check your application configuration.
ObjMgrMiscLog Error 1 000000064e150fa0:0 2011-07-07 19:45:31 (busobj.cpp (1654)) SBL-DAT-00222: An error has occurred creating business component 'Report Template Position BC' used by business object 'Report Administration'.
Please ask your systems administrator to check your application configuration.
ObjMgrBusServiceLog Error 1 000000064e150fa0:0 2011-07-07 19:45:31 (swemenusvc.cpp (406)) SBL-DAT-00222: An error has occurred creating business component '<?>' used by business object '<?>'.
Please ask your systems administrator to check your application configuration.
Thanks
Sean

Hi Rajan,
Thankyou for for your reply.
Reports were working fine and we are able to generate reports at configured views in 8.1.1.1 version.
After installing 8.1.1.3 patch, if we click on reports icon below is the error message displayed.
An error has occurred creating business component '<?>' used by business object '<?>'.
Please ask your systems administrator to check your application configuration. (SBL-DAT-00222).
- is it mandatory to configure security model?(in 8.1.1.1 we used default security model)?
-is it necessary to import BIPDataService and BIPSiebelSecurityWS inbound Web Services?
- I didn't see below views as mentioned in bookshelf.
. Reports - Custom Templates
. Reports - Standard Templates?
Thanks
Sean

Is it possible to create data control from wsdl when complextype is used

Getting DCA-40015 error when trying to create a data control from WSDL file.
The error clearly says complextype is not supported . just trying to see if there are any workarounds . because creating data control will save time in developing user interface by dragging and dropping the the data control in jsf page. jdeveloper webservice tester is able to create user interface for me based on wsdl when i run it , trying to develop the user interface using jsf pages
oracle.adf.model.adapter.AdapterException: DCA-40015: Failed to create the structure for schema element "result". The complex type definition of the element is not supported.

Hi,
I could reproduce what I did:
- created WebService from custom Pojo Model
- Made sure all entities implemented serializable
- In the WebServices Wizard, I created XML representations for my entities
- tested with OC4J WebServices tester
- Built ADF data control from WSDL file of deployed WebService
- Created dependency t project containing the POJO entities
- Selected result.xml of each method exposed in the WebService project
- In the structure window, selected "item" (result-->item)
- changed Bean class to my entity class name (absolute name)
This showed my entity in the DC palette
Frank

Error in generating .cs file from wsdl

hi ,
I am trying to generate .cs file from wsdl using commond
wsdl
http://pni3w274:8080/tc5_services/WebServices/ModelEntity?wsdl /language:CS /out:rt.cs /protocol:SOAP
it give following errors
Error: Unable to import binding 'ModelEntitySoapBinding' from namespace 'http://
teamcenter.com/TCENT/webservices/2005-06/services/ModelEntity'.
- Unable to import operation 'getListOfClasses'.
- The datatype 'http://teamcenter.com/TCENT/webservices/2005-06/schemas/ModelE
ntity:GetListOfClassesInputParams' is missing.
my wsdl is
ModelEntityService.wsdl
<?xml version="1.0" encoding="UTF-8" ?>
<wsdl:definitions
targetNamespace="http://teamcenter.com/TCENT/webservices/2005-06/services/ModelEntity"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsi="http://ws-i.org/schemas/conformanceClaim/"
xmlns:imp0="http://teamcenter.com/TCENT/webservices/2005-06/schemas/ModelEntity"
xmlns:imp1="http://teamcenter.com/webservices/2005-06/schemas/WSFaults"
xmlns:tns="http://teamcenter.com/TCENT/webservices/2005-06/services/ModelEntity">
<wsdl:documentation>
The service provides Model Entity related operation.
</wsdl:documentation>
<wsdl:types>
<xs:schema>
<xs:import namespace="http://teamcenter.com/TCENT/webservices/2005-06/schemas/ModelEntity" schemaLocation="ModelEntity.xsd" />
<xs:import namespace="http://teamcenter.com/webservices/2005-06/schemas/WSFaults" schemaLocation="WSFaults.xsd" />
</xs:schema>
</wsdl:types>
<wsdl:message name="PresentationTierFault">
<wsdl:part name="ex0" element="imp1:RequestManangerFault" />
</wsdl:message>
<wsdl:message name="getListOfClassesRequest">
<wsdl:part name="in0" element="imp0:GetListOfClassesInputParams" />
</wsdl:message>
<wsdl:message name="getListOfClassesResponse">
<wsdl:part name="out" element="imp0:GetListOfClassesOutputParams" />
</wsdl:message>
<wsdl:message name="getCreateAttributesRequest">
<wsdl:part name="in0" element="imp0:GetCreateAttributesInputParams" />
</wsdl:message>
<wsdl:message name="getCreateAttributesResponse">
<wsdl:part name="out" element="imp0:GetCreateAttributesOutputParams" />
</wsdl:message>
<wsdl:message name="createModelEntityRequest">
<wsdl:part name="in0" element="imp0:CreateModelEntityInputParams" />
</wsdl:message>
<wsdl:message name="createModelEntityResponse">
<wsdl:part name="out" element="imp0:CreateModelEntityOutputParams" />
</wsdl:message>
<wsdl:message name="getValueSetForAttributeRequest">
<wsdl:part name="in0" element="imp0:GetValueSetForAttributeInputParams" />
</wsdl:message>
<wsdl:message name="getValueSetForAttributeResponse">
<wsdl:part name="out" element="imp0:GetValueSetForAttributeOutputParams" />
</wsdl:message>
<wsdl:portType name="ModelEntity">
<wsdl:operation name="getListOfClasses">
<wsdl:documentation>
Gets List Of all ModelEntity Classes.
</wsdl:documentation>
<wsdl:input message="tns:getListOfClassesRequest" name="getListOfClassesRequest" />
<wsdl:output message="tns:getListOfClassesResponse" name="getListOfClassesResponse" />
<wsdl:fault message="tns:PresentationTierFault" name="PresentationTierError" />
</wsdl:operation>
<wsdl:operation name="getCreateAttributes">
<wsdl:documentation>
Gets ModelEntity Create Attributes.
</wsdl:documentation>
<wsdl:input message="tns:getCreateAttributesRequest" name="getCreateAttributesRequest" />
<wsdl:output message="tns:getCreateAttributesResponse" name="getCreateAttributesResponse" />
<wsdl:fault message="tns:PresentationTierFault" name="PresentationTierError" />
</wsdl:operation>
<wsdl:operation name="createModelEntity">
<wsdl:documentation>
Creates Model Entity.
</wsdl:documentation>
<wsdl:input message="tns:createModelEntityRequest" name="createModelEntityRequest" />
<wsdl:output message="tns:createModelEntityResponse" name="createModelEntityResponse" />
<wsdl:fault message="tns:PresentationTierFault" name="PresentationTierError" />
</wsdl:operation>
<wsdl:operation name="getValueSetForAttribute">
<wsdl:documentation>
Gets Value Set For Attribute.
</wsdl:documentation>
<wsdl:input message="tns:getValueSetForAttributeRequest" name="getValueSetForAttributeRequest" />
<wsdl:output message="tns:getValueSetForAttributeResponse" name="getValueSetForAttributeResponse" />
<wsdl:fault message="tns:PresentationTierFault" name="PresentationTierError" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="ModelEntitySoapBinding" type="tns:ModelEntity">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
<wsdl:operation name="getListOfClasses">
<soap:operation style="document" soapAction="getListOfClasses" />
<wsdl:input><soap:body use="literal" /></wsdl:input>
<wsdl:output><soap:body use="literal" /></wsdl:output>
<wsdl:fault name="PresentationTierError"><soap:fault name="PresentationTierError" use="literal" /></wsdl:fault>
</wsdl:operation>
<wsdl:operation name="getCreateAttributes">
<soap:operation style="document" soapAction="getCreateAttributes" />
<wsdl:input><soap:body use="literal" /></wsdl:input>
<wsdl:output><soap:body use="literal" /></wsdl:output>
<wsdl:fault name="PresentationTierError"><soap:fault name="PresentationTierError" use="literal" /></wsdl:fault>
</wsdl:operation>
<wsdl:operation name="createModelEntity">
<soap:operation style="document" soapAction="createModelEntity" />
<wsdl:input><soap:body use="literal" /></wsdl:input>
<wsdl:output><soap:body use="literal" /></wsdl:output>
<wsdl:fault name="PresentationTierError"><soap:fault name="PresentationTierError" use="literal" /></wsdl:fault>
</wsdl:operation>
<wsdl:operation name="getValueSetForAttribute">
<soap:operation style="document" soapAction="getValueSetForAttribute" />
<wsdl:input><soap:body use="literal" /></wsdl:input>
<wsdl:output><soap:body use="literal" /></wsdl:output>
<wsdl:fault name="PresentationTierError"><soap:fault name="PresentationTierError" use="literal" /></wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="ModelEntityService">
<wsdl:port binding="tns:ModelEntitySoapBinding" name="ModelEntity">
<soap:address
location="http://localhost:80/PTierApp/WebServices/ModelEntity" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
and xsd is ModelEntity.xsd
<?xml version="1.0" encoding="UTF-8"?>

<xsd:schema targetNamespace="http://teamcenter.com/TCENT/webservices/2005-06/schemas/ModelEntity"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsc="http://teamcenter.com/TCENT/webservices/2005-06/schemas/Common"
xmlns:wlt="http://teamcenter.com/TCENT/webservices/2005-06/schemas/ModelEntity"
elementFormDefault="qualified"
attributeFormDefault="unqualified">



<xsd:annotation>
<xsd:documentation>
The ModelEntity package defines elements and data types
for the parameters used by operations/messages of the ModelEntity Web Service.
</xsd:documentation>
</xsd:annotation>



<xsd:element name="GetListOfClassesInputParams"
type="wlt:GetListOfClassesInputType"/>
<xsd:complexType name="GetListOfClassesInputType">
<xsd:sequence>
<xsd:element name="UserName" type="xsd:string"/>
<xsd:element name="Password" type="xsd:string"/>
<xsd:element name="Locale" type="xsd:string" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>






<xsd:element name="GetListOfClassesOutputParams"
type="wlt:GetListOfClassesOutputType"/>
<xsd:complexType name="GetListOfClassesOutputType">
<xsd:sequence>
<xsd:element name="ClassList" type="wlt:ModelEntityValueDisplayedValuePair"
minOccurs="0" maxOccurs="unbounded" />
<xsd:element name="ReturnType" type="xsd:boolean"/>
<xsd:element name="ReturnMessage" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>






<xsd:element name="GetCreateAttributesInputParams"
type="wlt:GetCreateAttributesInputType"/>
<xsd:complexType name="GetCreateAttributesInputType">
<xsd:sequence>
<xsd:element name="UserName" type="xsd:string"/>
<xsd:element name="Password" type="xsd:string"/>
<xsd:element name="Locale" type="xsd:string" minOccurs="0"/>
<xsd:element name="ClassName" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>






<xsd:element name="GetCreateAttributesOutputParams"
type="wlt:GetCreateAttributesOutputType"/>
<xsd:complexType name="GetCreateAttributesOutputType">
<xsd:sequence>
<xsd:element name="Attributes" type="wlt:ModelEntityCreateAttributes"
minOccurs="0" maxOccurs="unbounded" />
<xsd:element name="ReturnType" type="xsd:boolean"/>
<xsd:element name="ReturnMessage" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>






<xsd:element name="GetValueSetForAttributeInputParams"
type="wlt:GetValueSetForAttributeInputType"/>
<xsd:complexType name="GetValueSetForAttributeInputType">
<xsd:sequence>
<xsd:element name="UserName" type="xsd:string"/>
<xsd:element name="Password" type="xsd:string"/>
<xsd:element name="Locale" type="xsd:string" minOccurs="0"/>
<xsd:element name="Attribute" type="xsd:string"/>

<xsd:element name="Criteria" type="wlt:ModelEntityNameValuePair"
minOccurs="0" maxOccurs="unbounded" />

<xsd:element name="ClassName" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>






<xsd:element name="GetValueSetForAttributeOutputParams"
type="wlt:GetValueSetForAttributeOutputType"/>
<xsd:complexType name="GetValueSetForAttributeOutputType">
<xsd:sequence>
<xsd:element name="StaticValues" type="wlt:ModelEntityValueDisplayedValuePair"
minOccurs="0" maxOccurs="unbounded" />
<xsd:element name="ReturnType" type="xsd:boolean"/>
<xsd:element name="ReturnMessage" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>






<xsd:element name="CreateModelEntityInputParams"
type="wlt:CreateModelEntityInputType"/>
<xsd:complexType name="CreateModelEntityInputType">
<xsd:sequence>
<xsd:element name="UserName" type="xsd:string"/>
<xsd:element name="Password" type="xsd:string"/>
<xsd:element name="Locale" type="xsd:string" minOccurs="0"/>
<xsd:element name="ClassName" type="xsd:string"/>
<xsd:element name="Attributes" type="wlt:ModelEntityNameValuePair"
maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>






<xsd:element name="CreateModelEntityOutputParams"
type="wlt:CreateModelEntityOutputType"/>
<xsd:complexType name="CreateModelEntityOutputType">
<xsd:sequence>
<xsd:element name="ObjectHandle" type="xsd:string"/>
<xsd:element name="ReturnType" type="xsd:boolean"/>
<xsd:element name="ReturnMessage" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>






<xsd:complexType name="ModelEntityCreateAttributes">
<xsd:sequence>
<xsd:element name="DisplayedName" type="xsd:string"/>
<xsd:element name="Name" type="xsd:string"/>
<xsd:element name="StaticValues" type="wlt:ModelEntityValueDisplayedValuePair"
minOccurs="0" maxOccurs="unbounded" />
<xsd:element name="IsRequired" type="xsd:boolean"/>
<xsd:element name="HasValueSet" type="xsd:boolean"/>
</xsd:sequence>
</xsd:complexType>






<xsd:complexType name="ModelEntityNameValuePair">
<xsd:sequence>
<xsd:element name="Name" type="xsd:string"/>
<xsd:element name="Value" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ModelEntityValueDisplayedValuePair">
<xsd:sequence>
<xsd:element name="Value" type="xsd:string"/>
<xsd:element name="DisplayedValue" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>



</xsd:schema>

check metalink note
Adpatch Fails With Error : adogjf() Unable to copy Registry.Dat.
Note:282153.1
also check (Adogjf() Unable To Copy Registry.Dat).
Note:382695.1 about the correct on the $806_ORACLE_HOME/forms60/java where it should be 755
make sure that you soruce the env fiel before adpatch and that ORACLE_HOME is poinitng to the correct oracle_home
fadi

Could not install DPM agent on Secondry site DPM could not connect to the Service control manager : ID 33221

Hi,
We have two DPM 2012 R2 server installed at Primary and Secondary site Windows 2012 R2 installed.
We need to Protected Primary DPM from Secondary DPM.
When install DPM agent got error from secondary DPM console.
“DPM could not connect to the Service Control Manager on these servers ID: 33221”
Checked till now :
Visual C++ redistributable installed.
Checked DNS A record and both server can ping each other,
Widows Firewall off on both servers.
Net stop mpssvc ( Windows firewall service)
sc \\Server1 query
àable
to see result
Thanks,

Hi
You mention checking the DNS A record, are these 2 servers not in the same domain? Can you ping -a computername?
Do you have any other AV software that have firewalls built in?
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Not able to generate multiple lines for headers in report

Hi,
I am new to BI publisher and not able to generate multiple lines for headers. Please help me to resolve.
I am using RTF template, data source as PS Query and XML file (system generated from the data source)
When I am using system generated 'First XML' file, I am getting output in the follwoing format.
TEAM_MEMBER, PROJECT_ID, NAME, START_DT
e.g.
EMP1 , 71000, Sample, 01-Jan-2010
EMP1 , 72000, Sample, 01-Feb-2010
EMP1 , 73000, Sample, 01-March-2010
But I want the report to be generate with multiple projects for one employee like below format , for that I used 'Second XML' file but I am getting blank report.
In short if there is one to many case, how to show in reports??? Please correct if I am going wrong.
TEAM_MEMBER
PROJECT_ID, NAME, START_DT
PROJECT_ID, NAME, START_DT
PROJECT_ID, NAME, START_DT
e.g.
EMP1
71000, Sample, 01-Jan-2010
72000, Sample, 01-Feb-2010
73000, Sample, 01-March-2010
**********First XML**************System generated XML ****************************
<?xml version="1.0"?>
<query numrows="2" queryname="SY_EMP_PROJECT" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="">
<row rownumber="1">
<TEAM_MEMBER>TEAM_MEMBER </TEAM_MEMBER>
<PROJECT_ID>PROJECT_ID samp</PROJECT_ID>
<NAME>NAME sample data</NAME>
<START_DT>2010-08-25</START_DT>
</row>
<row rownumber="2">
<TEAM_MEMBER>TEAM_MEMBER</TEAM_MEMBER>
<PROJECT_ID>PROJECT_ID samp</PROJECT_ID>
<NAME>NAME sample data</NAME>
<START_DT>2010-08-25</START_DT>
</row>
</query>
**********Second XML**************Manually created XML and using to show multiple projects for one employee****************
<?xml version="1.0"?>
<TEST numrows="2" queryname="SY_EMP_PROJECT" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="">
<TEAM_MEMBER rownumber="1">
<TEAM_MEMBER>1</TEAM_MEMBER>
<EMPLOYEE_NAME>SAMPLE</EMPLOYEE_NAME>
<PROJECT>
<PROJECT_ID>1111</PROJECT_ID>
     <PROJECT_DESCR>SAMPLE</PROJECT_DESCR>
<START_DATE>01012010</START_DATE>
</PROJECT>
<PROJECT>
<PROJECT_ID>1112</PROJECT_ID>
     <PROJECT_DESCR>SAMPLE</PROJECT_DESCR>
<START_DATE>01022010</START_DATE>
</PROJECT>
</TEAM_MEMBER>
<TEAM_MEMBER rownumber="2">
<TEAM_MEMBER>2</TEAM_MEMBER>
<EMPLOYEE_NAME>SAMPLEC</EMPLOYEE_NAME>
<PROJECT>
<PROJECT_ID>1111</PROJECT_ID>
     <PROJECT_DESCR>SAMPLE</PROJECT_DESCR>
<START_DATE>01012010</START_DATE>
</PROJECT>
<PROJECT>
<PROJECT_ID>1112</PROJECT_ID>
     <PROJECT_DESCR>SAMPLE</PROJECT_DESCR>
<START_DATE>01022010</START_DATE>
</PROJECT>
</TEAM_MEMBER>
</TEST>
Edited by: ganeshtw on Aug 25, 2010 12:14 AM

Hi,
With your first xml you can print like
EMP1
71000, Sample, 01-Jan-2010
72000, Sample, 01-Feb-2010
73000, Sample, 01-March-2010While creating the RTF template you can use the Group by option.
<?for-each-group:ROW;./columnname> then print the column name
<?columnname?>
--Then your table format
71000, Sample, 01-Jan-2010
72000, Sample, 01-Feb-2010
73000, Sample, 01-March-2010
<?end for-each-group?>
Thanks.

Not able to create a message from satellite system

Hello Everyone.
We have been working on Solution Manager .We have managed with successfull installation,Uploaded required support packages,configured the system according to SAP Solution Manager Guide.
Faced with some problem regarding support desk,we are not able to create a message from satellite system to Solution Manager.
Note : Error Message related to this problem is ....
<b>"Error in Local Message System : External number assignment, Enter notification num message was not Created."</b>
Thanks in advance.
Regards,
Nimesh V . Master

Hi, you need to check the number ranges for the notifications and make sure they are correct. Look in the IMG of the SAP Solution Manager system for the instructions. You also need to make sure that the Service Desk BC Sets are activated if you are NOT on 4.0 and SP Stack 09+. In the later SPs much of this configuration from the IMG is automated in the wizard.

Not able to generate AS2 MDN when receiving custom XML via AS2

Hi friends,
I have setup the trading partner and the corresponding TP certificate import for receiving the custom XML via AS2 channel.
I am receiving the custom xml properly to oracle b2b and able to receive the same to bpel as well. however in the oracle b2b console under reports tab i am seeing only one record for inbound document receive and i am not seeing the other record for the AS2 MDN going back to vendor. I have setup the AS2 channel under the external trading partner --> Channel using the vendor AS2 URL and selected all the security parameters while creating the Outbound AS2 channel.
1. Not able to generate AS2 MDN when receiving custom XML via AS2.
2. eventhough i am able to decrypt the inbound custom XML and ablr to recieve it in bpel also for processing, in the reports tab the inbound message state is changing to MSG_ERROR and it has the folloing error message:
Error Code
B2B-50037
Error Description
Machine Info: (***********) Description: B2B inbound message processing error
Error Level
ERROR_LEVEL_COLLABORATION
for AS2 MDN generation for custom XML receiving using As2 protocol, do we need to setup anything other than the outbound As2 Channel using the external vendor AS2 URL?
Can you please help me how can i generate the AS2 MDN for the inbound custom XML document i have received and also why the inbound message is failing even though i am receiving the custom XML properly to bpel?
Thanks,
Amirineni.

Hi Prasanna,
Vendor has enabled the ACK mode as SYNC.
Below are the headers for the inbound message to B2B. and we are able to receive the input message to bpel also.
Protocol Transport Binding
ChannelName=******** AS2-To=****AS2 TE=trailers, deflate, gzip, compress Date=Thu, 02 Oct 2014 14:26:31 GMT AS2-Version=1.2 Accept-Encoding=deflate, gzip, x-gzip, compress, x-compress AS2-From=****AS2 Disposition-Notification-Options=signed-receipt-protocol=optional, pkcs7-signature; signed-receipt-micalg=optional, sha1 Disposition-Notification-To=https://******/as2 Message-ID=<CLEO-20141002_142630452-31X54N@****_*****AS2.pcwbedi1-O> Content-type=application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7m Content-length=747006 MSG_RECEIVED_TIME=Thu Oct 02 10:26:39 EDT 2014 Subject=EDI ECID-Context=1.005175bK7U^AXNJCAnf9Cx0002pW000yjX;kXjE1ZDLIPGIj2QCYV8QoKSSILRO_PQT_IS Proxy-Client-IP=****** Recipient-Address=https://******/b2b/httpReceiver User-Agent=RPT-HTTPClient/0.3-3I (Windows 2003) X-Forwarded-For=****** Content-Disposition=attachment; filename="smime.p7m" Host=****** EDIINT-Features=CEM, multiple-attachments, AS2-Reliability Connection=Keep-Alive X-WebLogic-KeepAliveSecs=30 X-WebLogic-Force-JVMID=-1497702782 From=****** Mime-Version=1.0
Message Digest
Message Digest
Digest Algorithm
sha1
Transport Protocol
HTTP
Transport Protocol Version
1.0
Url
http://******
security
Transport Headers
ChannelName=****** AS2-To=******AS2 TE=trailers, deflate, gzip, compress Date=Thu, 02 Oct 2014 14:26:31 GMT AS2-Version=1.2 Accept-Encoding=deflate, gzip, x-gzip, compress, x-compress AS2-From=****AS2 Disposition-Notification-Options=signed-receipt-protocol=optional, pkcs7-signature; signed-receipt-micalg=optional, sha1 Disposition-Notification-To=https://******/as2 Message-ID=<CLEO-20141002_142630452-31X54N@****AS2_*****AS2.pcwbedi1-O> Content-type=application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7m Content-length=747006 MSG_RECEIVED_TIME=Thu Oct 02 10:26:39 EDT 2014 Subject=EDI ECID-Context=1.005175bK7U^AXNJCAnf9Cx0002pW000yjX;kXjE1ZDLIPGIj2QCYV8QoKSSILRO_PQT_IS Proxy-Client-IP=***** Recipient-Address=*******/b2b/httpReceiver User-Agent=RPT-HTTPClient/0.3-3I (Windows 2003) X-Forwarded-For=******* Content-Disposition=attachment; filename="smime.p7m" Host=***** EDIINT-Features=CEM, multiple-attachments, AS2-Reliability Connection=Keep-Alive X-WebLogic-KeepAliveSecs=30 X-WebLogic-Force-JVMID=-1497702782 From=***** Mime-Version=1.0
Thanks,
Amirineni

Not able to generate Service control from WSDL in Weblogic Workshop9.2

Similar Messages

Maybe you are looking for