on 2018 Sep 04 7:13 PM
Most of the documents and blogs help to deploy web applications using JAVA SDK, need help if there is any detailed documentation on setting up development environment in eclipse and deploy runnable JAR for SAP BO 4.2 Platform JAVA SDK.
I have done a lot of this kind of work, so here's the basic setup that I use:
1. Add the libraries to your project's Build Path. The two attached files contain the set of .jar files that I include - there are differences between the versions here. The list for 4.1 should be valid through 4.2 SP3. For 4.2 SP4, SAP replaced all of the old security libraries with newer versions, so that list is different.
2. When creating your program, the class needs to descend from IProgram if you want to be able to run it as a program within BusinessObjects. If you're descending from IProgram, the first four arguments that get passed in the args array are UserID, Password, CMS, Authentication Type (such as secEnterprise, secLDAP, etc.)
3. For debugging, you'll go to the "Run" menu and create a debug configuration.
4. When you're finished debugging your program, right-click on the project and select "Export". Export it to a "Runnable JAR File" and select the debug configuration that you created and give the output file a name and location. I will usually select "Package required libraries into generated JAR" for exports. This makes the .jar file bigger, but I've had fewer issues with programs not being able to find the libraries when I do this.
One of the other things I've done with the programs I've written is create several classes that encapsulate the recurring tasks for using the SDK. For example, there's a BOHelper class that handles the various options for logging in and logging out of the CMS and which contains the IInfoStore that you need for running queries. Then there's a QueryHelper class that has various options for running CMS queries. It contains things like code for running a raw query, running a paged query and handling the paging, getting a single IInfoObject by name, SI_CUID, or SI_ID value, etc. This makes it so that when I have to upgrade the SDK, the majority of the code is in a single place so it's easier to find where I need to make changes.
-Dell
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
77 | |
10 | |
10 | |
10 | |
10 | |
9 | |
8 | |
7 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.