Let's follow up this discussion at the Neptune Community

(this forum will be kept in read-only mode)

RFC function modules

 Hi,


in UX4.0 these function modules are RFC enabled:


used by Designer:
/NEPTUNE/CLASS_EXISTENCE
/NEPTUNE/GET_BINDING_DATA_CLS

used by Server
(*) /NEPTUNE/SERVER_ONAJAX
(*) /NEPTUNE/SERVER_ONREQUEST
(*) /NEPTUNE/SERVER_ONRESPONSE

/NEPTUNE/SERVER_ONSUBMIT
/NEPTUNE/SERVER_ONSYNC_IN
/NEPTUNE/SERVER_ONSYNC_OUT


In order to maximize security, we only have authorized RFC access for the marked (*) server function modules.


Is it correct to assume that the other ones are not to be used by newly developed apps anymore??


Best regards,

Kay


1 person has this problem

Ok, thanks for the clarification!

Best regards,
Kay

 

For running an app you will need the following 6:


/NEPTUNE/SERVER_ONAJAX
/NEPTUNE/SERVER_ONREQUEST
/NEPTUNE/SERVER_ONRESPONSE

/NEPTUNE/SERVER_ONSUBMIT
/NEPTUNE/SERVER_ONSYNC_IN
/NEPTUNE/SERVER_ONSYNC_OUT


All of them are used by  class   /NEPTUNE/CL_NAD_SERVER.


1 person likes this
I assume that as a developer, the FMs used by the Designer are necessary.

But is authorizing users for the marked FMs sufficient for running an app in a productive environment?

 

Hi Kay,


your assumption is correct if and only if you are not going to develop new apps using the  Frontend / Backend Split  setup option  (which makes use of RFC calls).


Kind regards,

Julian

Login or Signup to post a comment