In either case, if you are using an EJB session bean, you must generate a Java wrapper, if only to generate the EJB session bean.
If you wish to use an EJB session bean, you must generate the calling program or wrapper with a linkage options part in which the value of property type for the called program is ejbCall. You cannot make the decision to use a session bean at deployment time. If you set the property remoteBind to RUNTIME, however, you can decide at deployment time how the EJB session bean accesses the generated program, although making this decision at generation time is more efficient.
localCall is the default value
If the caller is Java code, communication is handled by the protocol specified in property remoteComType; the protocol choice indicates whether the called program is in the same or a different thread.
Related concepts
Linkage options part
Related tasks
Editing the callLink element of a linkage options part