RFC Destination for PC 3.0

[Former Member]

Hi everyone.

I have an issue in PC 3.0 into the ABAP ´s GRC PC, when I´ve been configured the RFC destination module, on IMG -> Evaluation SetUp -> Automated Testing and Monitoring-> Configure RFC Conectors. Within it, I configured as ABAP conection to the R/3 system, a dialog user and then press on the "remote logon " link and everything works ok.

But my question is, what will happen when the password of that user expires? And that kind of user has to be a dialog user, hasn´t it? Is there any chance to configure it with a conection user or configure this, like SM59 transaction in AC 5.3 for SPM´s module?

Thanks a lot.

[Former Member]

hi

[former_member771067]

Hi Jose,

It's not advisable to use Dialog user for maintaining any kind of RFC destination. Please use service user for this purpose.

Thanks,

Guru

[former_member212848]

Hello Jose,

I just have installed Process Control 3.0.

For the RFC configuration, you should use a RFC user, this user has to be set up as a rfc user, please be sure of giving this property in the SU01 on the Back End (qas, prd, etc)

The rfc property (or communication), give to that user the no change password option. You can not use the communication user to log in with sap gui.

Please check the post installation guide of Process Control.

Write again if you have another doubt.

Regards,

Alejandro

[Former Member]

HI / Hola Alejandro,

The issue that I have, is once the user has been created through transaction SU01, and created as C type user ( communication user). How can I test the conection in the Frontend, from this system to the Backend system?

For example in AC 5.3 you have several buttons that checks the connection to the Backend.

Thanks for everything

Regards.

[former_member212848]

Hello,

There are two ways con test the user.

The first one you can try, is to set up the user you have create on the backend, into the JCO connector, where you can configure the authentication with the user and password you have create on the back end system. On the JCO screen (portal side) there is a button to test connection.

The second one, is to create a new RFC (you have to create one any way) on the PC Abap instance, use SM59 and set up the user and pass you have on the back end. Then test connection and authentication. Of course you can not use a remote login, but that is how you can test the connection.

Please let use know if your doubt is solved. Write again otherwise.

Alejandro

PD: dont forget to give point to the answers.

Edited by: Alejandro Acuña Acosta on May 11, 2011 10:35 AM

[former_member212848]

Hello,

There are two ways con test the user.

The first one you can try, is to set up the user you have create on the backend, into the JCO connector, where you can configure the authentication with the user and password you have create on the back end system. On the JCO screen (portal side) there is a button to test connection.

The second one, is to create a new RFC (you have to create one any way) on the PC Abap instance, use SM59 and set up the user and pass you have on the back end. Then test connection and authentication. Of course you can not use a remote login, but that is how you can test the connection.

Please let use know if your doubt is solved. Write again otherwise.

Alejandro

PD: dont forget to give point to the answers.

[Former Member]

Hi Alejandro.

Firstly, thanks for your post. I want to know, please, how can I check the JCO connector into the Portal site?

And acording to the SM59, I´ve done some tests with a comunication user but it didn´t work properly, on the other hand it was ok with a Dialog or Service user.

Thanks a lot.

Regards.

[former_member212848]

Hello,

You are welcome any time.

first, to check the jco you have to log on to portal web dynpro tools, then open the content administrator, and then open the maintain jco destinations button. There you will find GRFN_CR_DATA and GRFN_CR_DATA, you have to set up this jcos before testing them. One of the steps to set up them is to use some authentication way with the back end ( des, qas, prd), so you can use tickets or you can use user and password.

This is the user and password created on then back end as a communication user. Be sure that te user has the apropiate role, in the case of PC, SAP_GRPCRTA_PC_ROLE. Then you can check the Jco.

The same topic of the role assignment to the communication user is applyed to the RFC with SM59, so if you have the user with the right role on the back end, the same user can be used with RFC and jco connector.

Regards

Alejandro

PwC

[Former Member]

Hi Alenjandro,

Related with the JCO configuration in Portal (WebDynpro tools), I have some issues at the setup process of the GRFN_CR_DATA &GRFN_CR_METADATA:

- In the General Data step, you have to put the client where PC is instaled or the client of the enviroment which you launch through.

- Then, in the Appl. Server Connection you have to put the IP adress of the client (not PC client) or fill out with the PC´s ABAP client.

Finally, I would like to know if this configuration is configured to connect to ABAP client or production client.

Thanx a lot.

[former_member771067]

Hello Jose,

On

 How can I test the conection in the Frontend, from this system to the Backend system? 

I would like to suggest that you create the user as "dialog" user first in SU01, test the connection with the user. If your are successful with the test, then go back to SU01 and change the user type to communication user.

Thanks,

Guru

[former_member212848]

Hello,

1. in the general tab, you have to put the info of the back end system, (des, qas, prd).

2. you can use both, the ip or the name of the target system (dse, qas, prd). Much better if you can select it from the drop down box.

if you have more questions, check my bussines card and contact me.

Regards,

Alejandro