Consuming WebService with 1-to-many relationship in one request, multi MBO?

Hi
I recently have started working on SUP. I was trying to create MBO from a webservice that provides me details of an Employee like name , age , ID and address. The employee can have many adress in this case. The webservice returns all the things in one request. I need to know how to create multiple MBO from this in one request. That is when I request to the webservice the name , age , ID to goto one table and addres should be populated in a separate table with ID as the realtionship parameter in both tables.
I have connected to the webservice and can see data in preview. I had on demand cache policy with default parameter as employee ID, so it populated CDB with as many number of rows as the addres exists for the same employee which was not the desired result.
Please let me know the most efficient way to do the same.
Thanks
Preksha

I am able to consume the webservice and make multiple MBO with single call.
http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc01283.0200/doc/html/fre1249336854524.html

Similar Messages

Consume WebService with Assertion Ticket in CE 7.2

Hi masters
I am using netweaver ce 7.2 and the problem is that I just can consume webservices with User ID/Password (Basic), but I need to do that with something like Assertion Ticked (like RFC connections)
Does anybody could say me how to configure a WS connection with assertion ticked ?

I solved by myself

Problem with 1-to-many relationship between entity beans

Hi All!
I have two tables TMP_GROUP and TMP_EMPLOYEE with following fields:
TMP_GROUP: ID, CAPTION, COMMENT, STATUS.
TMP_EMPLOYEE: ID, LOGIN, GROUP_ID.
For this tables i create two entity beans GROUP and EMPLOYEE respectively.
The relationship looks like this
descriptor ejb.xml:
<ejb-relation>
            <description>description</description>
            <ejb-relation-name>employeesOfGroup</ejb-relation-name>
            <ejb-relationship-role>
                <ejb-relationship-role-name>com.mypackage.GroupBean</ejb-relationship-role-name>
                <multiplicity>One</multiplicity>
                <relationship-role-source>
                    <ejb-name>GroupBean</ejb-name>
                </relationship-role-source>
                <cmr-field>
                    <cmr-field-name>employees</cmr-field-name>
                    <cmr-field-type>java.util.Collection</cmr-field-type>
                </cmr-field>
            </ejb-relationship-role>
            <ejb-relationship-role>
                <ejb-relationship-role-name>com.mypackage.EmployeeBean</ejb-relationship-role-name>
                <multiplicity>Many</multiplicity>
                <relationship-role-source>
                    <ejb-name>EmployeeBean</ejb-name>
                </relationship-role-source>
            </ejb-relationship-role>
        </ejb-relation>
descriptor persistent.xml:
<table-relation>
               <table-relationship-role
                    key-type="PrimaryKey">
                    <ejb-name>GroupBean</ejb-name>
                    <cmr-field>employees</cmr-field>
               </table-relationship-role>
               <table-relationship-role
                    key-type="NoKey">
                    <ejb-name>EmployeeBean</ejb-name>
                    <fk-column>
                         <column-name>GROUP_ID</column-name>
                         <pk-field-name>ejb_pk</pk-field-name>
                    </fk-column>
               </table-relationship-role>
          </table-relation>
Now i implement business method:
public Long addEmployee(String login, long groupId) {
          Long result;
          try {
               EmployeeLocal employee = employeeHome.create(login);
               GroupLocal group =
                    groupHome.findByPrimaryKey(new Long(groupId));
               Collection employees = group.getEmployees();
               employees.add(employee);
               result = (Long) employee.getPrimaryKey();
          } catch (CreateException ex) {
               result = new Long(0);
          } catch (FinderException ex) {
               result = new Long(0);
          return result;
When i call this method from web service, the following exception is raised:
com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception in method com.mypackage.GroupLocalHomeImpl0.findByPrimaryKey(java.lang.Object).
P.S.
1) I have transaction attribute set to "Required" for all methods of all beans
2) I have unique index for each table:
TMP_GROUP_I1: CAPTION
TMP_EMPLOYEE_I1: LOGIN (however i think GROUP_ID must be added here too)
3) I tried many:many relationship with this tables and it works fine
4) I try another implementation of addEmployee method with
EmployeeLocal employee = employeeHome.create(login, groupId);
without using GroupLocal cmr-field and GroupLocalHome findByPrimaryKey method, the result is same error.
Can somebody help me with this problem?
Thanks in advance.
Best regards, Abramov Andrey.

gimbal2 wrote:
1: The @JoinColumn on the listOfDepartments collection in Company is wrong. It should be something like this for a bidirectional relationship:
@OneToMany(mappedBy="company") // company is the matching property name in Department
private List <Department> listOfDepartment = new ArrayList<Department>();Note that I removed the fetch configuration; onetomany is fetched lazy by design. Saves some clutter eh.
2: use a Set in stead of a List (hibernate doesn't like lists much in entities and will break when you create slightly more complex entity relations)
3: don't just slap cascades on collections, especially of type ALL. Do it with care. In the many years I've been using JPA I've only had to cascade deletes in very specific situations, maybe once or twice. I never needed any of the other cascade types, they just invite sloppy code if you ask me. When working with persistence you should apply a little precision.I made all changes as you mentioned but still compID in department table shows null value...

One-to-many relationship within one bean

hello all,
Does S1 support a container managed one-to-many relationship to itself?
I used the verifer to verify my DD and the error is reported. (this prototype is migrated from weblogic6.1 and I use the S1 migration tool for the DD generation)
-----------------database schema-----------------
CREATE TABLE t_class_a
c_name VARCHAR2(255),
one_class_a_for_ma2918_id VARCHAR2(32), /* untruncated name: one_class_a_for_many_class_a_id */
object_id VARCHAR2(32) NOT NULL
CREATE UNIQUE INDEX t_class_a_id_PK ON t_class_a ( object_id );
ALTER TABLE t_class_a ADD ( CONSTRAINT t_class_a_id_PK PRIMARY KEY ( object_id ) USING INDEX );
ALTER TABLE t_class_a ADD ( CONSTRAINT FK_0 FOREIGN KEY ( one_class_a_for_ma2918_id ) REFERENCES t_class_a ( object_id ) );
---------------------------ejb-jar.xml------------------
<abstract-schema-name>ClassABean</abstract-schema-name>
<cmp-field>
<field-name>objectId</field-name></cmp-field>
<cmp-field>
<field-name>name</field-name></cmp-field>
<primkey-field>objectId</primkey-field>
<relationships>
<ejb-relation>
<ejb-relation-name>manyClassA_oneClassA</ejb-relation-name>
<ejb-relationship-role>
<description>optional</description>
<ejb-relationship-role-name>OneClassA-in-manyClassA_oneClassA</ejb-relationship-role-name>
<multiplicity>One</multiplicity>
<relationship-role-source>
<ejb-name>ClassAEJB</ejb-name></relationship-role-source>
<cmr-field>
<cmr-field-name>manyClassAsForOneClassA</cmr-field-name>
<cmr-field-type>java.util.Collection</cmr-field-type></cmr-field></ejb-relationship-role>
<ejb-relationship-role>
<description>optional</description>
<ejb-relationship-role-name>ManyClassA-in-manyClassA_oneClassA</ejb-relationship-role-name>
<multiplicity>Many</multiplicity>
<relationship-role-source>
<ejb-name>ClassAEJB</ejb-name></relationship-role-source>
<cmr-field>
<cmr-field-name>oneClassAForManyClassA</cmr-field-name>
</cmr-field>
</ejb-relationship-role>
</ejb-relation>
</relationships>
-----------sun-cmp-mapping.xml--------
<sun-cmp-mapping>
<schema>mySchema</schema>
<entity-mapping>
<ejb-name>ClassAEJB</ejb-name>
<table-name>T_CLASS_A</table-name>
<cmp-field-mapping>
<field-name>objectId</field-name>
<column-name>OBJECT_ID</column-name></cmp-field-mapping>
<cmp-field-mapping>
<field-name>name</field-name>
<column-name>C_NAME</column-name></cmp-field-mapping>
<cmr-field-mapping>
<cmr-field-name>manyClassAsForOneClassA</cmr-field-name>
<column-pair>
<column-name>T_CLASS_A.OBJECT_ID</column-name>
<column-name>T_CLASS_A.ONE_CLASS_A_FOR_MA2918_ID</column-name></column-pair></cmr-field-mapping></entity-mapping></sun-cmp-mapping></sun-cmp-mappings>
I beleive the migration tool missing the cmr-filed mapping for the oneClassAForManyClassA relation role.
but even if I add this mapping it still can't pass the verifiy.
So do I miss any thing or I can conclude S1 not support this one-to many self relation?
Any hint would be welcome.

It does.
There is a known problem with parsing self-referenced relationship info - the one side (with <multiplicity> Many) must be the first in the <ejb-relation> entry.
Regards,
Marina

Consume Webservices with AXIS from within WebAS

I have problems invoking Web Services from within a bean running in WebAS. I am using Axis to create the calls to the WebServices.
From a WebService_A running on WebAS 6.4 I want to call WebServices both running on the same server (WebAS 6.4) and on different servers (e.g. Axis).
If in the endpoint I use the server machine's IP address, I get a server Timeout (502), if I use the machine's name I get the message "Unknown Host". Only when I call a WebService within WebAs and use "localhost" in the endpoint address, do I get the desired result.
I have already described the problem of calling a web service on a different server in the topic below,and have also tried to configure the servers proxy settings as described (which however showed no effect):
Proxy Settings for WebService invocation
As for the generation of proxies (Developer Studio generated deployable proxies) I do not know if they would work for calls on a different server (e.g. Axis), because Developer Studio for some reason would not generate the proxy for the Axis-generated WSDL file (no detailled error message). However I cannot use the generated proxies anyway, because I need to call on endpoints which are provided from a GUI, so I must do the calls by hand - or can I reset a proxy's endpoint?
Does anybody know which additional settings I have to set (Axis Engine, or in WebAS Administration?)
Every hint would be greatly appreciated.

Hi,
You don't need LCDS/FDS/BlazeDS to consume a web service. All
you need to do is to use the WebService component.
Hope this helps.

Table Design issue with 1 to many relationship

target: to match business and owner info correctly.Business will always have
id, owner is supposed to know owner id but in reality, most owner doesn't know the id. Same owner can own many different business ( ie. same owner_id but different b_id).
A rough design is like the following:
I use owner_seq to serve as a pointer for me to keep track of the business and owner relationsip. The problem is this is difficult to prevent duplicates (combination of same b_id,owner_id) from entering into table.
b_seq,owner_seq : automatic generated sequential number.
business: b_seq (not null, primary key),b_id(not null), b_owner_seq(not null),b_name(not null), b_addr,b_city,b_state,b_zip
owner:owner_seq ( not null),owner_id,owner_name(not null), owner_addr, owner_city, owner_state,owner_zip
How would you do it ? can you help ? Thank you very much.
MunSharm

fahd,
thanks for your reply.
If i am not mistaken, i think I already using sequening to serve as primary key in both tables. ( b_seq, owner_seq). with my current design, the issue I have is how to prevent duplicates with the combination of 2 tables' entries ( b_id + owner_name) since owner_no is not always available.
MunSharmi

Consuming Webservice in WebDynpro - Content-Type issue

Hi,
I am getting a shortdump when consuming WebService in WebDynpro.
I trace it back to the class CL_SOAP_HTTP_TPBND_ROOT method GET_HTTP_HEADERS whereby the
value = 'text/html; charset=iso-8859-1' while the constants tsrc_soap_11_http_content_type = 'text/xml' ; tsrc_soap_bx_http_content_type = 'application/x-sap-bxml' ; tsrc_soap_mtom_http_cont_type = 'application/xop+xml' ; tsrc_soap_mp_http_content_type = 'Multipart/Related'. Because of this Content-Type difference my WebDynpro application dumps?
Any ideas how to solve this problem?
Thanks.
Regards,
Amel

hi,
Few indroductory sessions
/people/thomas.jung/blog/2007/12/17/consuming-services-with-abap -Consuming webservices with webdynpro.
It is possible to create webservice in ABAP as well as in Webdynpro.
ABAP Webservice:
http://wiki.open-esb.java.net/Wiki.jsp?page=BAPIWEBSERVICE
http://www.sappro.com/downloads/SAPXI.pdf
Webdynpro Webservice:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/244e7923-0a01-0010-5887-fe0b0c6dbb8d
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/30f1b585-0a01-0010-3d96-ad0ea291c4f9
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/db785a70-0701-0010-858c-eee0ec4fe1b3
In Web Dynpro ABAP there is nothing special about calling a web service. Unlike WD Java, there are not dedicated model object types in WD ABAP. WD ABAP simply has the ability to interact with other ABAP development object types. You can call function modules, ABAP classes, even modules in old dynpro apps.
So calling the webservice from ABAP therefore is just the process of generating the ABAP Proxy Class. This is the same process regardless of if you want to use this proxy class from WDA or any other type of ABAP development object. You can then call the proxy class from WDA just like any other type of ABAP class. There is a service wizard option in later support package levels that includes an option for ABAP Proxy classes - although it doesn't generate the proxy class it just generates the code and context for the call to an already existing proxy class. The service wizards in WD ABAP are not required however. They are just shortcut code generators and often can't even generate a complete context for a complex web service proxy - so expect to do some manual adjustment after running the wizard.
Edited by: Mahalakshmi kothuri on Jun 1, 2008 4:17 PM

Consuming webservice in a webdynpro component

Hi Experts,
I have a third party free webservice as WSDL link.My requirement is to make use of that webservice in my webdynpro component.
Can any body give me a step by step approach to consume that webservice in my webdynpro Component.
If possible, Provide me some good material for consuming webservice in a webdynpro component.
Awaiting for a useful reply.
Thanks,
Ramanan.p

hi,
Few indroductory sessions
/people/thomas.jung/blog/2007/12/17/consuming-services-with-abap -Consuming webservices with webdynpro.
It is possible to create webservice in ABAP as well as in Webdynpro.
ABAP Webservice:
http://wiki.open-esb.java.net/Wiki.jsp?page=BAPIWEBSERVICE
http://www.sappro.com/downloads/SAPXI.pdf
Webdynpro Webservice:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/244e7923-0a01-0010-5887-fe0b0c6dbb8d
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/30f1b585-0a01-0010-3d96-ad0ea291c4f9
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/db785a70-0701-0010-858c-eee0ec4fe1b3
In Web Dynpro ABAP there is nothing special about calling a web service. Unlike WD Java, there are not dedicated model object types in WD ABAP. WD ABAP simply has the ability to interact with other ABAP development object types. You can call function modules, ABAP classes, even modules in old dynpro apps.
So calling the webservice from ABAP therefore is just the process of generating the ABAP Proxy Class. This is the same process regardless of if you want to use this proxy class from WDA or any other type of ABAP development object. You can then call the proxy class from WDA just like any other type of ABAP class. There is a service wizard option in later support package levels that includes an option for ABAP Proxy classes - although it doesn't generate the proxy class it just generates the code and context for the call to an already existing proxy class. The service wizards in WD ABAP are not required however. They are just shortcut code generators and often can't even generate a complete context for a complex web service proxy - so expect to do some manual adjustment after running the wizard.
Edited by: Mahalakshmi kothuri on Jun 1, 2008 4:17 PM

Consuming Webservice in ABAP: SoapFaultCode:1

Hi,
I have created a webservice with NetweaverDeveloperStudio and deployed it to a J2EE. I tested it with the "NDS-Webservice-Tester" and it worked fine.
I then created a proxy following the section for WebAS 640 in the weblog of Thomas Jung:
/people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap
When using the "test-interface" function in SE80 (also described in Thomas weblog) I get the following result:
<CX_AI_SYSTEM_FAULT>
<CODECONTEXT>http://www.sap.com/xml_errorcodes</CODECONTEXT>
<CODE>SoapFaultCode:1</CODE>
<ERRORTEXT>
000D6019F1DD004000000036000020D8000405473991B26F:
Found 0 operation definitions using keys:
Key name:'first-body-element-ns'
key value: 'urn:EdilogUserManagementWebserviceWsd/EdilogUserManagementWebserviceVi/document';
Key name:'SoapRequestWrapper'
key value:'getCompany';
</ERRORTEXT>
<LANGUAGE />
</CX_AI_SYSTEM_FAULT>
Any idea what might cause this error? Is there a list with the SoapErrorCodes and their specific meanings?
Thanks and regards
Jan Hempel

I solved the problem "accidentally": The name of the Webservice was to long! Changing the name from "EdilogUserManagementWebservice" to "UserManagement" did the trick.
This is probably due to the restricted fieldlength of ABAP-programnames.
Regards
Jan Hempel

Many to Many relationship betwee dimension and fact tanle

Hello Gurus,
I have a little question about many to many realtionship between fact and dimension table. The situation is as follows.
Consider there is a fact table F1 and two dimension tables D1 and D2. D1 is joined to F1 with 1 to many relationship. D1 is joined to D2 with again one to many relationship ( Note: D1:D2 = 1:N and D1:F1 = 1:N). I am able to model this by merging D1 and D2 into one dimension table in BMM layer by adding them as logical table sources and creating logical table source join. I have built simple reports and the data returnned is fine. However, I would just like to know what could be the drawbacks of such a model.
We have many other dimesions joined to the fact table and users have access to the answers that means they would could what ever report they feel like. Hence, would just like to know in what cases this model could break which means reports would give wrong data because of a many to many relationship between one of the fact and dimension table.
Thanks in advance.

Hello Copter,
Even I had modeled it by reading this link before. In the situation explained by me dimension D1 is doing the job of table Rules ( as explained in link). The model is fine.
However, my point is to undersatnd in which scenerios this model will break. As already explained, the fact table is joined to various other dimensions, there could be situations in which users select columns from various dimensions and facts randomly.
Hence, which are the scenerios where I might get erroneous counts of meassures. Further, if someone feels this model is correct and would not break in any scenerio then please reply.

Async webservice with Callback

Hi Experts,
How to call a Asynchronous Microsoft webservice(Used callback mechanism) from XI?
First I have to call the Microsoft webservice, it will return acknowledgement about the status. Again I have to invoke the webservice then it(microsoft) will return the response.
How to do the above steps using XI? Please share your suggestions
Regards
Sara

Hi Sara,
Major thing is if ur webservice accepts some data and gives some response, then both input and output should get imported into XI as seperate message types (Under Messages Tab) as shown in step 1 of ur referred weblog
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
So there u must have 2 messages: 1 for request and 1 for response. This depends upon ur wsdl structure. Once u get these messages, u could proceed with ur message mapping
Steps are,
1.import the wsdl file in Integration Repository in Integration Objects->external definitions.
2.then create message types using the imported WSDL request and response.
3.Other things are as usual.
using SAP XI we can easily connect to webservices pls chk the links
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00c36ef6-dab9-2910-6ca9-a96b820de582
/people/yomeshp.sharma/blog/2006/05/31/integrating-jdedwards-system-with-xi-using-iway-adapter-part--iii
/people/anton.wenzelhuemer/blog/2006/03/05/integrating-php-and-abap-using-webservices
/people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap
http://help.sap.com/saphelp_nwpi71/helpdata/en/11/e8179b247e4720882512a04041491d/frameset.htm
Regards,
Vinod.

Create web service consumer client with Ant and wsdl

How can I create a web service client with just Ant and WSDL?
Thanks.

Hi,
Did you check this web log?
/people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap
Eddy

One to many relationships

Hi I have a big problem :)
I want to use one to many relationships.
One yable with primary key, foreign key view_id. The second table on the many side with primary key view_id and another primary key.
The problem is that ejbc gives the followin error:
" [java] In relationship 'ViewType-SView', role 'ViewType-Has-SView', a weblogic-relationship-role element contains the wrong number of column mappings. A single column mapping must be given for each primary key column in the bean referenced by the mapping."
And that makes no sense for me. Any ideas?

weblogic-relationship-role element column mappings should be the same as defined in
<ejb-relationship-role>
<multiplicity></multiplicity>
</ejb-relationship-role>
Erno wrote:
Hi I have a big problem :)
I want to use one to many relationships.
One yable with primary key, foreign key view_id. The second table on the many side with primary key view_id and another primary key.
The problem is that ejbc gives the followin error:
" [java] In relationship 'ViewType-SView', role 'ViewType-Has-SView', a weblogic-relationship-role element contains the wrong number of column mappings. A single column mapping must be given for each primary key column in the bean referenced by the mapping."
And that makes no sense for me. Any ideas?

Defining a many-to-many relationship with CMP EJBs : does it work for you

Curious to know whether someone has been able to set up a many to many relationship between two entity beans.
I have been struggling with this for days now and I can't get it to work.
In my test project I have two entity beans, resp. Consultant and Solution.
Consultant has a cmr field called 'solutions', which is a collection object from the opposite side (Solution).
This is the source of the ejb-jar.xml file
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
     <description>EJB JAR description</description>
     <display-name>EJB JAR</display-name>
     <enterprise-beans>
          <session>
               <ejb-name>ProfilerBean</ejb-name>
               <home>com.atosorigin.tcc.testing.ejbses.profiling.ProfilerHome</home>
               <remote>com.atosorigin.tcc.testing.ejbses.profiling.Profiler</remote>
               <local-home>com.atosorigin.tcc.testing.ejbses.profiling.ProfilerLocalHome</local-home>
               <local>com.atosorigin.tcc.testing.ejbses.profiling.ProfilerLocal</local>
               <ejb-class>com.atosorigin.tcc.testing.ejbses.profiling.ProfilerBean</ejb-class>
               <session-type>Stateless</session-type>
               <transaction-type>Container</transaction-type>
               <ejb-local-ref>
                    <ejb-ref-name>EJBTesting/Solution</ejb-ref-name>
                    <ejb-ref-type>Entity</ejb-ref-type>
                    <local-home>com.atosorigin.tcc.testing.ejbcmp.profiling.SolutionLocalHome</local-home>
                    <local>com.atosorigin.tcc.testing.ejbcmp.profiling.SolutionLocal</local>
                    <ejb-link>SolutionBean</ejb-link>
               </ejb-local-ref>
               <ejb-local-ref>
                    <ejb-ref-name>EJBTesting/Consultant</ejb-ref-name>
                    <ejb-ref-type>Entity</ejb-ref-type>
                    <local-home>com.atosorigin.tcc.testing.ejbcmp.profiling.ConsultantLocalHome</local-home>
                    <local>com.atosorigin.tcc.testing.ejbcmp.profiling.ConsultantLocal</local>
                    <ejb-link>ConsultantBean</ejb-link>
               </ejb-local-ref>
          </session>
          <entity>
               <ejb-name>ConsultantBean</ejb-name>
               <home>com.atosorigin.tcc.testing.ejbcmp.profiling.ConsultantHome</home>
               <remote>com.atosorigin.tcc.testing.ejbcmp.profiling.Consultant</remote>
               <local-home>com.atosorigin.tcc.testing.ejbcmp.profiling.ConsultantLocalHome</local-home>
               <local>com.atosorigin.tcc.testing.ejbcmp.profiling.ConsultantLocal</local>
               <ejb-class>com.atosorigin.tcc.testing.ejbcmp.profiling.ConsultantBean</ejb-class>
               <persistence-type>Container</persistence-type>
               <prim-key-class>java.lang.String</prim-key-class>
               <reentrant>False</reentrant>
               <cmp-version>2.x</cmp-version>
               <abstract-schema-name>Consultant</abstract-schema-name>
               <cmp-field>
                    <field-name>firstname</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>lastname</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>country</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>id</field-name>
               </cmp-field>
               <primkey-field>id</primkey-field>
               <query>
                    <query-method>
                         <method-name>findBySolution</method-name>
                         <method-params>
                              <method-param>java.lang.String</method-param>
                         </method-params>
                    </query-method>
                    <ejb-ql>SELECT Object(c) FROM Consultant AS c,
                    IN(c.solutions) s WHERE s.id = ?1 </ejb-ql>
               </query>
          </entity>
          <entity>
               <ejb-name>SolutionBean</ejb-name>
               <home>com.atosorigin.tcc.testing.ejbcmp.profiling.SolutionHome</home>
               <remote>com.atosorigin.tcc.testing.ejbcmp.profiling.Solution</remote>
               <local-home>com.atosorigin.tcc.testing.ejbcmp.profiling.SolutionLocalHome</local-home>
               <local>com.atosorigin.tcc.testing.ejbcmp.profiling.SolutionLocal</local>
               <ejb-class>com.atosorigin.tcc.testing.ejbcmp.profiling.SolutionBean</ejb-class>
               <persistence-type>Container</persistence-type>
               <prim-key-class>java.lang.String</prim-key-class>
               <reentrant>False</reentrant>
               <cmp-version>2.x</cmp-version>
               <abstract-schema-name>Solution</abstract-schema-name>
               <cmp-field>
                    <field-name>description</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>name</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>parent</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>id</field-name>
               </cmp-field>
               <primkey-field>id</primkey-field>
               <query>
                    <query-method>
                         <method-name>findChildSolutions</method-name>
                         <method-params>
                              <method-param>java.lang.String</method-param>
                         </method-params>
                    </query-method>
                    <ejb-ql>SELECT Object(s) FROM Solution AS s WHERE
                    s.parent = ?1</ejb-ql>
               </query>
               <query>
                    <query-method>
                         <method-name>findTopLevelSolutions</method-name>
                         <method-params/>
                    </query-method>
                    <ejb-ql>Select Object(s) FROM Solution AS s WHERE
                    (s.parent = 'none')</ejb-ql>
               </query>
          </entity>
     </enterprise-beans>
     <relationships>
          <ejb-relation>
               <description>A consultant may have one or more areas of expertise</description>
               <ejb-relation-name>Consultant_Solutions</ejb-relation-name>
               <ejb-relationship-role>
                    <ejb-relationship-role-name>com.atosorigin.tcc.testing.ejbcmp.profiling.ConsultantBean</ejb-relationship-role-name>
                    <multiplicity>Many</multiplicity>
                    <relationship-role-source>
                         <ejb-name>ConsultantBean</ejb-name>
                    </relationship-role-source>
                    <cmr-field>
                         <cmr-field-name>solutions</cmr-field-name>
                         <cmr-field-type>java.util.Collection</cmr-field-type>
                    </cmr-field>
               </ejb-relationship-role>
               <ejb-relationship-role>
                    <ejb-relationship-role-name>com.atosorigin.tcc.testing.ejbcmp.profiling.SolutionBean</ejb-relationship-role-name>
                    <multiplicity>Many</multiplicity>
                    <relationship-role-source>
                         <ejb-name>SolutionBean</ejb-name>
                    </relationship-role-source>
               </ejb-relationship-role>
          </ejb-relation>
     </relationships>
     <assembly-descriptor>
          <container-transaction>
               <description>container-transaction</description>
               <method>
                    <ejb-name>SolutionBean</ejb-name>
                    <method-name>*</method-name>
               </method>
               <method>
                    <ejb-name>ProfilerBean</ejb-name>
                    <method-name>*</method-name>
               </method>
               <method>
                    <ejb-name>ConsultantBean</ejb-name>
                    <method-name>*</method-name>
               </method>
               <trans-attribute>Required</trans-attribute>
          </container-transaction>
     </assembly-descriptor>
</ejb-jar>
I created a stateless session bean as a business facade for the two entity beans. I then created a webservice to test the beans.
What works :
- create a consultant
- get a consultant
- create a solution
- get a solution
(basically everything that doesn't involve the relationship field.
However, what doesn't work is the method call assignSolution:
- assign solution : this is implemented as follows
Business Method.
     public void assignSolution(String consultantID, String solutionID)
          throws ProfilingException {
          // TODO : Implement
          ConsultantLocal cons = null;
          SolutionLocal sol = null;
          try {
               cons = consHome.findByPrimaryKey(consultantID);
               sol = solHome.findByPrimaryKey(solutionID);
               Collection solutions = cons.getSolutions();
               solutions.add(sol);
               //sol.getConsultants().add(cons);
          } catch (FinderException ex) {
               ex.printStackTrace();
               throw new ProfilingException("failed to retrieve data from DB", ex);
As you can see I am trying to use the CM Relationship in this methhod. Adding the solution to a consultant should be as simple as adding a solution object to the collection retrieved with the getSolutions accessor. The Container is expected to persist the information in my MAXDB database.
However this doesn't happen.
The ORM details as defined in the persistent.xml follows :
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE persistent-ejb-map SYSTEM "persistent.dtd">
<persistent-ejb-map>
     <locking
          type="Table"/>
     <db-properties>
          <data-source-name>TCC_PORTAL_PROFILER</data-source-name>
          <database-vendor
               name="SAPDB"/>
     </db-properties>
     <entity-beans>
          <entity-bean>
               <ejb-name>ConsultantBean</ejb-name>
               <table-name>PFL_CONSULTANTS</table-name>
               <field-map
                    key-type="NoKey">
                    <field-name>firstname</field-name>
                    <column>
                         <column-name>FIRSTNAME</column-name>
                    </column>
               </field-map>
               <field-map
                    key-type="NoKey">
                    <field-name>lastname</field-name>
                    <column>
                         <column-name>LASTNAME</column-name>
                    </column>
               </field-map>
               <field-map
                    key-type="NoKey">
                    <field-name>country</field-name>
                    <column>
                         <column-name>COUNTRY</column-name>
                    </column>
               </field-map>
               <field-map
                    key-type="PrimaryKey">
                    <field-name>id</field-name>
                    <column>
                         <column-name>ID</column-name>
                    </column>
               </field-map>
               <finder-descriptor>
                    <method-name>findBySolution</method-name>
                    <method-params>
                         <method-param>java.lang.String</method-param>
                    </method-params>
                    <load-selected-objects
                         lock="read"/>
               </finder-descriptor>
          </entity-bean>
          <entity-bean>
               <ejb-name>SolutionBean</ejb-name>
               <table-name>PFL_SAPSOLUTIONS</table-name>
               <field-map
                    key-type="NoKey">
                    <field-name>description</field-name>
                    <column>
                         <column-name>DESCRIPTION</column-name>
                    </column>
               </field-map>
               <field-map
                    key-type="NoKey">
                    <field-name>name</field-name>
                    <column>
                         <column-name>NAME</column-name>
                    </column>
               </field-map>
               <field-map
                    key-type="NoKey">
                    <field-name>parent</field-name>
                    <column>
                         <column-name>PARENTID</column-name>
                    </column>
               </field-map>
               <field-map
                    key-type="PrimaryKey">
                    <field-name>id</field-name>
                    <column>
                         <column-name>ID</column-name>
                    </column>
               </field-map>
               <finder-descriptor>
                    <method-name>findChildSolutions</method-name>
                    <method-params>
                         <method-param>java.lang.String</method-param>
                    </method-params>
                    <load-selected-objects
                         lock="read"/>
               </finder-descriptor>
               <finder-descriptor>
                    <method-name>findTopLevelSolutions</method-name>
                    <method-params/>
                    <load-selected-objects
                         lock="read"/>
               </finder-descriptor>
          </entity-bean>
     </entity-beans>
     <relationships>
          <table-relation>
               <help-table>PFL_CONS_SOL_MAP</help-table>
               <table-relationship-role
                    key-type="PrimaryKey">
                    <ejb-name>ConsultantBean</ejb-name>
                    <cmr-field>solutions</cmr-field>
                    <fk-column>
                         <column-name>CONSULTANTID</column-name>
                         <pk-field-name>id</pk-field-name>
                    </fk-column>
               </table-relationship-role>
               <table-relationship-role
                    key-type="PrimaryKey">
                    <ejb-name>SolutionBean</ejb-name>
                    <fk-column>
                         <column-name>SOLUTIONID</column-name>
                         <pk-field-name>id</pk-field-name>
                    </fk-column>
               </table-relationship-role>
          </table-relation>
     </relationships>
</persistent-ejb-map>
The error in the default trace file when calling the method states, there is an "inconsistency in the number of primary keys". Details follow.
#1.5#000F1F188E5C004400000000000010480003E76C80EFD57A#1098880364327#com.sap.engine.services.ejb#com.atosorigin.tcc/EJBCMPProfilingTest#com.sap.engine.services.ejb#Guest#2####4d2b2370281411d9a40d000f1f188e5c#SAPEngine_Application_Thread[impl:3]_31##0#0#Error##Java###
[EXCEPTION]
#1#com.sap.engine.services.ejb.exceptions.BaseRemoteException: Exception in method assignSolution.
     at com.atosorigin.tcc.testing.ejbses.profiling.ProfilerObjectImpl0.assignSolution(ProfilerObjectImpl0.java:822)
     at com.atosorigin.tcc.testing.ejbses.profiling.Profiler_Stub.assignSolution(Profiler_Stub.java:533)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
     at $Proxy73.assignSolution(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:146)
     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:68)
     at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
     at SoapServlet.doPost(SoapServlet.java:51)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     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:339)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:317)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:810)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:238)
     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)
Caused by: com.sap.engine.services.applocking.exception.SAPAppLockingIllegalArgumentException: Inconsistency in number of primary keys
     at com.sap.engine.services.applocking.TableLockingImpl.getArgument(TableLockingImpl.java:385)
     at com.sap.engine.services.applocking.TableLockingImpl.lock(TableLockingImpl.java:128)
     at com.sap.engine.services.applocking.TableLockingImpl.lock(TableLockingImpl.java:138)
     at com.sap.engine.services.ejb.entity.pm.lock.TableLockingSystem.write(TableLockingSystem.java:82)
     at com.sap.engine.services.ejb.entity.pm.PersistentM2M.create(PersistentM2M.java:172)
     at com.sap.engine.services.ejb.entity.pm.PersistentCacheM2M.add(PersistentCacheM2M.java:197)
     at com.sap.engine.services.ejb.entity.pm.multiple.CollectionM2M.add(CollectionM2M.java:57)
     at com.atosorigin.tcc.testing.ejbses.profiling.ProfilerBean.assignSolution(ProfilerBean.java:201)
     at com.atosorigin.tcc.testing.ejbses.profiling.ProfilerObjectImpl0.assignSolution(ProfilerObjectImpl0.java:771)
     ... 32 more
I can't figure out what the problem is with the ORM mapping defined.
On the database level I have three tables. Consultant maps to PFL_CONSULTANT, Solution to PFL_SAPSOLUTIONS. The third table PFL_CONS_SOL_MAP is the help table used for the relationship (having two fields, which are in fact foreign keys from the other two tables to express the assignment of solutions to consultants (where a consultant can have one or more solutions).
ps. : I am running Netweaver Developer Workplace (Netweaver 2004, at stack level 5)
Message was edited by: Theo Paesen

Hm, after disabling 'automatic locking' it works.

Problem with 1:many relationship between entity beans.

Hi All!
I have two tables TMP_GROUP and TMP_EMPLOYEE with following fields:
TMP_GROUP: ID, CAPTION, COMMENT, STATUS.
TMP_EMPLOYEE: ID, LOGIN, GROUP_ID.
For this tables i create two entity beans GROUP and EMPLOYEE respectively.
The relationship looks like this
descriptor ejb.xml:
<ejb-relation>
            <description>description</description>
            <ejb-relation-name>employeesOfGroup</ejb-relation-name>
            <ejb-relationship-role>
                <ejb-relationship-role-name>com.mypackage.GroupBean</ejb-relationship-role-name>
                <multiplicity>One</multiplicity>
                <relationship-role-source>
                    <ejb-name>GroupBean</ejb-name>
                </relationship-role-source>
                <cmr-field>
                    <cmr-field-name>employees</cmr-field-name>
                    <cmr-field-type>java.util.Collection</cmr-field-type>
                </cmr-field>
            </ejb-relationship-role>
            <ejb-relationship-role>
                <ejb-relationship-role-name>com.mypackage.EmployeeBean</ejb-relationship-role-name>
                <multiplicity>Many</multiplicity>
                <relationship-role-source>
                    <ejb-name>EmployeeBean</ejb-name>
                </relationship-role-source>
            </ejb-relationship-role>
        </ejb-relation>
descriptor persistent.xml:
<table-relation>
               <table-relationship-role
                    key-type="PrimaryKey">
                    <ejb-name>GroupBean</ejb-name>
                    <cmr-field>employees</cmr-field>
               </table-relationship-role>
               <table-relationship-role
                    key-type="NoKey">
                    <ejb-name>EmployeeBean</ejb-name>
                    <fk-column>
                         <column-name>GROUP_ID</column-name>
                         <pk-field-name>ejb_pk</pk-field-name>
                    </fk-column>
               </table-relationship-role>
          </table-relation>
Now i implement business method:
public Long addEmployee(String login, long groupId) {
          Long result;
          try {
               EmployeeLocal employee = employeeHome.create(login);
               GroupLocal group =
                    groupHome.findByPrimaryKey(new Long(groupId));
               Collection employees = group.getEmployees();
               employees.add(employee);
               result = (Long) employee.getPrimaryKey();
          } catch (CreateException ex) {
               result = new Long(0);
          } catch (FinderException ex) {
               result = new Long(0);
          return result;
When i call this method from web service, the following exception is raised:
com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception in method com.mypackage.GroupLocalHomeImpl0.findByPrimaryKey(java.lang.Object).
P.S.
1) I have transaction attribute set to "Required" for all methods of all beans
2) I have unique index for each table:
TMP_GROUP_I1: CAPTION
TMP_EMPLOYEE_I1: LOGIN (however i think GROUP_ID must be added here too)
3) I tried many:many relationship with this tables and it works fine
4) I try another implementation of addEmployee method with
EmployeeLocal employee = employeeHome.create(login, groupId);
without using GroupLocal cmr-field and GroupLocalHome findByPrimaryKey method, the result is same error.
Can somebody help me with this problem?
Thanks in advance.
Best regards, Abramov Andrey.

I have posted excerpts from my orion-ejb-jar.xml file in this posting: Problem mapping a 1:M relationship between two entity EJBs w/ a compound PK
Sorry for the duplicate postings, but I was getting errors on the submission.
April

Consuming WebService with 1-to-many relationship in one request, multi MBO?

Similar Messages

Maybe you are looking for