Release Notes / Version 13.2512.1
Table Of Contents
Starting with CMCC 13 (release 2512.0), gRPC was introduced as an
inter-component protocol - alternative to CORBA. It was activated with
environment variable REPOSITORY_USEGRPC=true or
property repository.use-grpc=true. CORBA stayed the
default protocol, if neither the environment variable nor the property
were defined. Now, gRPC is the default protocol, if nothing else is
specified.
As CORBA will be removed with CMCC 14 and gRPC be the only protocol henceforth, CORBA-related API has been deprecated. This applies to the following APIs:
com.coremedia.cap.CapCONTENT_SERVER_URL,WORKFLOW_SERVER_URL, andORB: IOR URLs and ORB are not required with gRPCconnect(String, String, String, String):CapConnection,connect(String, String, String):CapConnection, andconnect(String):CapConnection: connection via IOR ULR not supported with gRPC. See manuals on how to establish a UAPI connection via gRPC.unfoldParameterMap(Map<String,?>):Map<String,Object>: with the removal of IOR URLs including connection parameters as query part, this method will be obsolete.
com.coremedia.workflow.errorcodes.WfErrorCodes: CORBA-related error codes will be obsolete.com.coremedia.cmdline.CapConnectionParameterCustomizerBuilder#iorUrl(String):CapConnectionParameterCustomizerBuilder: with the removal of IOR URLs, this method will be obsolete.
Upgrade Information
If you want to use CORBA as the communication protocol, use
environment variable REPOSITORY_USEGRPC=false or
property repository.use-grpc=false with each
CoreMedia component. For Docker Compose setups, files
corba.yml and elastic-corba.yml
are provided. Compose files grpc.yml and
elastic-grpc.yml have been removed and must thus be
removed from your Docker Compose setups as well.
As before, Content Servers and Workflow Server always offer both CORBA
and gRPC services to their clients, regardless of settings
REPOSITORY_USEGRPC and
repository.use-grpc.
(CMS-31343)
