BI 7.0 and EP 7.0 Integration using Template Installer

Transcription

1 BI 7.0 and EP 7.0 Integration using Template Installer Applies to: This Article applies to Enterprise Portal 7.0 and Business Intelligence 7.0. For more information, visit the Portal and Collaboration homepage. For more information, visit the Business Intelligence homepage. Summary This document coves BI 7.0 and EP 7.0 integration using template installer, this activity will be done as post installation of BI-Java. Author: Balakrishna Veerala Company: Intelligroup Asia Pvt Ltd Created on: 01 Septmeber 2009 Author Bio Balakrishna Veerala is working as Consultant in Intelligroup Asia Pvt Ltd, Hyderabad. He has worked on EP, KM and collaboration, WebDynpro Programming and Java Technologies. He has completed his masters in computer science from Osmania University SAP AG 1

2 Table of Contents Introduction... 3 Prerequisites... 3 BI and EP integration is made simple using template installer, but it works fine only if you fulfill all the prerequisites ) Enable SSO (Single-Sign on) in AS-ABAP (BI) system ) Create System PSE and SSL (Cryptolib) in AS-ABAP (BI) system ) Checking the SLD configuration ) Checking the AS-ABAP (BI) system registration in SLD ) Create Logon Group in AS-ABAP (BI) system ) Activate Bex Services in AS-ABAP (BW) system ) Regenerate SAPLogon ticket in AS-JAVA ) Role and profile for BI administrator ) HTTP settings... 5 Starting template installer... 6 Checking the status of each and every step Testing the connectivity Testing Using BI Diagnostic and Support Tool Possible errors Related SAP Notes Related Content Disclaimer and Liability Notice SAP AG 2

3 Introduction BI 7.0 and EP 7.0 integration is made simple using template installer. This will be used as post installation process. Prerequisites BI and EP integration is made simple using template installer, but it works fine only if you fulfill all the prerequisites. Ensure that all the below mentioned pre-requisites are available properly. 1) Enable SSO (Single-Sign on) in AS-ABAP (BI) system To allow SSO for the AS-ABAP (BI) system, the following profile parameters in the "default" profile have to been set: login/create_sso2_ticket=2 login/accept_sso2_ticket=1 Procedure: Login to AS-ABAP -> Start TA /rz10 -> Menue: Utilities -> Import profiles -> Of all active servers Profile: -> Select: Default -> Mark: Extended Maintenance -> Change Add the both parameter -> Save and activate the profile -> Restart the system In case if the above profile parameters are already set leave this step. 2) Create System PSE and SSL (Cryptolib) in AS-ABAP (BI) system PSE: When exporting certificate from the AS-ABAP (BI) system, the system PSE must be properly configured. Procedure: Start transaction STRUSTSSO2, if the System PSE does not have a green status, right mouse-click on System PSE, click on Create, and accept initial values. Save the changes. SSL: Although for running the template installer the SSL is not necessary. However it is recommended for a successful scenario setup. 3) Checking the SLD configuration When configuring the WebDynpro Jco destination connectivity the Configuration of SLD your system is pointing (local or central) should work properly. Procedure: Logon to the WebDynpro Welcome page And then go to Content Administrator -> Check SLD Connection -> Test Connection. The relevant connection settings will be brought out before. Make sure they are correct. The test result is listed on the bottom of the page SAP AG 3

4 If the test fails, verify and adjust the SLD settings in the visual admin: 1. Goto sld data supplier -> tab Run time -> tab(bottom) http settings, adjust all the parameters. 2. Goto sld data supplier -> tab Run time -> tab (bottom) CIM Client Generation Settings adjust all the parameters. 3. Goto configuration adapter -> CTC -> Propertysheet SystemProperties, adjust all the SLD relevante settings. 4. Retest. 4) Checking the AS-ABAP (BI) system registration in SLD When configuring the WebDynpro Jco destination connectivity the AS-ABAP (BI) system must be configured in the SLD. Procedure: Logon to the SLD: (Your configured SLD (central or local SLD)) Please check in Home -> Technical Systems -> select type ABAP. This should have configuration of your ABAP (BI) system. If it is missing, logon to your ABAP (BI) system -> go to transaction RZ70. Fill in the SLD Bridge: gateway info -> Activate -> Start data collection. If a error message like "ABAP backend doesn't exist in the SLD" pops up While running the template installer, there could be different possibilities for this error. Starting SP14 more detailed error sources will be popped up. For lower SPS the exact reason of the error can be found in the default trace file. 5) Create Logon Group in AS-ABAP (BI) system When configuring the connectivity between the AS-ABAP (BI) and AS-JAVA system, a "Logon Group" must be provided for the user input. Procedure: Login to AS-ABAP -> Start TA /smlg -> Create -> Enter Logon Group name(e.g. PUBLIC) and select an Instance -> Copy -> Save 6) Activate Bex Services in AS-ABAP (BW) system This step is not necessary for SPS with number higher than SP14. In order to get Services displayed in the portal, they have to be enabled and activated. Procedure: Login to AS-ABAP -> Start TA /sicf -> (if Screen Maintain ICFXXX; ICFXXX; appears -> Continue with Execute) -> Navigate: Default_host / sap / bw -> Mark "bw": Right-Click -> Activate Service -> Press "Y" to activate the whole tree 7) Regenerate SAPLogon ticket in AS-JAVA (Only valid for releases before SR2 /SPS09) 2009 SAP AG 4

5 Unfortunetly when you install a AS-ABAP and AS-JAVA system on one host the tickets from AS- ABAP and AS-JAVA have the same common name (CN) and will not be imported when exchanging the tickets. Therefore you have to regenerate the SAPLogonticket in the AS-JAVA system. Procedure: Login with the Visual Administrator to the J2ee Engine -> Navigate: Server / Services / Key Storage / TicketKeystore -> Mark and Delete the both tickets: "SAPLogonTicketKeypair" and "SAPLogonTicketKeypair-cert" -> Create a new ticket with the following values / settings: Country Name: <Value> / State: <Value> / Locality Name: <Value> / Organization Name: <Value> / Organization Unit Name: <Value> / Common Name: <HOST>_<PORT> Entry Name must be "SAPLogonTicketKeypair" Store certificate: X Algorithm: DSA -> Generate Result: 2 new Tickets are now available 8) Role and profile for BI administrator Ensure that administrator user already exist in your BI (ABAP) system and has been assigned role SAP_BC_JSF_COMMUNICATION (minimum requirement) and profile S_BW_RFC. 9) HTTP settings Make sure that http port of message server of your BI (ABAP) system is set. In case if you are using https protocol check SAP Note SAP AG 5

6 Starting template installer If you all the above settings are configured properly then you can start the template installer for configuration. To start the template installer, you need start NetWeaver administrator using the below url. name>:<port>/nwa Go to Deploy and Change 2009 SAP AG 6

7 Click on Configuration BI-Java Technical configuration BI-Java (repeatable, reproducible). Then click on Start. It will display the below screen SAP AG 7

8 If you are using the https then check the above button and make sure the settings are done related to https by clicking on the help button (information button which is just beside the check box shown in above screen shot). Now you are at the very import step of your configuration, where in you will provide all the information showed in the above screen shot. Please check the below steps properly before filling up the above details. SLD check: Click the checkbox if you like to perform the SLD checks. This creates the WebDynpro Jco destinations. If you skip the check then you have to configure the WebDynpro Jco destination manually ABAP Administrator User: Specify the administrator user (other than ddic) in BI (ABAP) system. This user should have the administrator right (for example has been assigned to role SAPJSF) that is only used during configuration. And make sure the user has authorization to these transactions BI administrators require authorization for transactions SM59, SMGW, RZ10, STRUSTSSO2, SM30 (table RSPOR_T_PORTAL) and, in some circumstances, STMS. Administrator Password: Provide administrator password. ABAP Application Server Host: Provide ABAP application server host (don t provide with domain name) Domain Name of ABAP Host: Specify the full domain name of the application server for BI (ABAP) system, without host name. For example, company.com System ID of ABAP System: Specify the system ID (SID) for the BI (ABAP) system (profile parameter SAPSYSTEMNAME) SAP AG 8

9 ABAP System/Instance Number: ABAP Client: Logon Group: Specify the system (instance) number of the BI (ABAP) system (Profile parameter SAPSYSTEM). Specify the client number of the BI (ABAP) system, for example, 003. In most cases this should be a number other than 000. Specify the logon group used by the system object in the portal and Web Dynpro (see available logon groups in transaction SMLG) User for BI Metadata in WebDynpro: Specify the user that the JCo destinations use to retrieve general metadata in the Web Dynpro Content Administrator of the J2EE Engine. This user is not used to perform user-specific actions. This user must exist in the BI (ABAP) system and be assigned role "SAP_BC_JSF_COMMUNICATION_RO". Password of User for BI Metadata in WebDynpro: Specify the password of the user given above Use SAP Export Library (PDF) Click the checkbox if you like to use SAP Export Library (PDF) Java/J2EE Administration User Specify the J2EE administrator user for BI(Java) system. Administration User Password Specify the administrator user password for BI(Java) system. Domain Name of Java/J2EE Host Specify the full domain name of the application server for BI(Java) system.for example, server.company.com Note: it s preferable to use the same User ID in BI and Portal with all enough administrative permissions (use J2EE_ADMIN). After specifying the entire above information click on Next, system takes few minutes performs about 59 steps automatically. Just beside each and every step you will see one of the symbols. Legend: Not executed In progress Finished successfully Incompletely executed Finished unsuccessfully 2009 SAP AG 9

10 Checking the status of each and every step If you click on details tab, you will see the information about all the steps performed by the system with status symbol. You will see the below screen shots of successful configuration of various steps performed by the system SAP AG 10

11 2009 SAP AG 11

12 Testing the connectivity Testing the connectivity between BI and EP: Login into enterprise portal name>:<port number>/irj Go to system administrator->system configuration->portal content->system landscape-> You will see the system object created with name SAP_BW see the below screen shot. Click on connection test. Select all 3 check boxes (SAP WebAs connection, ITS Connection, Connection test for connectors) 2009 SAP AG 12

13 If all the tests are success, then BI-EP integration happened successfully. To test further, create one transaction Iview in the portal and bring some BI transaction to portal (e.g. SE 38) SAP AG 13

14 Testing Using BI Diagnostic and Support Tool Testing using SAP NetWeaver Business Intelligence Diagnostic and Support Desktop Tool. This will completely test each every thing and clarifies all the details. Accessing the Diagnostic and Support Desktop Tool. Use the below url to start diagnostic tool automatically. name >:<port numebr>/irj/servlet/prt/portal/prtroot/com.sap.ip.bi.supportdesk.default? See the below screen shot which shows the result of configuration. If all are in GREEN then, every thing is configured perfectly. In if you see anything in RED, try to fix the error and run the diagnostic tool once again. Incase if you see anything with RED status, suggested solution will be provided in the bottom, try to fix that and run the Diagnostic Tool again SAP AG 14

15 Possible errors Possible errors while doing the configuration: Incase the provided information (User Credentials) doesn t have any proper rights then you will see some error like this. See the below screen shot. After performing some steps it says the error NO_AUTHORIZATION_RFC. It means the provided BI administrator User ID is not having proper authorizations to create RFC destinations in ABAP. You have 3 options here: Retry Step: Skip Step: This will retry the same step. This will skip the current step where you have the error and proceeds further, but we need perform this again manually. Cancel Process: This will cancel you configuration process. Incase if you get the above error you can cancel the process and re-start it again by providing the appropriate User credentials with all necessary administrative rights mentioned in the prerequisites SAP AG 15

16 Related SAP Notes sapnote_ sapnote_ , sapnote_ , sapnote_ sapnote_ , sapnote_ sapnote_ sapnote_ sapnote_ sapnote_ sapnote_ sapnote_ sapnote_ SAP AG 16

17 Related Content nd?rid=/library/uuid/b0a5216a-349c-2a10-9baf-9d f6a&overridelayout=true nd?rid=/library/uuid/d082fe b fd009f695c74&overridelayout=true For more information, visit the Portal and Collaboration homepage. For more information, visit the Business Intelligence homepage 2009 SAP AG 17

18 Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document SAP AG 18