Integration Server 10.11 | Integration Server Administrator's Guide | Configuring gRPC in Integration Server | Working with gRPC Channels | Editing a gRPC Channel
 
Editing a gRPC Channel
To use the predefined gRPC channel, you must edit the channel to specify:
*An unused port for the machine on which Integration Server resides.
Note:
The port used by a gRPC channel is not an Integration Server port that can be configured using Integration Server Administrator. Instead, the gRPC channel port is an HTTP/2 port managed by the gRPC server embedded in Integration Server.
*The keystore, key, and truststore information needed for two-way authentication. The GRPCdefault channel lists the DEFAULT_IS_KEYSTORE and DEFAUL_IS_TRUSTSTORE as the default keystore and truststore for the channel, respectively. However, these are placeholders that you need to replaced with keystore, key alias, and truststore specific to your organization. For information about creating keystores and truststores, see Keystores and Truststores.
For the GRPCdefault channel, the Name, Description, and Package property values cannot be edited. Additionally, as the predefined channel is the only channel allowed, it is always the default channel.
*To edit a gRPC channel
1. Open Integration Server Administrator.
2. Go to Settings > gRPC. In the gRPC Channel List, click GRPCDefault.
3. On the Edit channelName page, in the Port field, specify the HTTP/2 port on which the channel receives and sends requests. This must be an unused port on the machine that hosts Integration Server.
When you change the port number, upon save of the channel, Integration Server unregisters all gRPC descriptors and their gRPC method flow services associated with that channel from the original port and registers them on the new port. Any in-flight requests to the old port will fail.
Note:
You must notify any gRPC clients that call a gRPC method flow service associated with a channel of changes to the port number for a channel.
4. Under gRPC Channel Credentials, specify the following information for authentication:
Field
Description
Keystore Alias
The alias for the keystore that contains the key alias used by the gRPC server for SSL/TLS support.
Key Alias
The alias to the key entry that contains the private key used by the gRPC server for its SSL/TLS support. This key alias contains the private key used by the server as well as the certificate chain used to sign that certificate. The key alias must be in the keystore specified in Keystore Alias.
Truststore Alias
The alias for the truststore that contains the client certificates (public key and certificate chain) user for two-way SSL.
5. Click Save Changes.