We want to better understand the other TP Monitor options : EJB Web Services, INTERNET, Web View

[Ben_D]

We are currently using the default TP Monitor selections : 

Operating System=JVM, DBMS=Oracle, TP Monitor=EJB.

We want to better understand the other TP Monitor options and how they are used. 

Can you please provide more info that is currently available in the toolset?

Thanks,

Ben 

[Lynn Williams]

Hi Ben,

In brief, you have probably seen that whatever you choose as the Operating System will then control what TP Monitors are listed.

 

I will cover what is available for Java i.e. JVM as you have shown that

EJB - applies to Java servers.

EJB Web Services - applies to Java servers plus also generates web services for them.

INTERNET - applies to the first generation of client web applications delivered with Gen i.e. Web Generation.

Web View - applies to the second generation of client web applications delivered with Gen i.e. Web View. However, that option should not be used from the Toolset any more and all Web View generation should be done from Gen Studio. Generation error messages will appear if it is tried to be used:

 

Here are some relevant doc. pages and you can also search the documentation for other relevant information:

https://techdocs.broadcom.com/us/en/ca-mainframe-software/devops/ca-gen/8-6/distributed-processing/working-with-distributed-processing/anatomy-of-a-dp-application.html

https://techdocs.broadcom.com/us/en/ca-mainframe-software/devops/ca-gen/8-6/distributed-processing/working-with-distributed-processing/anatomy-of-a-dp-application/client-execution-environments.html

https://techdocs.broadcom.com/us/en/ca-mainframe-software/devops/ca-gen/8-6/distributed-processing/working-with-distributed-processing/anatomy-of-a-dp-application/server-execution-environments.html
https://techdocs.broadcom.com/us/en/ca-mainframe-software/devops/ca-gen/8-6/developing/designing/using-the-toolset/perform-file-transfers-error/export-push-button/generation-defaults-dialog.html

 

I hope that information helps.

 

Please let us know if you have additional questions about the above or other Operating System options.

 

Regards

 

Lynn

------------------------------
Lynn Williams
Senior Principal Support Engineer
Broadcom Software
Australia
------------------------------

[Ben_D]

Hi Lynn,

    The attached information was very helpful.

    I think we may have a solution by using the CFB server to execute the EJB RMI code while just using TCP from the clients side.

Thanks,

Ben

[Lynn Williams]

Hi Ben,
Thanks for the update.

It sounds like you have Gen C clients rather than Java clients?

CFB Server is an option for connecting a C client to an EJB server.

However, I received some further advice from Gen Engineering.

These days the recommended approach would be to use the Web Services Coopflow option, rather than the Converter Services (i.e. the CFB Server or the C to Java RMI Coopflow).

The Web Services Coopflow has less overhead, so it usually performs better.

Also, the CFB Server could become a bottleneck in a high-volume transaction environment and might require having multiple CFB Servers configured to handle the load (and some kind of load balancer in front of them). 

 

In Gen's long history, the Converter Services were the original offering, but later the Web Services Coopflow was added for a better experience. The Converter Services in Gen are only kept for those who had already adopted it, but with the expectation that everyone would move to the Web Services Coopflow eventually. 

 

When using the Web Service Coopflow, you would need to generate your EJBs using the EJB Web Services TP Monitor option and configure the client side commcfg.ini file to use the Web Services Coopflow, as shown below:

 

# For Web Services the format is:

#           <TRANCODE> WS <baseURL> <contextType>

#                     baseURL: Scheme, Domain and Port of a Web Service end point URL

#                          ex: http://<hostname>:<port>

#                     contextType: part of the path of a Gen Web Service end point URL

#                          'P' to use ProcedureStep Name (with WebLogic)

#                          'W' to use with WildFly

#                          'J' to use with JBoss EAP

#                          'L' to use LoadModule Name (everywhere else)

I hope that information helps.

 

Regards,

 

Lynn

------------------------------
Lynn Williams
Senior Principal Support Engineer
Broadcom Software
Australia
------------------------------

[Ben_D]

Hi Lynn,

  

We have one follow up question of CFB – will the CFB server continue to be supported going forward, or are there any plans to stop supporting it?

Thanks,

Ben 

[Lynn Williams]

Hi Ben,
I discussed with the Gen product owner and there are currently no specific plans to stop support of the Converter Services including CFB Server, but that is likely to occur at some stage.
For the performance reasons I referred to above, we would still strongly encourage you to instead use Web Services Coopflow (EJB Web Services).

Hope that helps

Regards

Lynn

------------------------------
Lynn Williams
Senior Principal Support Engineer
Broadcom Software
Australia
------------------------------