Additional Blogs by Members
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member
0 Kudos


BEA Weblogic Server and SAP Integration






For the integration of Weblogic Server applications to access/update data from SAP basically there are 2 methods







    • Using the data engine.






    • The steps involved in the configuration and usage of the Adapters and Data engine is described below.





Adapters for SAP from BEA


















4. Once the details are provided and saved, in the left side tree, a node with the system name (as per the value entered for system name) will be shown below SAP as the main node.







5. Select the new system added and from the right side panel right click & choose, “Test Connection” and provide the password of the SAP user and below SAP comes, 3 nodes – BAPIs, Remote Function Modules & IDoc Interfaces.






















6. Select the relevant BAPI/FM and right click to do a test run and can be tested whether its working as per our requirement and its also a confirmation that the data is flowing to and fro from BEA to SAP and vice versa.







7. Once the testing is done and confirmed, right click on the right hand side panel and generate the XML schema. This will generate a request and response schema.







8. Once this schema files are saved into the Schema folder configured for the BEA Workshop (IDE for developing Java applications for BEA Weblogic server), the building of the schema will happen and the XML bean will be generated which can be used in the application project.







Data Engine







1. Create a new schema in the Oracle DB which is used for the creation/change of the cross reference tables for each SAP module application that are being built.







2. Next step is to configure the BEA data engine, with the ip address, name of the SAP system, user id and password (Here make sure that we are using a CPIC or a background user).







3. Once the data engine is configured, the mapping of the user id has to be done. This is the mapping of the Portals user id with the SAP user id.







4. The final step is that for each and every functionality that is being implemented, create a mapping object by providing the BAPI/RFC FM name and creation of the fields or structures or tables as per the input/output configuration done in the SAP side for these parameters in the BAPI/RFC FM. Here the kind of usage for the BAPI/RFC FM has to be mentioned – Display/Update.







STEP 1:
Click “Setup EIS Object Preferences”











STEP 2:
Select “SAP46C” and click “Search”.










This will list all the available portlets in the selected EIS Application.





STEP 3:
Click “Add New Portlet” to create a new Portlet for the SAP BAPI/RFC Function module.











STEP 4:
Enter the Portlet Name and click “Submit”.











STEP 5:
The newly created portlet is listed as shown below.










Click on the (highlighted) Portlet Name. This will display the list of BAPI/RFC Function module available for the given portlet.





STEP 6:
To create a new BAPI, click “Add New Bapi”.











STEP 7:
Enter the “BAPI Name”, select the “Purpose” and click “Submit”.










This will list all the available parameters for the selected BAPI.





STEP 8:
To add a new edit parameter, click “Add New Edit Display Parameter”.











STEP 9:
Select the “Edit Display Type” – INPUT/OUTPUT depending on the usage of the edit parameter.
Select the “Sub Type” – SCALAR/TABLE/STRUCT depending on the type of the edit parameter. Click “Submit”.











STEP 10:
If the Edit Display Parameter selected in Step 9, is a structure, provide the Structure Name and click “Submit”.











STEP 11:
The newly added Edit Display Parameter is listed as shown below.










To create further Edit Display Parameter (Input/Output), follow step steps 8-11. To add a new field in the STRUCTURE/TABLE, click on the highlighted icon





STEP 12:
This will list all the available fields in the STRUCTURE/TABLE.To add a new Edit Display Structure/Table Parameter, click “Add New Edit Display Table Parameters”.











STEP 13:
Provide values for “Field Name”, “Mandatory”, “Label Name”, “Default Value” (if any), “Data Type” and “User Type”. Click “Submit”.











STEP 14:
The newly created Structure/Table field will be listed as shown in the figure below.










To add other Structure/Table fields, follow steps 12-14.





STEP 15:
To create a new SCALAR Field, in Step 9, choose “Sub Type” as “SCALAR”. Select Edit Display Type as INPUT/OUTPUT, depending on the usage.











STEP 16:
Provide the values for “Field Name”, “Mandatory”, “Data Type”, “Label Name”, “Hidden Status”. Check the EMPLOYEE/CUSTOMER checkboxes, if the Portlet is required to be visible to the respective user chosen.











STEP 17:
The input/output and Edit/Display parameters for a given BAPI/RFC Function Module will be listed as shown below.










This completes SAP BAPI/RFC Function Module – Portlet Mapping.





5. This mapping will generate a unique id for each and every field in the BAPI/RFC mapping and this id has to be referred when the data retrieval or update is done. The next step is to verify the mapping entries in the portal database.



Verification of Mapping in Portal Database










The following steps will be done thru the BEA Workshop (IDE for the development of java applications) for the accessing of the data in SAP using the Data Engine. The PortalNet. properties file contains the Pagelet Id mappings for the various portlets created using the EIS Admin Portal.









The PageletId are mapped to String constants, which are used in the Java Program to access the corresponding DataEngine Pagelets.













1 Comment