[Migrated content. Thread originally posted on 11 August 2011]

We are running SEE 6.0 and Enterprise Server:

1] For communication directly between say a .net client application and a native cobol process would you say the best option would to use COM on both sides? If native cobol code needs to call .net then use a CCW on the .net code and if the .net code needs to call a native cobol process then use a RCW.

Where:
CCW - COM Callable Wrapper (wraps the .net code as a COM Service)
RCW - Runtime Callable Wraper (wraps the native cobol process in a COM service)

2] I would say for the best performance this COM interfacing is the best option over P/Invoke because I have read there are some multi-threaded issues with IIS.

3] For straight services for for use by both the .net and native clients "Direct Web Services for Cobol" web services would be the best choice for slowly moving processes from pure native cobol environment to .net (vs2010/c# 4.0, FW 4.0), is this correct?

4] Interface Mapping Toolkit can make the native cobol processes into wrapped COM RCWs?

5] Interface Mapping Toolkit can make the native cobol processes into "Direct Web Services for Cobol"? I'm assuming from everything I have read that these are basic WS-I HTTP web services.

6] Can the Interfac Mapping Toolkit make new WCF web service end points like say a TCP/IP end point?

7] If WCF web services can be used with Enterprise Server environment then what level of WCF? Will it work with WCF 4.0?

Any and all help and direction is greatly appreciated!!
Thanks!! Jerry

#EnterpriseDeveloper