Web Dynpro with Bapis using Miniwas 6.20 or Sneak Preview 6.40 ABAP

[Former Member]

Does anyone know if I can I use a web Dynpro that uses BAPIs to connect to a Miniwas 6.20 like a Backend system?

I have the SLD configuration OK, I was able to create the Jco connection, but when I test the Metadata application with this Technical System (Miniwas 6.20) at the Content Administrator I get an error message: "Group PUBLIC not found" (I also tried with SPACE, like a Logon Group). I have the corresponding settings in the service file on Windows folder (sapmsBSP 3600) and the others settings too.

I think the problem is to try to define Logon Groups at this kind of R/3 system (Miniwas 6.20) ... It's possible to use Logon Group with Miniwas?

I want to know if somebody had tried to do this practice (Web Dynpro using BAPIS)against to Miniwas System.

Please I would like to get a yes or no answer

Janett

[Former Member]

Hi,

You have to configure the PUBLIC logon group in SMLG transaction.

Once configured the SLD and JCO-Destinations in the WebDynpro Content Administrator, we had the same problem with METADATA_DIRECTORY JCO-Connection. When we tested it, we got an error related with the PUBLIC LOGON GROUP. This JCO destination is a metadata directory connection and use the SAP message server to connect to the PUBLIC logon group.

You can create the PUBLIC logon group easly with SMLG, but it is necesary to add a "Logon Favorite Storage" in "SMLG Transaction - Display control/status Area" called PUBLIC too.

More information at:

http://help.sap.com/saphelp_nw04/helpdata/en/28/1c623c44696069e10000000a11405a/content.htm

After that, all JCO connections and the webdybpro application should run fine.

Regards.

Agustin Alvarez

[Former Member]

It took long time to solve the problem, but finally we resolved our problem of Logon Groups with a Note OSS 32188 "No logon Groups are available after a system starts".

We had to run a report RSRZLLG0 and had to change the parameter rdisp/autoabaptime from 0 to 5.

Fortunaly, that procedure resolved the problem: logon groups appeared after changing that parameter and after running the report.

Afterward we were able to test and run the JCo connection and to run the webdynpro application.

Janett

[Former Member]

Hi, Rich!

Did you do that process with MINIWAS 6.20 or with Sneak Preview 6.40 ABAP?

I mean Miniwas 6.20 NOT the complete SAP WAS 6.20. I use BCUSER when I access to Miniwas 6.20. I dont have a special user.

It's important to me to know if this really works in the test drives version. I'm not in a Production environment, i'm doing proofs.

Ramakrishna, thaks for answer me too,

What do you mean with "valid credentials". I followed completely that tutorial, I did create the Jco Connection, the problem is when I want to test it inside the COntent Administrator. I got that message error.

Can you help me to resolve my problem?

Thank you very much!

Janett

[Former Member]

Hi,

Have you tested your JCO connection, do you have valid credentials to access R/3 backend access.

here is a simple tutorial which gives dtep by step procedure webdynpro access R/3 Backend.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/s-u/tutorial on accessing abap functions in web dynpro - 4.htm

Accessing ABAP Functions in Web Dynpro (4)

[RichHeilman]

In order for me to get this to work, I had to set up the PUBLIC logon group using transaction SMLG.

Regards,

Rich Heilman