Information broadcasting in BI7.0

Question

Dear friends,
Could you pls help me with the procedure to configure the information broadcasting in BI7.0.
Pls help us with the below information
1.prerequiste for information broadcasting
2.How to configure bex broadcaster?(is there any step by step procedure doc?)
3.As per our understanding we can access bex broadcaster in web environment only(in browser).Is there any other way to access bex broadcaster to email the reports to the users?.
4.Is precalculation server is mandatory to execute and email the reports?
Thanks in advance for your time and help.
Regards
Soujanya

Answer 1

Overview: Integration into the Portal
Use
A number of settings need to be made in the BI system for the integration of SAP NetWeaver BI and SAP NetWeaver Portal. Some settings depend on one another, which is why we recommend that you follow the given sequence when you maintain settings in the BI system and in the portal. The report Maintain Settings for Integration into the Portal (report RSPOR_SETUP) supports BI system and portal administrators in setting up a secure connection in both directions, step by step. First the report asks you to make the required entries and then automatically determines additional specifications that you either have to enter manually, or that are entered automatically when the steps are performed.
Template Installer
As an alternative to report Maintain Settings for Integration into the Portal (report RSPOR_SETUP), you can use the template installer. The portal-based template installer enables the automatic configuration of the settings required in the portal and in the BI system. For more information, see Template-Based Configuration.
Requirements
Before you start to maintain settings, you enter general information. This information is used, in part, by various steps. If you determine this mandatory information at the start, you can perform the steps in a simple, logical sequence.
The report summarizes these specifications in the selection screen. The specifications are saved for the current session so that the transactions for the individual steps can be called separately from the SAP Reference IMG.
BI administrators require authorization for transactions SM59, SMGW, RZ10, STRUSTSSO2, SM30 (table RSPOR_T_PORTAL) and, in some circumstances, STMS.
Portal administrators need to have the portal roles super_admin_role and com.sap.ip.bi.business_explorer_showcase assigned to them. They also need to have access to the portal file system.
It is recommended that, from an organizational point of view, BI and portal administrators work together closely.
Connections Between SAP NetWeaver BI and SAP NetWeaver Portal
This report supports you in establishing connections between BI and the portal. The portal communicates with BI using the Web protocol http or https. Communication is establised based on the system object in the portal.
BI uses an RFC connection to communicate with the portal. The portal is the RFC server and BI is the RFC client. The report is used to create an RFC destination.
Single Sign-On Between SAP NetWeaver BI and SAP NetWeaver Portal
Single Sign-On saves you having to log on to BI and the portal separately. Single Sign-On uses SAP Logon Tickets. SAP Logon Tickets are created in the source system and contain the system ID, user, validity, and a digital signature. The digital signature is created by using the private key of the certificate. In the target system, the signature is verified by using certificates with public keys. The target system must trust SAP Logon Tickets from the source system; this requires the source system to be entered in the access control list (ACL).
For single sign-on to work correctly, the URL must be fully specified with the host name and domain. For this reason, you must also specify the portal URL prefix and domain in step 3. When you call BI iViews within the portal, the hostname from SAP NetWeaver AS determined in step 7 is used if this is a Web template from BEx Web Runtime 3.x For this reason, you must also specify the domain there. See the documentation for different domains under SAP Library -> SAP NetWeaver -> Security -> User Authentication and Single Sign-On -> Authentication on the Portal ->Single Sign-On -> Single Sign-On with SAPLogon Tickets -> SAP Logon Tickets for Multiple Domains.
Standard settings
The individual selection screen values are now described. For a more detailed description of these values, see the documentation on the individual steps.
Creating RFC Destinations in the J2EE Engine
Program ID: The program ID is the name of the registered server program (see step Creating RFC Destinations for the Portal).
Portal Directory: The Portal Directory is used to start the SAP J2EE Engine Administrator tool. The file ./admin/go.bat has to be in the directory. The SAP J2EE Engine Administrator can also be installed locally on the administrator's PC for remote access to the portal server.
BI User and BI Password: The BI user and the BI password are used by the J2EE Engine to request signatures from the RFC function modules in the BW system. Users can be compared using ALEREMOTE.
Creating RFC Destinations for the portal
User-Defined RFC Destination, Program ID as RFC Destination and RFC Destination : This report allows you to choose any name for the RFC destination. Otherwise the program ID is used (see above). If you choose a user-defined name, enter the name under RFC destination.
RFC Description: The RFC description is the text that is displayed in the BEx Web Application Designer and BEx Query Designer applications as the description of the connected portal.
Maintaining Portal Server Settings for the Portal
Default: To select a portal as the default portal, select the Default indicator. A warning will be produced if another portal is already marked as the default portal.
Portal URL Prefix: The Portal URL prefix is required for input help in the BEx Broadcaster. The report uses the portal URL prefix to list particular iViews for maintaining or testing the settings. The portal roles super_admin_role and com.sap.ip.bi.business_explorer_showcase are required for calling these iViews.
Prefix of RM for BI Metadata: The RM prefix for BI metadata is required in the step Setting up Repository Managers for BI in the Portal and also has to be maintained in the portal server settings. The prefix determines the path in Knowledge Management under which BI metadata is accessed by the Repository Manager.
Exporting the BI Certificate into SAP BI
Export Path and Export File Name: The BI certificate is saved under the specified path and file name and can then be imported into the portal.
Creating BI Systems in the Portal
Path in Portal Content and Name in Portal Content: The BI system in the portal is created under the specified path and name in the Portal Content Studio.
Template for Defining BI Systems in the Portal: As a template, you can choose either System with Load Balancing orSystem with Application Server when creating a BI system in the portal. The necessary information is determined and displayed depending on the template you select.
BI Properties: The following properties are specific to a BI system. If the identifier BI Directory Provider is activated, the BI system is displayed in open dialog when selecting queries or InfoProviders. The properties BI Documents for InfoProviders, Master Data, and Metadata contain the path to the respective CM Repository Manager for storing BI documents in Knowledge Management. These properties are used when the documents are migrated to Knowledge Management.
The property BI Master System means that the BI system is the central persistent store in the portal. The BI master system is used to read and execute Web templates. The running BI Web Runtime requires exactly one BI master system within a portal.
System Alias: Every system in the portal requires a system alias. You can enter any value. SAP recommends that you use the logical system name as the alias.
Creating System Alias SAP_BW: For the portal role Business Explorer com.sap.ip.bi.business_explorer_showcase, a BI system is required in the portal with the system alias SAP_BW. Note that there can only be one system with the alias SAP_BW.
Configuring User Management in the Portal
Logon Ticket Client: The logon ticket client can be any value between 000 and 999. The client is necessary if several portals with identical portal SIDs are connected. This is not normally the case and the default value can usually be transferred. You have to enter the client when you import the portal certificate into the BI system.
Exporting the Portal Certificate into the Portal
Portal SID: The portal SID is required so that naming conventions are observed. It has to be entered when you import to the BI system.
Import Path and Import File Name: The portal certificate should be saved under the specified path and file name and can then be imported into the BI system.
Maintaining User Mapping in the Portal
User-Mapping User and User-Mapping Password: The user-mapping user and password are used to check user assignment. This information is not absolutely necessary but does ensure that all settings have been made for a secure connection from the BI system to the portal.
Activities
1. Determine the mandatory information described above.
2. Execute the activity (= report Maintaining Settings for Integration into SAP Enterprise Portal ).
3. Enter the mandatory information on the selection screen.
4. Choose Execute.
5. Choose Previous Step or Next Step to switch between the individual steps.
6. To execute the step, choose Execute Step. The system either starts the necessary application so that you can enter information manually, or executes the step automatically.  For each step the report supports the start-up of the appropriate application for executing the step manually.
Sequence of Steps
SAP recommends that you perform the necessary steps in the following order:
7. Create RFC Destination in J2EE Engine
8. Create RFC Destination for the Portal
9. Maintain Portal Server Settings for the Portal
10. Maintain Single Sign-On in the BI System
11. Export BW Certificate to the BI System
12. Import BW Certificate to the Portal
13. Create BW System in the Portal
14. Configure User Management in the Portal
15. Export Portal Certificate to the Portal
16. Import Portal Certificate to the BI System
17. Set Up Repository Manager for BW in the Portal
18. Maintain User Mapping in the Portal
19. Import SAP Basis Plug-In to the BI System
The documentation for the individual steps describes the manual process. The report Maintaining Settings for Integration into the SAP Enterprise Portal (report RSPOR_SETUP) executes some of these steps automatically..