Can we able to use BI -WAD without Portal?

[Former Member]

Hi All,

i have a query based on my clients requirement.

Is it possible to work on BI 7.0 , WebApplicationDesigner without PORTAL integration?as per some threads , it's showing it's must.but not got exact picture .

Any inputs... is it possible or Not ?IF "YES" how to do that?

thanks & regards,

prasad

[former_member189638 · Accepted solution]

Portal is just used to display the Report in Web.

You can also execute the report in Web through a query or WAD using the button Display Query on the Web available on the toolbar...For doing this you do not require any portal intgration..

[Former Member · Accepted solution]

Thanks rakesh for the reply.

But i am getting "RFC communication error with portal".WHY?

regds

[Former Member · Accepted solution]

usually this error u face when u ahve error in rfc connection between bw server and portal.

u can ask ur basis colleagues to get their input.

they will let u create and maintain the sucessfull rfc connection between both servers.

if u know how to do the same , uc an also do it i.e. create sucesful rfc connection between servers :

follow SAP NOTES 916090 -- which talks about this in great detail

SAP note 917950.

you need to check the RFC connection between BW and portal side. Check the connection SALE and SM62 from bw side.

SM59 for RFC connection

1. Check all the services related to BI in SICF of ABAP stack.

2. Check whether ITS services are active, namely webgui.

3. Check the note 872043 for any access denied stuff.

IN Visual Admin check the JCo RFC Provider is properly configured with backend username.

Chk all the JCo related to BI are working properly either with SSO or User mapping

Chk in Table RSPOR_T_PORTAL the portal URL is proper or not

(transaction code SM30).

2. Enter RSPOR_T_PORTAL as the table.

3. Choose Maintain.

4. Choose New Entries to create a new entry.

5. Maintain the connected portal:

RFC destination: <RFC_DESTINATION>

System name: <SYSTEMALIAS>

Default: <DEFAULT>

Portal URL prefix: <PORTAL_URL_PREFIX>, for example, http://<portalserver><domain>:<port>;

Prefix of RM for BW Metadata: <KM_RM_METADATA_PREFIX>, for example, /bw_metadata

KM service URL: <blank>

Referesh the MetaData Service in BI Web Application Designer under settings try to connect you SAPRFC.ini file set enviroment variables for the same.

DESCRIPTION OF NOTE I FOUND ON FORUMS IN OTHER LINK-

Summary

Symptom

You are using SAP Netweaver 2004s Web Application Designer.

An operation that you want to perform is answered by a popup saying:

"Error during RFC communication (subrc = ...)", followed by the a certain

function name and in most cases an information that the portal or java

communication has failed. The message usually has the message class

RSBOLAP, numbers are 15, 17, 18.

This may occur during an operation like Save Template, Load Template,

Validate Template on Server, Load Reusable Web Item, Save Reusable Web

Item, Get Valuehelp, Execute Template in Portal, Publish Template to...,

Download of Metadata, and others.

All of these operations use functionality from the Java Server in some way

or the other, so they require a valid connection.

Function modules that may be mentioned in the error message (the list is

not complete) are:

RZX2_BTMP_SET, RZX2_BTMP_GET, RZX2_BITM_SET, RZX2_BITM_GET,

RSWAD_WEBPUB_CALL_SERVICE, RZX2_MIG3X70_DATA_GET, RSWAD_METADATA_GET,

RSWAD_TEMPLATE_SERVICES, RSWAD_PF_WEBPUBGETVH, ...

This note also applies if you for example change a Web Template, save it,

and the changes do not seem to be reflected when executing the Template

again.

More Terms

Setup, RSBOLAP015, RSBOLAP017, RSBOLABP18, RSBOLAP, 015, 017, 018, 15, 17,

18

Cause and Prerequisites

The Web Application Designer needs an active and valid Portal connection

for most of its operations. It can not be used without being connected to a

BI backend system (Netweaver BI Server).

Additionally, the connectivity Java->ABAP and ABAP->Java has to work for

the user currently logged on.

The usual communication flow is like this:

1. The frontend calls for a service on the Netweaver Server.

2. The call first meets the ABAP server.

3. The call is processed in the ABAP server as far as possible, and then

(if necessary) forwarded to the Java server.

4. The Java server processes the call as far as possible, and if

necessary calls another service functionality on the ABAP server.

5. The result is sent back on exactly the same way that it has arrived

25.01.2007 Page 2 of 3

SAP Note Number 916090

RFC-error messages in Web Application Designer 2004s

(in the most complex scenario: ABAP back to Java, then back to ABAP,

and then back to the frontend).

So if either the call from ABAP to Java fails, or the later call Java back

to ABAP does not work, an RFC-error occurs, leading to the error message in

the frontend.

Solution

This is not an error in the Web Application Designer.

When such an RFC-connection error occurs, the call from the Web Application

Designer frontend to the backend has not worked or not received a result.

In most cases, this means that the requested operation could not be

performed.

It may be that only the current call has failed, while the connectivity in

general is set up correctly. This may be for example, if the maximum number

of concurrent connections for the Portal is reached at the moment.

For that reason, please wait a few moments or minutes, and try again to see

whether the operation can be performed then.

In most cases, however, the connectivity is not properly configured, so the

call will not return a result also during the second and all following

tries.

In that case please ask your system administrator to set up the ABAP->JAVA

and JAVA->ABAP connectivity in a valid way (at least for your user...).

Please use note 888687 and 917950 (and their related notes) for the task.

If you do not succeed, please make sure to provide all the information

requested in these notes in your message. Otherwise an efficient message

processing is not possible, postponing the solution unnecessarily.

Header Data

[Former Member · Accepted solution]

HOW TO CREATE RFC CONNECTION ?

The RFC destination is generally created by the system administrator as follows:

Call transaction SM59.

Choose Create.

Enter GFW_ITS_RFC_DEST as the RFC destination.

Enter T as the Connection type.

Choose Enter.

Choose Registration.

Enter RFCCOM.GFW_ITS_RFC_DEST as the Program ID.

Connection between Source Systems and BW

http://help.sap.com/saphelp_nw70/helpdata/en/00/dc54384ac9a81be10000009b38f8cf/frameset.htm

Creating SAP Source Systems

http://help.sap.com/saphelp_nw70/helpdata/en/ac/4a4e38493e4774e10000009b38f889/frameset.htm

BW connectivity(.doc)

http://help.sap.com/bp_biv335/BI_EN/BBLibrary/documentation/B84_BB_ConfigGuide_EN_DE.doc

Test the RFC connection with Source Sytem

Go to Tcode SM59...

Double Click the RFC for that particular Source System

Click on Check Connection...

If you find some issues or don't have auth check with your basis team..