No central node on RFC destinations in TDMS

Hi all,
We are running a TDMS proof of concept. The initial runs TDMDC & TDTIM went well. We are trying more iterations to get a feel for what TDMS performance is like. However, we cannot progress further as we have issues with RFC. When we check u201CRFC Informationu201D we see u201CCheck of all settings has been performed. All settings in all systems are consistentu201D.
Yet when we check the Synchronization tab, we see entries for control (_PCL), sender (_SND) and receiver (_REC) only u2013 there is no entry for central (_CEN). If we look at the system as a graphic, it has connections between sender, control and receiver but the instance on which TDMS sits has only a Control entry u2013 it does not have an entry for Central that previous TDMS iterations that ran to completion successfully have.
The upshot of this is that when we look at the TDMS main screen for a new package, we can see entries for both u201CSender systemu201D and u201CReceiver systemu201D but u201CCentral systemu201D has an entry of u201CNoneu201D.
Has anyone come across this and if so could you please advise u2013 we cannot progress until this RFC issue is resolved completely.
regards,
Marit Duits, Jason Hunt
P. SL Basis Systems Management

Hello,
The required Destination type may differ for different TDMS process types. In TDTIM / TDMDC a CEN destination is required for technical reason - for other Process types ( e.g. Shell creation ) - this might no be required (even there is an entry in the header section of the process tree .
For which process type did you observe the missing CEN destination ?
Best regards,
Peter Freund

Similar Messages

TDMS auto-generated RFC Destinations cleanup

Hi Experts,
We have performed the deletion per note 1030483 - TDMS Deletion/reorganization of
transfer packages for completed and incomplete packages.
But we noticed the RFC destinations auto-generated by TDMS still remained and pilling up in the systems.
Would like to get some expert opinions whether we should delete or keep these RFC destinations?
Thank you.
BR,
Bee Huang

Hi,
If you are not using the packages9old) any more , you can delete the generated RFCs for the old packages as well.
Reagrds,
Sandeep

CCMS aler for RFC destinations availability

Hi Experts,
We have configured ccms alert autoreaction method for availability of RFC destinations.
alert is configured with yellow thershold as 10% and red threshold as 5%.
alert text is :&1 &3 < &2 &3 15 min. avg. value below threshold value (&4 measurements)".
We are receiving mail alerts for CCMS red alert for RFC saying" 0 % < 5 % 15 min. avg. value below threshold value (1 measurements) ".
But when we checked the corresponding RFC is working fine.
Can anyone please explain how this RFCs destinations check alert will work and what is the meaning of alert text ":&1 &3 < &2 &3 15 min. avg. value below threshold value (&4 measurements)"."
Thank you,
Kavitha

Hi
I have done
1. RFC connection from x to y and y to x
In X system:
1. In transaction RZ21, mark Method definitions, and choose Display overview
Copyed standard CCMS_RFCDest_Availability_Col method definition to ZCCMS_RFCDest_Availability_Col
Parameters tab
For x
Parameter name = RFC_DEST
value = SM_XCLNT510_TRUSTED
Parameter name1 = COLL_METHOD
value = ZCCMS_RFCDest_Availability_Col
Same in Y but for RFC_DEST give
Parameter name = RFC_DEST
value = SM_YCLNT100_TRUSTED
Execution Tab
Type of call = Function module
Call SALK = SALK_RFCDEST_AVAILABILITY
Execute method on = The local server of the MTE to be processed
Execute method for = Individual MTE
Control tab :
Execute method for = Individual MTE
Execute method = periodically in dialog process (short-running program)
Startup method = Execute method immediately after monitoring segment start
Execution location
of startup method = Only on the central instance
Start Tab:
Execute method = Data Collection Method
also try in so many way as in :Parameter Tab:
RFC_DEST               SM_XCLNT510_TRUSTED
COLL_METHOD            ZCCMS_RFCDest_Availability_Col
MTE_CLASS              Availability_RFC_Destinations
MTE_CLASS              CCMS_RFCDest_Availability_MO_Class
MTE_CLASS              CCMS_RFCDest_Availability_Col
COLL_METHOD            CCMS_RFCDest_Availability_Col
RFC_DEST               CCMS_RFCDest_Availability_Col
Problem:
I am not able to Reset the segment in WARMUP status
not able to find the node in RZ20
Regards,
Neni

ShellCreation -RFC destinations

When I run RFC Destinations I get only Control and sender system detail. Do we have to Add Central system and Receiver as well ? Thanks

No you dont need to add control or receiver.
During shell only two systems are required, one on which you run TDMS and other one is the sender system from which you want to export the data.
Shell process doesnot do any step in the receiver it just guides the user to do some manual steps.
I hope this info helps

RFC Destination Between R/3 and XI Not Reestablishing

I have an RFC destination set up in R/3 so that calls can be made to our XI system. Everything works fine until our central SLD goes down for maintenance,etc. When the SLD is down, the RFC connection is lost. I assume this is by design. The problem is that once the SLD comes back up, I would expect the RFC Destination connection to automatically re-establish itself. It does not. I have to go into IB:Config and change/save/reactivate a channel using the RFC destination so that it gets reregistered.
Is there a setting that will make the RFC Destination connectivity re-establish itself automatically?
Thanks

When you say "go add some spaces" are you referring to putting spaces in the description field just so you can change/activate? I assume you did, just checking.
Thanks Naveen.
Everyone else out there: Do you all have to manually do this every time the SLD goes down?

Calling Remote enabled Function module in java using RFC Destination

Hi
We are on Portal 7.3 ehp1 sp9.
Steps followed are :
RFC Destination called “SAP_RFC” has been created as below :
Configuration -> Destinations -> RFC Destinations
Connection and Transport:
Load balancing :Yes
Provided : SystemID / MS Server / MS Server Service / Logon Group / Gateway Host / Gateway Service
SNC : Inactive
Logon Data:
Authentication : Current User (Assertion Ticket)
Language : EN
Client : XXX
Repository Connection:
Destination Name : This Destination
Specific Data:
pooled Connection Mode : Yes
Max : 5
Size : 10
Max. wait time : 10,000
Ping Destination results : Successfully connected to System XXX as per user XXXXXXX.
JAVA Code as Follows:
JCoDestination destination = JCoDestinationManager.getDestination("SAP_RFC");
//destination.ping();
JCoRepository repository = destination.getRepository();
JCoFunction function = repository.getFunction("FM_NAME");
function.execute(destination);
Lines highlighted in RED color throwing an error as below :
{"ERROR":"Initialization of destination JCO_RFC failed: Incomplete logon data. on <SID> mshost <MS_HOST>/ com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Incomplete logon data. on SID mshost MS_HOST"}
And found that no COOKIE with the name “SAP_SESSIONID_<system>_<client>” was not found, I am afraid that “Assertion Ticket” was not created in above scenario.
To confirm SSO configuration working, i have followed below steps:
1) Created System Object pointing to R/3 and tests were successful for authentication type "SSOLOGONTICKET / ASSERTIONTICKET"
It's J2EE application, no references or any other additional configuration been made part from above.
Any help ?
Thanks

Here is log ..Assertion ticket could not be retrieved. Error was null
Log Record Details
Message:
Assertion ticket could not be retrieved. Error was null
Severity:
Error
Date:
2014-04-23
Time:
20:28:26:056
Category:
/System/Security/destinations
Location:
com.sap.security.core.server.destinations.service.AssertionTicketRetriever
Application:
Thread:
System [2]
Data Source:
j2ee/cluster/server0/log/system/security_00.log
Arguments:
Passport User Activity ID:
3a7af5ddca8b11e384bd8adb6f484d33
Message ID:
Session:
Transaction:
User:
Time Zone:
+0800
Customer Message Component:
BC-JAS-SEC
Runtime Component:
tc~sec~destinations~service
Correlation ID:
3643650000002747
Passport Session:
3A7AF5DDCA8B11E384BD8ADB6F484D33
Passport Connection:
3a7af5ddca8b11e384bd8adb6f484d33
Passport Connection Counter:
0
Log ID:
C0000AD01D7B002200000EA5009800B2
Host:
host
System:
XXX
Instance:
J00
Node:
server0

RFC destination problem in SWF_XI_CUSTOMIZING

Hi,
SWF_XI_CUSTOMIZING
While performing SAP XI customizing (Automatic workflow customizing) on the node Maintain Runtime Environment, the system is asking question like below..
Configure RFC Destination:
RFC user has wrong password. Synchronize password?
Thanks,

Hi Raja,
check the RFC destination from R/3 to XI and XI to R/3....
The Business Process Engine (BPE) processes integration processes at runtime. Since the BPE uses functions of the Workflow Engine and generates workflows from integration processes at runtime, you must customize the Workflow Engine automatically by using transaction SWF_XI_CUSTOMIZING before you can use the BPE.
also check ...
http://help.sap.com/saphelp_nw04/helpdata/en/cd/20bc3ff6beeb0ce10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/5c29eb96803e2be10000000a1553f6/frameset.htm
Regards
Biplab

Post Install Activities Problem - Checking RFC Destination

I "successfully" installed Web AS 6.4 SR1 ABAP Non-Unicode. I am following the instructions in SAP Web Application Server 6.40 SR1 ABAP on Windows: MS SQL Server guide. The Post Installation instructions (2.2.6) require that I Check the RFC Destinations if my the database is located on a remote server from the central instance server.
The instructions tell me to locate the SAPOSCOL_<DB_Hostname> under the TCP/IP connections and if I cannot locate it I must add it.
In my case I cannot locate it so I want to add it. However, I do not know what data I must enter in the various fields of the RFC Destination screen. Example: what is the connection type for SQL Server
Thank you.

Hi Doug,
Is your database installed on a separate host from the SAP software? If not, you can safely ignore this recommendation and move on.
We have many systems on Win / MSS on 6.40 ABAP / Java with db and SAP on the same systems. None of my systems have this RFC, and I am not aware of any problems due to the lack there of.
Regards,
Sanket

RFC destinations for CUA - clarification required.

Greetings, Gurus!
I'm in the planning-going-testing phase of CUA implementation for our landscape, and it appears I've run into something of a snag.
According to everything I've read, including various SAPnotes and documentation available in SAP Library, I understand that it is not possible to configure the CUA to use specific RFC destinations. Instead, CUA will attempt to use an RFC destination that has the same name as the logical system it is calling. I.e. central system ADMCLNT070 is making an RFC call in context of CUA to PRDCLNT510, for this purpose, RFC destination named PRDCLNT510 will be used.
Q1: Have I understood this correctly?
Q2: Is there any way to specify an RFC destination I want to use?
Thanks for your time!

would like yiu to go through the below link too,
As the complication of using diffrent name and etc has been mentioned, and fixing has been hit and trial method for me when i did it..
logical system name vs. destination name - CUA -
Thanks,
Prasant K paichha
Edited by: Prasant K Paichha on Mar 5, 2010 12:52 PM

An RFC destination could not be specified for the logical system

Hello Experts,
I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
An RFC destination could not be specified for the logical system
SB3CLNT011
Message No. B1550
Diagnosis
An RFC destination should be specified for the logical system SB3CLNT011.
This could not be done in this case. SB3CLNT011 is not your local logical system
and this system is not included in the relevant Customizing tables.
Procedure
Check:
RFC
destination
Port
definitions
oubound partner profile of
message type SYNCH for this logical system
Regards,
Khushboo

Hi Oritra and Suraj,
I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
System SB3CLNT011 as a partner type already exists
System SB3CLNT012 as a partner type already exists
Port A000000018 with RFC destination SB3CLNT011 already exists
Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
Outbound parameters for message type SYNCH SYNCHRON already exist
Am I missing something in WE20?
Regards,
Khushboo

Logical system and rfc destination

hello all,
what is the difference between logical system and RFC destination?
thanks for ur help in advance.
regards,
vikas

Hi,
In any ALE scenario u need one sender and one receiver system.
Logical systems are just logical representation of these systems but in case of RFC destination u specify technical parameters for those systems like IP address and username and password to connect to that system.
Thus when u create port i.e.we21 u specify actual RFC destination for the system to which u want to connect and when u create partner profile for that logical system u specify this port so when u want to send data to this logical system i.e receiver system port will be used which in turn has RFC destination which will be used to connect to that system.
In simple terms logical systems are logical representation of any system and RFC destinations are physical/techinical systems.
Regards

Logical system and rfc destination related Query?

Hi Dudes
Do we need to define logical system and RFC destination if they are in different clients in same server
Regards
Raj Kumar

Hi
Both are client independent setting, so even if you define in one client, it would be available in other clients also.
Regards,
Sanjeev

RFC Destination Connection Pool requirement

Hi Experts,
I have a custom webdynpro java application to display number of work items pertaining to that particular user in a backend.
There are users who dont use this functionality as well. But the requirement is to place this application in home screen.
I have used both metadata and modeldata with hard coded user since we did not want error messages to appear for users who do not have backend access.
Application & Access Details
Application Location : Home Screen
Concurrent Users : 600 concurrent users maximum possible value
Connection Usage : Close connection immediately using disconnectIfAlive() method.
Now I need to configure JCO Pool Size , Max Connections, Wait Time for the RFC destination.
I have read a lot of post and documents but could not acheive clarity of thought on this.
Kindly let me know what values I should give in these fields for optimal performance and no connection issue for users.
Regards,
Porselvan

Hi Muthavudaiyan,
Hope you are doing good.
Basically from the JCo perspective, there are only 5 parameters that are involved here:
jco.destination.pool_capacity:
Maximum number of connections that are held open in the pool for reuse (default: 1)
jco.destination.peak_limit:
Maximum number of connections that can be obtained from a pool at peak usage times
jco.destination.max_get_client_time:
Maximum time to wait for a free connection if the peak limit is reached before exception is thrown
jco.destination.expiration_time:
Timeout period after which pooled idle connections can be closed (default: 600000ms = 10mins)
jco.destination.expiration_check_period:
Regular time interval for checking if pooled connections have expired and will be closed
The values are determined by the application in question. The ideal values have to told to you by the application developer; there are no two ways about this.
Thank you and have a nice day :).
Kind Regards,
Hemanth

Service desk RFC destination in the Satellite system

HI All,
can any body tell me the RFC destination that is to be maintianed in the satellite system so that the message reaches the solution manager service desk.
I am creating messages they are being send to the service desk successfully but are not visible when I go into the service desk of the solution.
But they are visible through the transaction code CRM_DNO_MONITOR .Can any body help the RFC destination to be maintaned in the BCOS_CUST table so that the message reaches the Service Desk.]
Currently I am using the RFC destination to the service desk client in the solution manager ie SIDCLNT200
Thanks in advance
Regards
Amit

Hi Amit,
I think your expectation is not correct. I understood, you can create a message in a satellite system and you can see the ticket in SolMan service desk. Then everything is configured correct. What you are now looking for is to see the ticket in a solution when the sat. system is part of the solution. This is not working. If you create out of a solution a service desk ticket, these ticket get a special attribute that they belong to this solution, all other tickets can not be selected by a solution.
Sorry but I am quite sure that it is working like this.
There is only one option, that you define special variants so you can see only tickets from special systems, but these variants can not be assigned to a solution.
Regards,
uDo

How to create a RFC destination for extracting data to HANA

Hello All,
Could someone help me in providing a document or note on how to create a RFC destination for extracting data from SAP data source to HANA using SAP LT replication server ?
I am able to create a data base connection while transforming data from non SAP data source,but wasnt able to transform data which is from SAP abap tables .

Hi Venkatesh,
In SM59 t.code we create RFC destinations.
Go thru the video link for creating RFC destinations step by step
How to setup a trusted RFC connection between SAP systems: a step-by-step guide - YouTube

No central node on RFC destinations in TDMS

Similar Messages

Maybe you are looking for