Necessary settings in JBuilder to connect to SAP MI Client.
Following programs have to be installed and properly working on your computer:
<MI_Home> refers to the folder in which the Mobile Infrastructure
is installed (for example C:\ME21).
Main class | com.sap.ip.me.core.Startup |
VM parameters | -Duser.dir="<MI_Home>\webapps\me" -Dtomcat.home="<MI_Home>" |
Application parameters | -home:<MI_Home> -trace |
With this configuration JBuilder can start the Mobile Infrastructure server with the commands Run > Run Project. To see the MI start page and to test if the settings are correct, launch your web browser and enter the URL http://localhost:4444/
When Tomcat
is running in another window, shut down Tomcat before you start the Mobile Infrastructure
in JBuilder with Run > Run Project.
<Context path="/COOKBOOKEXAMPLE"
docBase="C:/MI25/CookbookExample/webapp"
debug="0" reloadable="true" />
Replace path
and docbase
parameters according
to your application name and path settings so that you can test your web-application
instantly without copying war file.When your application works properly in JBuilder you have to perform a final test your web-application’in the Mobile Infrastructure environment. To do that remove the context-entry from the server.xml file, copy your war-file into the webapps directory of your Mobile Infrastructure installation (<ME_Home>\webapps) and start the MI Client (<MI_Home>\bin\startup.bat) and start your application again.
![]() |
JBuilder uses the jar-tool from JDK 1.3.x to generate the .war and .jar files (regardless of the JDK Version setting). When the final destination of your .war file is a client with JDK 1.1.8 you have to extract the .war file generated by JBuilder (for example into a temporary folder) and repackage the file using the JDK 1.1.8 jar-tool. For details, see JDK Version Information. |