Skip to Content

<body><p> </p>   <p>This blog gives an adumbrate of the rudimentary steps that have to be done in Netweaver Developer studio before writing the Java application which invokes the proxy call for Client Java Proxy. </p><p>Data types, Message types and Outbound Synchronous message interfaces are created in Integration Repository.</p><p>In Integration Repository right click on the Outbound Synchronous interface and choose the Generate Java Proxy option from the context menu which creates the following java class files for synchronous interface</p><p> </p><p><DataTypeRequest>_Type.java</p><p><DataTypeResponse>_Type.java</p><p><MessageInterface>_PortType.java</p><p><MessageInterface>_PortTypeBean.java</p><p><MessageInterface>_PortTypeHome.java</p><p><MessageInterface>_PortTypeLocal.java</p><p><MessageInterface>_PortTypeLocalHome.java</p><p><MessageInterface>_PortTypeRemote.java</p><p> </p><p>1. In NetWeaver Developer Studio create new EJB module Project. Choose the project -> Properties and then Java Build path -> add these libraries to the EJB Module Project</p><p> </p><ul><li>aii_proxy_xirt.jar</li><li>aii_msg_runtime.jar</li><li>aii_utilxi_misc.jar</li><li>guidgenerator.jar</li></ul><p> </p><p>Note : You can find above libraries under the path C:\usr\sap\J2E\JC00\j2ee\cluster\server0\bin\ext</p><p> </p><p>Once the jar files are added EJB Candidates are available.</p><p> </p><p>              !https://weblogs.sdn.sap.com/weblogs/images/251806397/1.JPG|height=182|alt=|width=220|src=https://weblogs.sdn.sap.com/weblogs/images/251806397/1.JPG|border=0!</p><p>  </p><p style=”margin: 0in 0in 0pt 0.25in; text-indent: -0.25in; tab-stops: list .25in” class=”MsoNormal”>2.  Choose import from the File menu, in the next screen choose zip file then select the Generated Java Proxies from Integration Repository under EJB Module.</p><p> </p><p>In Java Explorer close the project and Open it again to reflect the addition of Proxies in the EJB Class. The Proxy bean class appears under EJB Candidate. !https://weblogs.sdn.sap.com/weblogs/images/251806397/2.JPG|height=1|alt=|width=1|src=https://weblogs.sdn.sap.com/weblogs/images/251806397/2.JPG|border=0!  </p><p> </p><p>               !https://weblogs.sdn.sap.com/weblogs/images/251806397/2.JPG|height=1|alt=|width=1|src=https://weblogs.sdn.sap.com/weblogs/images/251806397/2.JPG|border=0!!https://weblogs.sdn.sap.com/weblogs/images/251806397/2.JPG|height=204|alt=|width=239|src=https://weblogs.sdn.sap.com/weblogs/images/251806397/2.JPG|border=0!</p><p>3.  Right Click the Proxy Bean and select Add to ejb-jar.xml then Proxy Bean is added to ejb-jar.xml.</p><p> </p><p>                  !https://weblogs.sdn.sap.com/weblogs/images/251806397/3.JPG|height=104|alt=|width=237|src=https://weblogs.sdn.sap.com/weblogs/images/251806397/3.JPG|border=0!       </p><p style=”margin: 0in 0in 0pt 0.25in; text-indent: -0.25in; tab-stops: list .25in” class=”MsoNormal”>4.  Open ejb-j2ee-engine.xml in that under Session Bean you can find the Proxy bean that has been added to the ejb-jar.xml.</p><p style=”margin: 0in 0in 0pt 0.25in; text-indent: -0.25in; tab-stops: list .25in” class=”MsoNormal”> </p>5.   Double click the proxy bean and Enter a valid JNDI name(this JNDI Name is used by the java application after deploying for identifying the jars)      <p>              </p><p>!https://weblogs.sdn.sap.com/weblogs/images/251806397/4.JPG|height=355|alt=|width=458|src=https://weblogs.sdn.sap.com/weblogs/images/251806397/4.JPG|border=0!</p><p style=”margin: 0in 0in 0pt” class=”MsoNormal”>                      Save the Process. </p><p style=”margin: 0in 0in 0pt” class=”MsoNormal”> </p><p style=”margin: 0in 0in 0pt” class=”MsoNormal”>6.  After this Right click the Project -> Choose Build EJB Archive from context menu which builds the jar file <ProjectName>.jar   </p><p style=”margin: 0in 0in 0pt” class=”MsoNormal”> </p><p style=”margin: 0in 0in 0pt” class=”MsoNormal”> </p><p style=”margin: 0in 0in 0pt” class=”MsoNormal”>              !https://weblogs.sdn.sap.com/weblogs/images/251806397/5.JPG|height=1|alt=|width=1|src=https://weblogs.sdn.sap.com/weblogs/images/251806397/5.JPG|border=0!!https://weblogs.sdn.sap.com/weblogs/images/251806397/5.JPG|height=111|alt=|width=176|src=https://weblogs.sdn.sap.com/weblogs/images/251806397/5.JPG|border=0! </p><p style=”margin: 0in 0in 0pt” class=”MsoNormal”> </p><p style=”margin: 0in 0in 0pt 0.25in; text-indent: -0.25in; tab-stops: list .25in” class=”MsoNormal”>     </p><p>7.  Create New Enterprise Application Project with EJB module project as its reference.  </p><p> </p><p>           !https://weblogs.sdn.sap.com/weblogs/images/251806397/6.JPG|height=215|alt=|width=222|src=https://weblogs.sdn.sap.com/weblogs/images/251806397/6.JPG|border=0!  </p><p style=”margin: 0in 0in 0pt” class=”MsoNormal”>   </p><p style=”margin: 0in 0in 0pt” class=”MsoNormal”> </p><p>          A New enterprise Application Project is Created like this  </p><p> </p><p style=”margin: 0in 0in 0pt” class=”MsoNormal”>                   !https://weblogs.sdn.sap.com/weblogs/images/251806397/7.JPG|height=56|alt=|width=192|src=https://weblogs.sdn.sap.com/weblogs/images/251806397/7.JPG|border=0!</p><p style=”margin: 0in 0in 0pt” class=”MsoNormal”> </p><p>8.  Add the following Source code to the application-j2ee-engine.xml </p><p> </p><p style=”margin: 0in 0in 0pt” class=”MsoNormal”> </p><p style=”margin: 0in 0in 0pt” class=”MsoNormal”><application-j2ee-engine></p><p><reference  reference-type=”weak”><br /><reference-target provider-name=”sap.com” target-type=”library”>com.sap.aii.proxy.xiruntime</reference-target><br /></reference></p><p><br /><reference  reference-type=”weak”><br /><reference-target provider-name=”sap.com”  target-type=”library”>com.sap.aii.messaging.runtime</reference-target><br /></reference></p><p><br /><reference  reference-type=”weak”><br /><reference-target  provider-name=”sap.com”  target-type=”library”>com.sap.xi.util.misc</reference-target><br /></reference></p><p><br /><reference  reference-type=”weak”><br /> <reference-target  provider-name=”sap.com”  target-type=”library”>com.sap.guid</reference-target><br /></reference></p><p><br /><provider-name>sap.com</provider-name><br /><fail-over-enable mode=”disable” /><br /></application-j2ee-engine></p><p>      Save the process. </p><p> </p><p>9.    Right click the Enterprise Application Project  -> Choose Build Application Archive from context menu which generates the ear file < EnterpriseApplicationProjectName>.ear </p><p> </p><p style=”margin: 0in 0in 0pt” class=”MsoNormal”>                !https://weblogs.sdn.sap.com/weblogs/images/251806397/8.JPG|height=74|alt=|width=197|src=https://weblogs.sdn.sap.com/weblogs/images/251806397/8.JPG|border=0!</p><p style=”margin: 0in 0in 0pt” class=”MsoNormal”> </p><p>10.       Finally Right click on the ear file and Choose Deploy to J2EE engine. </p><p> </p><p>                  !https://weblogs.sdn.sap.com/weblogs/images/251806397/9.JPG|height=134|alt=|width=237|src=https://weblogs.sdn.sap.com/weblogs/images/251806397/9.JPG|border=0!</body>

To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. Michal Krawczyk
    Hi,

    please make sure you check the previous content
    as we already have articles about the same subject:

    part 1
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9

    part 2
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d

    or at least add them to your blog and show the dirrecencies if there are many – this way your blog will add some value and not just be the same thing with new blogger name

    thank you very much,

    Regards,
    michal

    (0) 
    1. Yugapreetha T Post author
      Hi Michal,

      Last month only I did’t this java proxt sceanrio for that I gone through the above documents.I feel that for beginner the article is bit difficult to follow.

      More over in that article they discussed more about Design and configuration part rather than the steps that to be followed in NWDS part.
      As an XI consultant any one can do the Design and Configuration in Integration builder.

      This is the reason I came up with this blog which gives the flow more clearly compared to that article.

      This blog definitely will guide more from the XI beginners perspective.

      (0) 
      1. Michal Krawczyk
        no problem so next time
        just include links to the previous doc
        and exaplain why you post something similar – but different from another point of view 🙂

        then your blog will be more complete 🙂

        Regards,
        michal

        (0) 
  2. Ramohan Rao
    Hi, i found this is one of the best blog which shows the work to be done in NWDS…., Really useful for beginers….
    if you are able to provide the sample java application to invoke proxy,then it will be great help for beginers of xi.
    (0) 

Leave a Reply