Configure SAP RFC destinations – ECM Only

base configuration for ecm requires (at least one) sap rfc to be created this allows link enterprise ecm within sap to execute rfc calls to an instance of the enterprise connector (in theory you can utilize more than one) acting as an sap jco server the rfc destination configured here will be selected in the link enterprise configuration outlined the step base sap link enterprise configuration – ecm only (api destination) destination name z cmsapi 01 we suggest the following naming convention z cmsapi \<number> but any destination name can be used connection type t (tcp/ip connection) technical settings select registered server program radio button program id z cmsapi 01 we suggest to keep the program id name the same as the rfc destination name for simplicity as this will need to match the program id in the enterprise connector gateway options (optional if only one gateway host for the sap environment) gateway host \<insert the gateway host to use> gateway service \<insert the gateway service to use> unicode select unicode radio button note you cannot test the rfc destination until the enterprise connector has at least 1 rfc destination (outbound rule) configured is also completed below and the windows service is running when the windows service is installed, configured and running, refer to section milestone establish sap < > enterprise connector connectivity configuration to test connectivity the program id and gateway host and service must match that configured in the enterprise connector (section “base enterprise connector configuration”), work with your gimmal link enterprise configurator to ensure this is the case you may need to repeat rfc destination creation above for additional processing threads and load balancing initially however only one rfc destination is needed important this rfc destination chosen must match the api destination configured in link enterprise connector in step base enterprise connector configuration – ecm only