Default Global Mailbox and Sterling B2B Integrator configuration
When you install Global Mailbox and Sterling B2B Integrator, the installer sets some default configurations based on the values that you specify during installation.
The default configuration includes property files, application registration, services, and adapters and business process in Sterling B2B Integrator, Apache Cassandra, Apache ZooKeeper. The following sections provide details about the default configuration.
The global.properties and installinfo.properties files are in the config folder in the shared storage path that you specified during the installation. The mailbox.properties file is in /<install_dir>/install/wlp/usr/servers/mailboxui (used by the Global Mailbox management node) and /<install_dir>/MailboxUtilities/admin/conf (used by command line utilities) folders.
The global.properties file contains the properties that are shared by all nodes in all data centers. The datacenter.properties file contains properties that are shared by all nodes in the local data center. Properties that are specified in the datacenter.properties file override the same properties that are specified in the global.properties file. Properties that are specified in mailbox.properties override the same properties that are specified on datacenter.properties and global.properties.
When you install additional Global Mailbox nodes (second or subsequent in the same data center or first node in the second data center), the global.properties and installinfo.properties files are copied to the shared storage path that you specified when you installed the additional nodes.
The properties in these files contain the configuration for the Cassandra nodes, ZooKeeper nodes, replication settings, Cassandra consistency, and Global Mailbox. For more information about the properties in the property files, see Global Mailbox properties files reference.
When a Global Mailbox node is installed (with Sterling B2B Integrator or on an existing Sterling B2B Integrator node), the installer registers the
Sterling B2B Integrator node in Global Mailbox by using the
- User lookup service
- User lookup service is configured per data center, which means a Global Mailbox Management node accesses user lookup service URLs for Sterling B2B Integrator servers that are in the same data center. When requested, Global Mailbox uses the user lookup service to look for active users, groups, and administrators in Sterling B2B Integrator. Global Mailbox administrator can look for required users and groups and assign appropriate permissions to global mailboxes. For more information about user lookup service, see Global Mailbox REST Services.
- Event properties service
- Event properties service is configured per data center, which means a Global Mailbox Management node accesses event properties service URLs for Sterling B2B Integrator servers that are in the same data center. When creating or editing an event, a Global Mailbox administrator can look for properties such as, business process name, contracts, and authorized users. Global Mailbox uses the event properties service to look for these properties. For more information about event properties service, see Global Mailbox REST Services.
- SSL configuration
- SSL is configured across data centers. The SSL configuration is used to make secured outbound
connection when connecting to the application for user lookup, event property lookup, or single
appConfigUtilitySSL settings are independent of the Liberty SSL settings, which are used to secure inbound browser connections to the Global Mailbox admin UI.
- WebSphere® MQ cluster configuration
- Configuration for the WebSphere MQ cluster is shared across data centers. Global Mailbox uses the WebSphere MQ configuration to notify Sterling B2B Integrator about the various events in the global mailboxes. Though WebSphere MQ configuration is specified during installation, it is not stored in the property files. The configuration is stored in Cassandra because it is specific to Sterling B2B Integrator node.
- Single sign-on
- Single sign-on configuration allows a Sterling B2B Integrator to access the Global Mailbox admin UI by clicking a link in the Sterling B2B Integrator dashboard, without having to provide log in credentials to Global Mailbox.
appConfigUtilityscript with appropriate option.
For more information about
appConfigUtility, see appConfigUtility script.
Services and adapters in Sterling B2B Integrator
- Global Mailbox Configuration Adapter (GMCA)
GMCA is used to manage access to Global Mailbox from Sterling B2B Integrator. For new installations, the GMCA is by default installed in the ASI node. For upgrades, the GMCA remains on the Container Adapter. However, a copy of GMCA is created on the ASI node. The GMCA must be installed and configured on any node that has an adapter or service to access the Global Mailbox functionality. For example, to run a Global Mailbox enabled FTP Server Adapter on an Adapter Container node, you must also have a Global Mailbox Client Adapter on that node.
Even after GMCA, ERA, and Protocol Adapter are all installed in the ASI node, you can create a copy of the GMCA and define a Protocol Adapter on the AC node. The GMCA copy and Protocol Adapter on AC are automatically used to upload files when the ASI node goes down. However the processing of the files occur only in the ASI node after the node is up.
GMCA uses the configuration information such as, information about Cassandra and ZooKeeper hosts, and replication settings from global.properties and datacenter.properties files. Additionally, the global_mailbox.properties file is used by GMCA in Sterling B2B Integrator. The file specifies GMCA configuration such as, sessionCacheMaxSize, inlinePayloadMaxSize. For information about GMCA parameters, see Global Mailbox Client Adapter.
- Global Mailbox Event Rule Server Adapter
- The Global Mailbox Event Rule Server adapter listens to the events generated by Global Mailbox and accepts the events over WebSphere® MQ when the events are available. The Event Rule Adapter is by default installed or upgraded in the ASI node. For information about Global Mailbox Event Rule Server Adapter parameters, see Global Mailbox Event Adapter.
- Global Mailbox REST Services Adapter
- The Global Mailbox REST Services adapter provides configuration for the REST services that are required by Global Mailbox. The adapter is an instance of the HTTP Server adapter. User lookup and event property rest services are currently supported. The REST Services Adapter is by default installed in the ASI node.
Business process in Sterling B2B Integrator
RoutingRuleGMMsgStatusMonitor business process is defined in Sterling B2B Integrator when Global Mailbox is installed. The business
process is used to monitor the status of the business process that is started to process a message
from the Global Mailbox. For more
RoutingRuleGMMsgStatusMonitor, see RoutingRuleGMMsgStatusMonitor Business Process.
Apache Cassandra and Apache ZooKeeper
Cassandra configuration files are created in <install_dir>/apache-cassandra/conf. Cassandra ports and cluster topology information can be found in the configuration files. The cassandra.yaml file is the main configuration file for Cassandra. For more information about cassandra.yaml file, see cassandra.yaml properties file.
ZooKeeper configuration files are in <install_dir>/zookeeper/conf. The main configuration is zoo.cfg. The file provides information about the ports and the topology that are provided during the installation.
When Global Mailbox is installed, the
installer runs the provision bucket script and sets up the
global_mbx bucket. The
bucket is set to use shared storage path that you provide for the local data center, during
installation. For more information, see Storage. Another default bucket,
1st_provisioned is also created. However,
the bucket is not used by Global Mailbox. Do
not delete either of these system default buckets.
Apart from the default SSL and single sign-on the installer does not configure any default security settings. For more information about security, see Security options.