Limitations for gRPC Support
Integration Server provides the following support for gRPC features and functionality in this initial release:
Only API-first gRPC provider descriptors can be created. You can use
Designer to create a gRPC provider descriptor from an existing proto file for a gRPC service.
The proto file must be protocol buffers version 3 (proto3). Integration Server does not support creating a gRPC descriptor from a proto file that uses proto2 syntax.
Unary RPCs.
The predefined gRPC channel named GRPCDefault is the only supported gRPC channel. Additional gRPC channels cannot be created.
Integration Server does not support the following:
Client streaming, server streaming, or bidirectional streaming RPCs.
The gRPC field types: Any, Map, Oneof, Enum.
The gRPC Reflection protocol.
Compression for channels or messages.
Creation of gRPC consumer descriptors.
Creation of gRPC provider descriptors from existing IS services.
Using
Deployer to deploy gRPC descriptors and their supporting assets.
Configuration variables for gRPC channels.
Refreshing of gRPC descriptors.
Note:
Once created, the gRPC descriptor and all associated Integration Server artifacts, must remain in the Integration Server package and folder where they were created. Moving or renaming the generated folders, gRPC method flow services, and gRPC document types breaks the gRPC descriptor implementation.