Ansicht
Dokumentation
03723 - Problems with RFC destination for Vertex
CL_GUI_FRONTEND_SERVICES - Frontend Services General Material DataThis documentation is copyright by SAP AG.
Problems with RFC destination for Vertex
I am not sure but I think it is picking up the PRD02 useridfrom the SM59 R3 connections on the 05 application server.
I think you would be better off running vertex in 'Registration mode'.
The vertex job could run under any user id you setup as long as the
authority is OK. You can also run the vertex job in any subsystem
you decide to use. I will send you another e-mail with instructions on
how to do that if you decide to go that route.
Charlie
> -----Original Message-----
> From: russ.cookZg... [SMTP:russ.cookZg...]
> Sent: Wednesday, October 31, 2001 11:38 AM
> To: DoNotReply@consolut.eu
> Subject: Problems with RFC destination for Vertex
>
> In the past I had 2 production instances (02 and 05) created on 2
> separate AS400s (Q2 - central instance and Q3 - app server). These
> were opticonnected together. I had a RFC destination set up in SM59
> that pointed to a program for Vertex and the gateway service that
> existed on the central instance 02. This was working fine. When a
> batch job or dialog was run on the 05 app server instance that
> required Vertex it ran on the central instance and ran under user id
> PRD02.
>
> I recently created a new PRD app server instance 09 on the same AS400
> as the central instance 02. Now when I attempt to use the same Vertex
> RFC destination, it is using the user id PRD09 instead of PRD02. I
> do not understand why this works differently between the 3-tier
> setup, and running a new instance on the same box as the central
> instance. In both cases, they are pointing to the same gateway and
> host. I need the RFC destination to always use the same SAP instance
> user id (PRD02) because Vertex has a paramter file where you must
> code the user id to access the Vertex SQL collection. Has anyone run
> into a problem like this?
>
>
>
> DoNotReply@consolut.eu
>
> Your use of consolut is subject to http://www.consolut.net
>
Durban Tours - Südafrika Safari
ROGBILLS - Synchronize billing plans SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 3132 Date: 20240420 Time: 032439 sap01-206 ( 4 ms )
