Do not use older or non-standard protocols

In a cloud environment, certain protocols related to EJB 2.0, CICS Transaction Gateway, and IMS Connect are not supported. Updating your applications to use newer, standardized protocols, such as an HTTP-based infrastructure that incorporates REST, makes it easier to port your applications to new environments. You can also assess whether asynchronous protocols, such as IBM MQ or MQTT, are a good choice for your application needs.

Protocols related to EJB 2.0 are not supported. Update your application to use EJB 3.0 or later. This rule flags references to t3://, iiop:// and corbaloc: in the following locations:

• In Java string literals
• In the java.naming.provider.url property value in the jndi.properties files

For CICS Transaction Gateway, the tcp, ssl, and local protocols are not supported. Use the http and https protocols instead. This rule flags references to tcp://, ssl://, and local: in the following locations:

• In Java string literals
• In the com.ibm.ctg.JavaGateway and com.ibm.ctg.epi.EPIGateway constructors
• In the com.ibm.ctg.JavaGateway and com.ibm.ctg.epi.EPIGateway methods setProtocol(String) and setURL(String)
• In the com.ibm.connector2.cics.CICSManagedConnectionFactory.setConnectionURL(String) method

IMS Connect is not supported. This rule flags references to the IMS Connect API for Java provided by the com.ibm.ims.connect package.

For more information, see Top 9 rules for cloud applications.