Application Integration (On-Premises) : Administering the Software AG Infrastructure : Using Command Central to Manage Infrastructure : Configuration Types that the OSGI Profile Components Support
Configuration Types that the OSGI Profile Components Support
The OSGI profile run-time components support creating instances of one or more of the following configuration types:
*COMMON-JAAS
*COMMON-JVM-OPTIONS
*COMMON-LDAP
*COMMON-LOCAL-USERS
*COMMON-LOG
*COMMON-MEMORY
*COMMON-PORTS
*COMMON-PROXY
*COMMON-SYSPROPS
The following sections provide more detail about each configuration type and list the products whose OSGI profile supports each configuration type.
COMMON-JAAS
Use to configure profile authentication and authorization configuration:
installation_directory/profiles/product_code/configuration/jaas.config file
For Command Central and Platform Manager, the jaas.config file is located under:
installation_directory/profiles/product_code/configuration/security/jaas.config file
Note:  
For the product_code in the directory path, refer to the description of COMMON-SYSPROPS.
Products whose OSGI profile supports COMMON-JAAS: Command Central, Platform Manager, Software AG Runtime
COMMON-JVM-OPTIONS
Use to configure extended JVM options.
Products whose OSGI profile supports COMMON-JVM-OPTIONS: Command Central, Platform Manager, Software AG Runtime, Integration Server, My webMethods Server
COMMON-LDAP
Use to configure a connection to an external LDAP directory.
Products whose OSGI profile supports COMMON-JAAS: Command Central, Software AG Runtime, Integration Server
COMMON-LOCAL-USERS
Use to manage internal users for a product instance.
Products whose OSGI profile supports COMMON-LOCAL-USERS: Command Central, Platform Manager, Integration Server, My webMethods Server, Universal Messaging
COMMON-LOG
Use to configure log levels for log categories and log file locations.
Products whose OSGI profile supports COMMON-LOG: Command Central, Platform Manager, Software AG Runtime
COMMON-MEMORY
Use to configure common memory settings, such as Initial Heap Size and Maximum Heap Size. Configuring extended JVM options using COMMON-MEMORY is deprecated. To configure extended JVM options, use COMMON-JVM-OPTIONS.
Products whose OSGI profile supports COMMON-MEMORY: Command Central, Platform Manager, Software AG Runtime
COMMON-PORTS
Use to configure the HTTP, HTTPS, JMX, JDWP (Debug), and/or SSH ports. The following tables lists products that have OSGI profile components that support COMMON-PORTS and the types of ports each support.
Port type
Products whose OSGI profile supports this port type
Description
HTTP
Command Central
Platform Manager
Software AG Runtime
The HTTP port is enabled by default. You can use the command line interface to add, remove, edit, and validate the HTTP port.
HTTPS
Command Central
Platform Manager
Software AG Runtime
The HTTPS port is enabled by default. You can use the command line interface to add, remove, edit, and validate the HTTPS port.
JMX
Command Central
Integration Server
My webMethods Server
Platform Manager
Software AG Runtime
The JMX port is enabled by default. You can use the command line interface to add, remove, and edit the JMX port. You can only define one JMX port.
JDWP (Debug)
Command Central
Integration Server
My webMethods Server
Platform Manager
Software AG Runtime
The JDWP (Debug) port is disabled by default. You can use the command line interface to edit this port, but not to remove or add it. This port is used when the run-time component is started in debug mode using the sagcc exec lifecycle command.
SSH
Command Central
Integration Server
My webMethods Server
Platform Manager
Software AG Runtime
The SSH port is disabled by default. You can use the command line interface to add, remove, and edit the SSH port. You can only define one SSH port.
COMMON-PROXY
Use to configure proxy server settings if you must route server requests through a third party server. Based on the transport protocol, COMMON-PROXY has the following configuration types:
Configuration types
Description
COMMON-PROXY-HTTP
Use to configure proxy settings over the HTTP protocol.
COMMON-PROXY-HTTPS
Use to configure proxy settings over the HTTP protocol.
COMMON-PROXY-FTP
Use to configure proxy settings over the FTP protocol.
COMMON-PROXY-SOCKS
Use to configure proxy settings over the SOCKS protocol.
COMMON-PROXY-ALL
Use to indicate whether to use the operating system proxy settings instead of COMMON-PROXY-* configuration.
You cannot edit or delete this configuration type.
Run-time components whose OSGI profile supports the COMMON-PROXY configuration type: Command Central, Platform Manager, Software AG Runtime, My webMethods Server
Note:  
Integration Server supports COMMON-PROXY configuration type at the ENGINE level.
You can use the Command Central web user interface to add, view, edit, and delete a proxy server configuration. After you add a new proxy server configuration, you must restart Platform Manager for the changes to take effect.
You can also create, get, update and delete proxy server settings using the configuration commands in the Command Central command line interface. When creating or updating a proxy server configuration instance, the input XML file that contains the proxy server configuration data must use the following format:
<?xml version="1.0" encoding="UTF-8"?>    
<Proxy alias="HTTPS">    
  <Enabled>true</Enabled>    
  <Protocol>HTTPS</Protocol>    
  <Host>hostName</Host>    
  <NonProxyHosts>host1,host2</NonProxyHosts>    
  <Port>12321</Port>    
  <Username>user</Username>    
  <Password>secure</Password>    
</Proxy>
The following table describes the values you provide for each of the parameters in the proxy server configuration data XML file:
For this parameter...
Specify...
Alias
The alias name to use for this host/port combination. The Alias and Protocol parameters should have the same value.
Enabled
Whether to enable the proxy server configuration instance. By default, the existing proxy server configurations except COMMON-PROXY-ALL are enabled. Valid values are:
*true Enabled
*false Disabled
The COMMON-PROXY-ALL configuration type is not enabled by default. For the COMMON-PROXY-ALL configuration type the Enabled parameter indicates whether to use the proxy settings of the operating system and ignore any other COMMON-PROXY-* configurations.
Protocol
The type of protocol to use for the host/port combination. The Alias and Protocol parameters should have the same value.
Host
The host name or IP address of the proxy server. For the COMMON-PROXY-ALL configuration type, you can also specify noHost.
NonProxyHosts
You can optionally route selected requests directly to their targets, bypassing the proxy. To specify non-proxy hosts, type the fully qualified host and domain name of each server that should receive requests directly. To enter multiple names, separate each with commas.
Port
The port on which this proxy server listens for requests. Specify a valid port number in the range of [1-65535].
Username
The user name to use to access this proxy server.
Password
The password to use to access this proxy server.
All proxy server configuration settings are stored in the config.ini configuration file under the OSGI run-time component profile directory. You must not modify or edit the config.ini configuration file.
COMMON-SYSPROPS
Use to configure the OSGI profile properties defined in the config.ini configuration file:
installation_directory/profiles/product_code/configuration/config.ini file
Note:  
Under normal circumstances, you must not modify the config.ini file. It should only be modified by the Software AG Installer.
The following tables lists products that have OSGI profile components that support COMMON-SYSPROPS and the product_code used in the directory path to the location of the config.ini for that product.
Products whose OSGI profile supports COMMON-SYSPROP
product_code used in the directory path to the config.ini file
Command Central
CCE
Integration Server
IS_instancename
where instancename is the name of the Integration Server instance, for example, “IS_default”.
My webMethods Server
MWS_instancename
where instancename is the name of the My webMethods Server instance, for example, “MWS_default”.
Platform Manager
SPM
Software AG Runtime
CTP
Copyright © 2015- 2016 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback