Java API: repository.login error

I MDM guru,
i habe the "little" problem with JAVA API SP2.
I have do the followings step:
- download last JAVA API from service.sap.com/swdc:
   Support Packages and Patches->SAP NetWeaver->SAP MDM->SAP MDM 5.5->JAVA API
- download "MDM Java API Samples Framework"
- downloadn MDM_API_SAMPLES repository (import ad load it in the MDM server)
When run Application.java (with program = KeyMappingProgram.RETRIEVE) when exextute this line
repository.login(region, user, password);
i have this error
com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: Dati non convalidati da verifica CRC
     at com.sap.mdm.commands.AuthenticateRepositorySessionCommand.execute(AuthenticateRepositorySessionCommand.java:94)
     at com.sap.nw.mdm.rig.server.SessionImpl.authenticateRepositorySession(SessionImpl.java:136)
     at com.sap.nw.mdm.rig.server.SessionImpl.<init>(SessionImpl.java:37)
     at com.sap.nw.mdm.rig.server.RepositoryImpl.login(RepositoryImpl.java:61)
     at com.sap.nw.mdm.rig.Application.start(Application.java:208)
     at com.sap.nw.mdm.rig.Application.main(Application.java:157)
Caused by: com.sap.mdm.internal.protocol.manual.ServerException: Dati non convalidati da verifica CRC
     at com.sap.mdm.internal.protocol.manual.AbstractProtocolCommand.execute(AbstractProtocolCommand.java:112)
     at com.sap.mdm.commands.AuthenticateRepositorySessionCommand.execute(AuthenticateRepositorySessionCommand.java:88)
     ... 5 more
com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: Dati non convalidati da verifica CRC
     at com.sap.mdm.commands.AuthenticateUserSessionCommand.execute(AuthenticateUserSessionCommand.java:84)
     at com.sap.nw.mdm.rig.server.SessionImpl.authenticateUserSession(SessionImpl.java:87)
     at com.sap.nw.mdm.rig.server.SessionImpl.<init>(SessionImpl.java:41)
     at com.sap.nw.mdm.rig.server.RepositoryImpl.login(RepositoryImpl.java:61)
     at com.sap.nw.mdm.rig.Application.start(Application.java:208)
     at com.sap.nw.mdm.rig.Application.main(Application.java:157)
Caused by: com.sap.mdm.internal.protocol.manual.ServerException: Dati non convalidati da verifica CRC
     at com.sap.mdm.internal.protocol.manual.AbstractProtocolCommand.execute(AbstractProtocolCommand.java:112)
     at com.sap.mdm.commands.AuthenticateUserSessionCommand.execute(AuthenticateUserSessionCommand.java:79)
     ... 5 more
Where is the problem?
This is my configuration:
MDM Server 5.5
- mds Version 5.5.61.48 Built on 2008-Jan-12
   Client Interface Version 5.5.61.12
   Console Interface Version 5.5.61.06
   Web Interface Version 5.5.61.12
mdm-core.jar:
    Build Version 5.5.62.83
Public Interface Version 5.5.62.00 [Interface CRC=0xab59b8dc]
Console Interface Version 5.5.62.01 [Interface CRC=0xf3c104b6]
    Web Interface Version 5.5.62.06 [Interface CRC=0x86541e49]

well i got this error while creating a repository session. but the crc is for version mismatch as said in the previous post.
Check the following wiki for details on the error
https://www.sdn.sap.com/irj/sdn/wiki?path=/pages/viewpage.action?pageId=4119
I got this error when i moved my EP Server to MDM Java 602 and my MDM server was at 5.5
Then i moved by EP server back to 5.5 and resolved the issue.
I hope this will help.

Similar Messages

OWB repository login error

Hi,
While connecting to the OWB design repository from OWB client the following errors are occured. This happens intermittently. Pls suggest how this can be rectified. we are using OWB 10g (10.1) and oracle 10g database.
AP10420:Error Message: Listener refused the connection with the following error
ORA-12516, TNS:listener could not find available handler with matching protocol stack.
followed by the host name and connection string
Regards
Kishan

I'm not sure I can help you, but I have some questions....
Is OWB the only software getting this error message?
If it's not, does this gives you any clue?
When you say interminttently, I understand that sometimes you can connect to database, sometimes don't. Is it true?
Does this happens since you have installed OWB or is it something recent?
Have you asked the DBA if he/she has recently changed something about db configuration? It might be related to dispatchers (multi threaded servers)...
Maybe looking for ORA-12516 in database general forum and you'll find answeres for your question.
Good luck.
Marcos

Bursting Java API throws an error javax.mail.internet.ParseException

Hi,
I am using the BurstingProcessorEngine API call send emails to the employees of an organization.
When i used the bursting file with the paramter of attachments to false, the email goes through. When i change the attachment parameter to yes in the bursting control file then program errors with an exception [oracle.apps.xdo.batch.DeliveryHelper][EXCEPTION] javax.mail.internet.ParseException
following is how i the bursting control file i have used
<?xml version="1.0" encoding="UTF-8" ?>
<xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi/" type="bursting">
<xapi:request select="/PAYSLIP_REPORT/PAYSLIP">
<xapi:delivery>
<xapi:email server="exchange.corp.rghent.com" port="25" from="[email protected]">
<xapi:message id="EMAIL1" to="${EMAIL}" content-type="text/html" attachment="true" subject="Test Email">
Hello,
Oracle Workflow
</xapi:message>
</xapi:email>
</xapi:delivery>
<xapi:document key="${EMPLOYEE_NUMBER}" output-type="PDF" output="${EMPLOYEE_NUMBER}.pdf" delivery="EMAIL1">
<xapi:template type="rtf" location="xdo://PAY.XXEPUSDEPADVXML_PDF.en.US/?getSource=true" filter="">
</xapi:template>
</xapi:document>
</xapi:request>
</xapi:requestset>

Hi,
You need to change the output-type to lower case, ie "pdf".
Regards,
Rajeev

SAP BO Data Services Repository Login error

Hi All,
I am a new SAP data services 4.0 user. I am getting following error while connecting to the repository while starting the designer.
ERROR: ODBC call <SQLDriverConnect> for data source <SERVERNAME> failed. <[Microsoft][ODBC SQL Server Driver][DBNETLIB] SSL security error>. Notify customer support. (BODI - 1112172)
However, it worked just fine initially and suddenly started throwing the above error.
Kindly help.
Regards,
Developer

I did manual registration of BODATAVIEW.ocx . Its working fine now.

Cannot add Portlets: Portal Repository - Refresh Errors

I cannot add portlets in Portal 3.0.8.
When I click the "Refresh Error" link in the Portal Repository, I get the following error:
PROVIDER[527954]: Oracle Portal Pages PORTLET[886]: TN_ORGAN LANGUAGE: s ERROR: User-Defined Exception
How do I get rid of the error?
null

The way the Refresh works is that for each provider, Oracle9i AS Portal contacts the provider for its list of portlets. It will request the list in each of the installed languages. For database providers, this call is the get_portlet_list API. For web providers, this call is the oracle.portal.provider.v1.Provider.getPortlets java API.
The error you are seeing in the refresh log is being caused by an exception raised in provider=527954,portlet=886,language=s in either the get portlets or get portlet methods. You should check these two methods with Swedish.

Error while creating user id from MDM JAVA API in 7.1 SP7

Hi,
We are trying to create user id in MDM 7.1 SP7 using JAVA API in SAP Portal. When trying to create user id, we are getting below error. If you have any solution please let us know.
com.sap.mdm.commands.CommandException: MDM repository data is out-of-date or is locked by another MDM Server. Refresh the data and try the operation again. If the error persists, contact the system administrator
Thanks,
Vinit Pugaliya

URGENT** How to change OIM user password from outside OIM

Financial Reports error message Java API can't connect to olap

Hi,
On version 11.1.1.3, after reapplication of 11.1.1.3 because of other problems with shared services, get the following message on the diagnostics for the financial reporting server.
Launch external checker with next command: E:\Hyperion\common\validation\9.5.0.0\launchEssbaseJavaAPI.bat EssbaseJAPIConnect admin ****** hypolap.msj.org http://hypapp2.msj.org:13080/aps/JAPI
Error: Result: -1; Error message: Cannot connect to olap service. Cannot connect to Essbase Server. Error:Essbase Error(1051293): Login fails due to invalid login credentials
Recommended Action: Make sure external checker is working.
Financial reports over the Web can not connect to the essbase server. Financial reports through the studio works fine. Any suggestions how to troubleshoot or resolve the issue with the login credentials for the Java API to essbase?
Anne

Things to check -
1) Does the user you specified in the connection have the role OLAP_USER
2) Does the user you specified in the connection have access to an OLAP schema (analytic workspace or CWM2 ROLAP schema)
3) Have you installed the correct JDBC files from your database instance into the BI Beans JDBC directory
Keith Laker
Oracle EMEA Consulting
BI Blog: http://oraclebi.blogspot.com/
DM Blog: http://oracledmt.blogspot.com/
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Samples: http://www.oracle.com/technology/products/bi/samples/

How do I resolve connection error with Java API listener?

I have created a listener using the new Java API (see How do I implement a listener using new MDM Java API? for background). When I run it, I get this error message
Mar 19, 2008 3:57:58 PM com.sap.mdm.internal.net.ConnectionImpl finalize
INFO: Disconnect was not called. Cleaning up connection in finalize.
This message is triggered whenever I generate a data event that I would otherwise expect to be captured and handled by the listener. I have tried a number of things, including setting the connection to NO_TIMEOUT and trying SimpleConnection versus ConnectionPool, but always with the same result.
Here is some sample code for the listener:
public class DataListenerImpl implements DataListener {
     public void recordAdded(RecordEvent evt) {
          System.out.println("===> Record Added Event");
          System.out.println(evt.getServerName());
     public void recordCheckedIn(RecordEvent evt) {
          System.out.println("===> Record Checked In Event");
          System.out.println(evt.getServerName());
     public void recordCheckedOut(RecordEvent evt) {
          System.out.println("===> Record Checked Out Event");
          System.out.println(evt.getServerName());
     public void recordModified(RecordEvent evt) {
          System.out.println("===> Record Modified Event");
          System.out.println(evt.getServerName());
And here is the code for the Event Dispatcher:
public void execute(Repository repository) {
     DataListener listener = new DataListenerImpl();
     try {
          EventDispatcherManager edm = EventDispatcherManager.getInstance();
          EventDispatcher ed = edm.getEventDispatcher(repository.getServer().getName());
          ed.addListener(listener);
          ed.registerDataNotifications(SystemProperties.getUserName(), SystemProperties.getPassword(),
                    repository.getIdentifier(), repository.getLoginRegion());
          ed.registerRepositoryNotifications(SystemProperties.getUserName(), SystemProperties.getPassword(),
                    repository.getIdentifier());
          ed.registerGlobalNotifications();
          while (true) {
               Thread.yield();
               try {
                    Thread.sleep(1500);
               } catch (InterruptedException ex) {
                    System.out.println("Interrupted Exception: " + ex.getMessage());
     } catch (ConnectionException e) {
          e.printStackTrace();
     } catch (CommandException e) {
          e.printStackTrace();
Has anyone else encountered this message? Could it be related to a TCP configuration on the server? Or is this a bug in the Java API?
As I mentioned in the forum posting linked to above, I have not encountered this problem with the MDM4J API.
Any help is greatly appreciated.

I resolved it. We are switching over to SP6, Patch 1 and the listener code works fine with this version of the Java API.
Just one thing to note, though: make sure that you register data notifications through MetadataManager in your initialization code:
metadataManager.registerDataNotifications(userSessionContext, repositoryPassword);
For information on the changes to the SP6 Java API, especially with regard to connecting to MDM with the UserSessionContext, please review Richard LeBlanc's [presentation|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20073a91-3e8b-2a10-52ae-e1b4a10add1c].

Error when trying to connect to create a new repository login

Hi,
when i try to create a new repository login in ODI 11g, I get the following error:
java.lang.NullPointerException
    at oracle.odi.ui.gallery.CreateNewOdiMasterWizard.invoke(CreateNewOdiMasterWizard.java:51)
    at oracle.ide.wizard.WizardManager.invokeWizard(WizardManager.java:372)
    at oracle.ide.wizard.WizardManager$1.run(WizardManager.java:420)
    at oracle.ide.util.IdeUtil$3.run(IdeUtil.java:1089)
    at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:642)
    at java.awt.EventQueue.access$000(EventQueue.java:85)
    at java.awt.EventQueue$1.run(EventQueue.java:603)
    at java.awt.EventQueue$1.run(EventQueue.java:601)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:612)
    at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
    at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
The weird thing is, when I tried to create the login a second time, I got the message that the login name is already in use. When I chose another name I got the same error.
Any ideas,
Thanks

If you are trying to create repository first time then delete from ODI and check SNP table(SNP_LOC_REPW) whether metadata successfully removed or not. then create again and create login for the same.
let me know your process also.
follow below link
ODI11g: Creating and Connecting to ODI Master and Work Repositories
Thanks

Error while using LiveCycle java APIs with Http servlets:"Remote EJBObject lookup failed for ejb/Inv

Hi all,
When i try to run more than one servelt of the Quick Start samples that using Livecycle Java APIs and i get an error of "Remote EJBObject lookup failed for ejb/Invocation provider" from any servelt i run.
I try some Quick samples which is not servelts (java class) and it works fine, which makes me sure that my connection properties is true.
Environment:
The LiveCycle is based on "Websphere v6.1", and i use "Eclipse Platform
Version: 3.4.1".
i install "tomcat 5.5.17" to test the servelts in developing time through Eclipse.(only for test in developing time not for deploy on )
The Jars i added in the classpath:
adobe-forms-client.jar
adobe-livecycle-client.jar
adobe-usermanager-client.jar
adobe-utilities.jar
ejb.jar
j2ee.jar
ecutlis.jar
com.ibm.ws.admin.client_6.1.0.jar
com.ibm.ws.webservices.thinclient_6.1.0.jar
server.jar
utlis.jar
wsexception.jar
My code is :
Properties ConnectionProps = new Properties();
ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_DEFAULT_EJB_ENDPOINT, "iiop://localhost:2809");
ConnectionProps.setProperty ServiceClientFactoryProperties.DSC_TRANSPORT_PROTOCOL,ServiceClientFactoryProperties.DSC_ EJB_PROTOCOL);
ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_SERVER_TYPE,ServiceClientFa ctoryProperties.DSC_WEBSPHERE_SERVER_TYPE);
ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_USERNAME, "Administrator");
ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_PASSWORD, "password");
ConnectionProps.setProperty("java.naming.factory.initial", "com.ibm.ws.naming.util.WsnInitCtxFactory");
//Create a ServiceClientFactory object
ServiceClientFactory myFactory = ServiceClientFactory.createInstance(ConnectionProps);
//Create a FormsServiceClient object
FormsServiceClient formsClient = new FormsServiceClient(myFactory);
//Get Form data to pass to the processFormSubmission method
Document formData = new Document(req.getInputStream());
//Set run-time options
RenderOptionsSpec processSpec = new RenderOptionsSpec();
processSpec.setLocale("en_US");
//Invoke the processFormSubmission method
FormsResult formOut = formsClient.processFormSubmission(formData,"CONTENT_TYPE=application/pdf&CONTENT_TYPE=app lication/vnd.adobe.xdp+xml&CONTENT_TYPE=text/xml", "",processSpec);
List fileAttachments = formOut.getAttachments();
Iterator iter = fileAttachments.iterator();
int i = 0 ;
while (iter.hasNext()) {
Document file = (Document)iter.next();
file.copyToFile(new File("C:\\Adobe\\tempFile"+i+".jp i++;
short processState = formOut.getAction();
...... (To the end of the sample)
My Error was:
com.adobe.livecycle.formsservice.exception.ProcessFormSubmissionException: ALC-DSC-031-000: com.adobe.idp.dsc.net.DSCNamingException: Remote EJBObject lookup failed for ejb/Invocation provider
at com.adobe.livecycle.formsservice.client.FormsServiceClient.processFormSubmission(FormsSer viceClient.java:416)
at HandleData.doPost(HandleData.java:62)
at HandleData.doGet(HandleData.java:31)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
a

I assume here that your application is deployed on a different physical machine of where LCES is deployed and running.
Do the following test:
- Say that LCES is deployed on machine1 and your application is deployed on machine2. Ping machine1 from machine2 and note the ip address.
- Ping machine1 from machine1 and note the ip address.
The two pings should match.
- Ping machine2 from machine1 and note the ip address.
- Ping machine2 from machine2 and note the ip address.
The two pings should match.
Usually this kind of error would happen if your servers have internal and external ip addresses.

Java API for Error Handling

There are some common error tables storing error IDs information ( IDs like error type, project id, interface id, message id etc.) in Operational Database (is not on source or target system) which we have to update using java API. We need to call java API (java code) whenever error occurs. We have to provide all the IDs to this function and then API will take care of DB updating. We can call java API in mapping program by creating user-defined java function, this will trap all the errors which are in source file as well as in mapping and mapping lookup. Query is:
A- A- Do we have any other place after the mapping to call this java API and trap the errors through it?
B- Can we call Java API using BPM and pass error IDs to it.

Hi Anand,
You Have to write Module For that(if you wanna call Java API after Mapping)at the receiver.
To write Module Here is a link which will help you in.....
==>http://help.sap.com/saphelp_nw04s/helpdata/en/84/2e3842cd38f83ae10000000a1550b0/frameset.htm
==>http://help.sap.com/saphelp_nw04s/helpdata/en/e4/6019419efeef6fe10000000a1550b0/frameset.htm
==>http://help.sap.com/saphelp_nw04s/helpdata/en/f4/0a1640a991c742e10000000a1550b0/frameset.htm
Enjoy Coding....:)
Regards,
Sundararamaprasad.

Bursting with JAVA APIs / MultiThreading / Errors Handling

We are trying to use the bursting JAVA APIs 10.1.3.3.1 Standalone) to burst huge XML files and generate PDF Files from RTF templates. Here are a list of our issues with this feature:
1. We have some problems catching the errors when bursting. We have tried to use the "oracle.apps.xdo.common.log.Logger" class, but it is not always reacting like we think it should. Could you please give us an exemple of a clean bursting error catching or a brief description of how we could do it. We have a lot of difficulties to find information about using the JAVA APIs of BIP.
2. Is it a clean way of catching the bursting errors to use the "oracle.apps.xdo.common.log.Logger" class?
3. When using the 10.1.3.3.1 DocumentProcessor JAVA API, the process gets killed when the RTF template is not where the control file specified it. Even when using a finally clause containing the document processor, we can't fetch the error from the "oracle.apps.xdo.common.log.Logger" class. We did not find a way to catch this error which make our program crash.
4. How can we enable multi-threading that is included in the DocumentProcessor JAVA APIs so it can take advantage of the multi-processors environnements?

1. Check tim d. blog, you can use the bursting listners to get the errors. It's also in the documentation.
First, on every exception, the Bursting APIs are dumping the error in the Logger. So I can't see how we can use the listeners to catch these. We can check the hasExceptions on the Logger but still, we have some problems with this. When we deploy our application as a MDB (Message driven bean), it seems that once the hasException flag has been raised, if we call the MDB again, it is still up. Is there documentation about that Logger class? Also, I'm worried that we won't be able to call our MDB twice to run simultaneously 2 different bursting process since it seems the Logger is something static, keeping every exception in memory... That's bad.. And show me where you have found documentation about this. All I see in documentation is how to call the DocumentProcessor in a couple of lines. I don't see anything about a clean way to catch errors.
2. Yes/No/Depends. I think it's fine. If your changing the logger options in your program that could come back to haunt you.
I guess so, I'm not changing anything and its already haunting me...
3. When using the 10.1.3.3.1 DocumentProcessor JAVA API, the process gets killed when the RTF template is not where the control file specified it. Even when using a finally clause containing the document processor, we can't fetch the error from the "oracle.apps.xdo.common.log.Logger" class. We did not find a way to catch this error which make our program crash.
Even worst, when we deploy the component has an MDB, when the error happens, it kills the whole oc4j container... please correct this quick.
4. How can we enable multi-threading that is included in the DocumentProcessor JAVA APIs so it can take advantage of the multi-processors environnements?
We got an answer from the dev team which is to add two properties to the document processor, something like:
enable-multithreading: true
thread-count: >2
We did that and what we got is that the process started and it got stuck in a dead lock at the first document processing. How nice! :)
We got a milestone in March and I'm really worried about all those problems... Not enough documentation, a pretty bad error handling, errors making crash the whole oc4j container, Logger seems not to be handling simultaneous calls/ threads, not even handling two subsequent calls... etc.
If anyone has the magic answer, it would be pretty welcomed!
Thanks

Uploading images whit thumbnail to MDM repository using Java API

Hello,
can someone tell me how to upload images whit thumbnail to MDM repository using Java API?
i get following message using setHasThumbnail(true):
com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: Ungültiger Wert für Parameter
thanks

You can upload images to MDM via the API, but the only way to create thumbnails is via the MDM Data Manager application which uses some embedded libraries to do the work.
Walter

MDM 7.1 SP03 Java API - setRetrieveResultCounts & taxonomy aliases = error

We just upgraded our test MDM system to 7.1 SP03 so we could use the new methods in the Java API to get result counts. However, we've run into a problem with the result counts when taxonomy aliases are being used.
The following code works when there are no taxonomy aliases defined in our MDM system, but as soon as we add any aliases, it fails:
        RetrieveLimitedRecordsCompoundCommand command = new RetrieveLimitedRecordsCompoundCommand(sessionContext);
        command.setPageIndex(pageIndex);
        command.setPageSize(pageSize);
        ResultDefinition resultDefinition = new ResultDefinition(PRODUCTS_TABLE);
        resultDefinition.addSelectField(CATALOG_NUMBER_FIELD);
        resultDefinition.addSelectField(LIST_PRICE);
        resultDefinition.addSelectField(PRODUCT_CATEGORY);
        resultDefinition.addSelectField(PRIMARY_IMAGE);
        command.setResultDefinitions(new ResultDefinition[] { resultDefinition });
        command.setRetrieveResultCounts(true);
        RecordId category = new RecordId(categoryId);
        // Set category search constraint
        if (categoryId > 0) {
               search.addSearchItem(new FieldSearchDimension(PRODUCT_CATEGORY),
                                       new PickListSearchConstraint(new MdmValue[] { new LookupValue(category) }));
        command.setSearch(search);
        command.execute();
Here is there error we get:
com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: Win32 structured exception occurred
     at com.sap.mdm.data.commands.RetrieveLimitedRecordsCompoundCommand.execute(RetrieveLimitedRecordsCompoundCommand.java:187)
     at com.baldor.mdm.Mdm.SearchProducts(Mdm.java:276)
     at com.baldor.beans.ProductSearch.search(ProductSearch.java:110)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at org.apache.el.parser.AstValue.invoke(AstValue.java:172)
     at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276)
     at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:98)
     at com.sun.faces.facelets.tag.jsf.core.DeclarativeSystemEventListener.processEvent(EventHandler.java:112)
     at javax.faces.component.UIComponent$ComponentSystemEventListenerAdapter.processEvent(UIComponent.java:2327)
     at javax.faces.event.SystemEvent.processListener(SystemEvent.java:102)
     at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:1993)
     at com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:1941)
     at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:285)
     at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:243)
     at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:114)
     at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:97)
     at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:311)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
     at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
     at java.lang.Thread.run(Unknown Source)
Caused by: com.sap.mdm.internal.protocol.manual.ServerException: Win32 structured exception occurred
     at com.sap.mdm.internal.protocol.manual.AbstractProtocolCommand.execute(AbstractProtocolCommand.java:126)
     at com.sap.mdm.data.commands.RetrieveLimitedRecordsCompoundCommand.execute(RetrieveLimitedRecordsCompoundCommand.java:183)
     ... 32 more
Exception in thread "com.sap.mdm.internal.net.ConnectionPoolBase" java.lang.NullPointerException
     at com.sap.mdm.internal.net.ConnectionPoolBase.reserveConnection(ConnectionPoolBase.java:150)
     at com.sap.mdm.internal.net.ConnectionPoolBase.reserveConnection(ConnectionPoolBase.java:130)
     at com.sap.mdm.internal.net.ConnectionPoolBase.checkAndDiscardConnections(ConnectionPoolBase.java:494)
     at com.sap.mdm.internal.net.ConnectionPoolBase.run(ConnectionPoolBase.java:556)
     at java.lang.Thread.run(Unknown Source)
Also, if I monitor the MDM system I can see the memory usage goes up more than 200MB and the CPU is pegged for 5-10 seconds before getting the error on the client.
Is there something we can do to fix this?
Thanks,
Jonathan

Sorry about the formatting of the above message - for some reason the forum pulled out all the line breaks and ignored the tags...

11G: Error invoking adf-binding service in composite with JAVA API

Hello,
i'm trying to invoke a asyncrhonous composite via JAVA API. My composite has two services: WS and ADF-BC SERVICE both of two are wired with a MEDIATOR that connects with two BPEL Process depending on two rules.
I need to invoke a process depending of the input: if the input is A i invoke the process 1 and if the input is B I invoke the process 2. I use the Mediator instead of switch because it's an example in order to build a complex decission system then.
R1 and R2 are two static rules in the Mediator.
R1 = $in.payload/client:process/client:tiposiniestro = 'A'
R2 = $in.payload/client:process/client:tiposiniestro = 'B'
And my XSD is:
<schema attributeFormDefault="unqualified"
     elementFormDefault="qualified"
     targetNamespace="http://xmlns.oracle.com/POC_jws/ProcesoApertura/ProcesoApertura"
     xmlns="http://www.w3.org/2001/XMLSchema">
<element name="process">
          <complexType>
               <sequence>
                    <element name="tiposiniestro" type="string"/>
               </sequence>
          </complexType>
     </element>
     <element name="processResponse">
          <complexType>
               <sequence>
                    <element name="result" type="string"/>
               </sequence>
          </complexType>
     </element>
</schema>
If i invoke with SOAP, sending the message:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
     <soap:Body xmlns:ns1="http://xmlns.oracle.com/POC_jws/ProcesoApertura/ProcesoApertura">
          <ns1:process>
               <ns1:tiposiniestro>A</ns1:tiposiniestro>
</ns1:process>
</soap:Body>
</soap:Envelope>
the composite works. But if i try to invoke with JAVA, with the code:
String payload5 = "<process xmlns=\"http://xmlns.oracle.com/POC_jws/ProcesoApertura/ProcesoApertura\">" +
     "     <tiposiniestro>A</tiposiniestro>" +
     "</process>";
String conversationId = UUID.randomUUID().toString();
NormalizedMessage nm = new NormalizedMessageImpl();
nm.addProperty(NormalizedMessage.PROPERTY_CONVERSATION_ID, conversationId);
Map<String,Object> payload = nm.getPayload();
payload.put("payload", pPayLoad);
nm.setPayload(payload);
service.post(pOperation, nm);
i get the following error:
Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to org.w3c.dom.Element
How can I send the message via JAVA API using the mediator in my composite?
Is there any important difference in the format between send a request with SOAP or JAVA?
Thanks in advance.
Edited by: user7239022 on 05-ene-2010 7:38
Edited by: user7239022 on 05-ene-2010 7:40
Edited by: user7239022 on 05-ene-2010 7:49
Edited by: user7239022 on 05-ene-2010 8:41

Talking about the dynamic rules in the Mediator, Oracle documentation says:
"As of now, only SOAP bindings are supported. There is a dummy SOAP binding in the composite.xml file. This endpoint is overridden by Mediator in runtime through NM property. So, outbound services can be called only over SOAP."
Is it valid for static rules as well? I means, how can i use Java API to invoke a Composite with a Mediator as first element? I always get the message:
+"java.lang.ClassCastException: java.lang.String cannot be cast to org.w3c.dom.Element"+
Thanks again

Java API: repository.login error

Similar Messages

Maybe you are looking for