webMethods and Intelligent Business Operations 10.2 | Integrating Cloud Applications | Administering CloudStreams | CloudStreams Configuration Options | The Administration Options | Setting the General Options
 
Setting the General Options
Use these options to manage the inbound service requests sent by consumers to CloudStreams. To manage the outbound requests that CloudStreams sends to the cloud provider, set the options for your cloud connections in your CloudStreams cloud connector. For details, see the section Creating Cloud Connections in the documentation for your CloudStreams cloud connector.
* To set the CloudStreams > Administration > General options
1. In Integration Server Administrator, select Solutions > CloudStreams > Administration > General.
2. Click Edit, complete the following fields and click Save.
Option
Description
Target Name
The CloudStreams target name. This name is included in the events that are sent to the database for metrics reporting purposes.
HTTP Load Balancer URL
The primary HTTP load balancer URL and port number to use.
For the URL, you can specify either the IP address or host name of the load balancer with the port number, as follows:
http://IP-address:portnumber
or
http://hostname:portnumber
If specified, all virtual services hosted in CloudStreams will use this value.
HTTPS Load Balancer URL
The primary HTTPS load balancer URL and port number to use.
For the URL, you can specify either the IP address or host name of the load balancer with the port number, as follows:
https://IP-address:portnumber
or
https://hostname:portnumber
If specified, all virtual services hosted in CloudStreams (and exposed on HTTPS) will use this value.
Keystore Name
The Integration Server keystore that CloudStreams should use. This field lists all available Integration Server keystores. If there are no configured Integration Server keystores, the list will be empty. To configure Integration Server keystores, see the section Securing Communications with the Server in the document webMethods Integration Server Administrator’s Guide.
Signing Alias
The signing alias. This alias is the value that is used to sign the outgoing response from CloudStreams to the original consumer. It is auto-populated based on the keystore selected from the IS Keystore Name above. This field will list all the aliases available in the chosen keystore. If there are no configured keystores, this field will be empty.
Truststore Name
Specify the same truststore that is specified in Integration Server (as described in the section Securing Communications with the Server in the document webMethods Integration Server Administrator’s Guide).
This truststore will be used in the following cases:
*If you select the Secure Connection option for a CloudStreams server as described in Defining and Managing a CloudStreams Server Target. The truststore you specify in the IS Truststore Name field must contain the required SSL certificates.
*This truststore is also used by the CloudStreams SMTP e-mail server if you select the TLS Enabled option while Setting the E-mail Options for Logging Payloads and Sending Performance Monitoring Alerts. The truststore you specify in the IS Truststore Name field must include a certificate in the e-mail server's certificate chain or the certificate authority of the e-mail server.
*This truststore is also used when making a connection to a third-party OAuth 2.0-based service provider to refresh the access token (as described in Setting the OAuth Tokens Options).
HTTP Ports
Select one or more HTTP ports on which CloudStreams and the deployed virtual services will be available.
CloudStreams is always available on the primary HTTP port. The primary HTTP port is the port specified on the Integration Server's Security > Ports page. You can specify additional HTTP and HTTPS ports here. To configure ports for Integration Server, see webMethods Integration Server Administrator’s Guide.
Note: If you specify multiple ports, the port that is reported in the WSDL is the non-primary port with the lowest number. There is only one port reported in the WSDL retrieved through CloudStreams, but all the specified ports are usable. If you are using a webMethods Enterprise Gateway (EG) Registration port to process requests from external clients, the EG port will be displayed with the EG hostname prefixed to the port, in order to distinguish it from the local internal server ports. The Enterprise Gateway Registration port must be specified for CloudStreams.
HTTPS Ports
Select one or more HTTPS ports on which CloudStreams and the deployed virtual services will be available.
Connection Factory Wire Logging
This option captures additional debug messages that show the request's HTTP content that is sent over the wire to the native provider. The messages also show the response content that was received. This can be useful when debugging connector service invocations, but there are two implications you should be aware of:
*The server.log will grow quickly as it captures this verbose content, and performance will be severely impacted. Use this option sparingly.
*Because all "cleartext" HTTP content is captured (even the content sent over SSL), be careful to avoid security issues. In addition to all request and response message content, the transport headers are also included, including Authorization headers.
Note: Enabling wire logging will reveal sensitive data, for example, user credentials and authorization headers in the logs. It is recommended to filter out or mask the sensitive data before sharing the logs.
If you disable and then re-enable the Connection Factory Wire Logging, in certain cases it may be necessary to disable and then re-enable any existing managed connection pools. To do this, in the Integration Server Administrator go to Solutions > CloudStreams > Providers, click your cloud provider's name, click the connector name, and click the Enabled column to disable/re-enable the connection pool.
Note: By default, Integration Server keeps archived server log files indefinitely. Because server.log files can rapidly become large or numerous when using more verbose logging levels, you might want to limit the number of server log files that Integration Server keeps on the file system. See the Limiting the Number of Server Log Files Kept by Integration Server section in the webMethods Integration Server Administrator’s Guide for more information.
If you enable Connection factory wire logging, requests and responses containing actual data will be logged in the Integration Server logs. This log data may contain account specific or user specific data, for example, email addresses, which may be considered as personal data or personal identifiable information. If for privacy concerns or to be in compliance with General Data Protection Regulation (GDPR), you want to delete the personal data of a user, you can manage the log files that contain the wire logging data from the file system. See the webMethods Integration Server Administrator’s Guide for information on how to manage these logs, their related files, and specific identifiers to look for in the logs.
Handle Binary Streams
Large data configuration enables CloudStreams to send and receive large binary streams over HTTP/HTTPS. If you enable Handle Binary Streams, then during outbound and inbound invocations, if the stream is greater than the Threshold Size (bytes), the entire stream is not stored in memory. Threshold Size (bytes) is applicable only if Handle Binary Streams is enabled. Before enabling the large data handling capability of CloudStreams, configure the TSpace properties (watt.server.tspace.*) in the webMethods Integration Server Administrator > Settings > Extended > Show and Hide Keys page. See the webMethods Integration Server Administrator’s Guide for information on the TSpace properties. After setting these values, restart Integration Server.
Note: Errors may appear if the watt properties are not configured properly. Increase the watt.server.tspace.max value in case of InsufficientSpaceException errors or increase the watt.server.tspace.timeToLive value incase of Connection reset by peer: socket write errors.
Keep the following points in mind regarding large data configuration:
*If the request/response payload is greater than the Threshold Size (bytes) and if the log request or response is greater than the specified Threshold Size (bytes), then the request/response will neither be logged in the database nor in the Integration Server log. This is designed to prevent the Integration Server and database logs from getting flooded with large number of log messages.
*If you want to send a large binary stream and if the back end supports HTTP chunking, ensure that you set the Use Chunking option in the connection configuration page to true. Else, heap space errors may appear even if large data handling is enabled.
*If you want to send a large binary stream but if the back end does not support HTTP chunking, then heap space errors may appear even if large data handling is enabled.
*Currently, Handle Binary Streams and Threshold Size (bytes) cannot be deployed using webMethods Deployer.
Copyright © 2015- 2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release