Copyright © Cloud Software Group, Inc. All Rights Reserved

Set Runtime Properties

You can set the runtime properties of the Core Engine using the Config UI . Select the Gateway Engine Properties in the drop-down list next to icon on the home page of the Config UI.

Using the Config UI, the runtime properties can be set to the following links:

•

General

•	Monitoring

•

Database

•

Transport

•

Security

On the home page of the Config UI, select the Gateway Engine Properties to display the runtime properties of the Core Engine. These properties are saved in the ASG_CONFIG_HOME/asg.properties and ASG_CONFIG_HOME/asg_cl.properties files respectively.

General Properties

To set the General properties, follow these steps:

1.	Select the Gateway Engine Properties from the drop-down list.

2.	Click the General link:

Table 59 General Properties

Property	Description
Common
Example Home	Specifies the home location for the examples directory shipped with TIBCO API Exchange Gateway. For example, the home directory for the examples location is as follows: ASG_HOME/examples
Allow Hot Update	Select this check box to set the value to true.If the check box is not selected, the value is set to false. The default is false. • If this check box is set to true, the hot configuration update is enabled. • If this check box is set to false, the hot configuration update is disabled.
Enable Default Operation	Select this to enable the default operation feature. See Pass-Through Gateway.

Monitoring Properties

To set the Monitoring properties, follow these steps:

1.	Select the Gateway Engine Properties from the drop-down list.

2.	Click the Monitoring link.

Table 60 Monitoring Properties

Property	Description
Generic
Use Synchronous HTTP Client	A boolean field used to send a request to the target side by running the http client in the same thread as the facade processing. Using the synchronous http client is recommended when high load of short lived requests are expected. Select this check box to set the value to true.If the check box is not selected, the value is set to false. The default is false. • If this check box is set to true, the client sends the synchronous request for the HTTP transport. • If this check box is set to false, the asynchronous request is sent for the HTTP transport.
Number of Threads	The number of threads used for the HTTP Client. This is relevant only if the value of useSynchHttpClient is false (that is, when asynchronous request is sent for the HTTP transport). The default value is 10
ModRV North Request Subject Name	Specifies the Rendezvous subject name, which is used by the Core Engine to listen for requests from the Apache module. The default value is _LOCAL.asg.north.request
RV Subject Prefix	Specifies the prefix for all Rendezvous subject names used between the Core Engine and Central Logger, Core Engine and Global Throttle Manager components. The default value is TIBCO.ASG.INTERNAL
Throttle Update Interval (sec)	Specifies the time interval (in seconds) for sending throttle updates to the Global Throttle Manager. The default value is 10
Request Binary	The default value is _LOCAL.asg.north.request_binary
RV Daemon	Specifies the value of Rendezvous daemon for the Core Engine to listen for the requests from the Apache module. The default value is tcp:7500
RV Network	Specifies the value of the Rendezvous network for the Core Engine to listen for the requests from the Apache module.
RV Service	Specifies the value of the Rendezvous service for the Core Engine to connect and listen for the requests from the Apache module. The default value is 7500
GTM RV Daemon	Specifies the value of the Rendezvous daemon for the Core Engine to connect to the Global Throttle Manager. The default value is tcp:7500
GTM RV Network	Specifies the value of the Rendezvous network for the Core Engine to connect to the Global Throttle Manager.
GTM RV Service	Specifies the value of the Rendezvous service for the Core Engine to connect to the Global Throttle Manager. The default value is 7500
Logging
Enable Reporting to Central Logger	Specifies if the reporting to the Central Logger is enabled or not. By default, the Core Engine does not record the transactions to the Central Logger. The default value is false. See Enable Reporting to the Central Logger.
Logging Interval (ms)	Specifies the time interval (in milliseconds) between Core Engine and Central Logger to record transactions. The default value is 30000
Minimum Log Level	Specifies the logging level for the Central Logger component. The possible values are as follows: • DEBUG • INFO • WARN • ERROR • NO LOGGING The default value is DEBUG
Central Logger Log Level	Specifies if the detail level logging is enabled for the Central Logger component. The possible values are as follows: • Detail Logging ON • Detail Logging OFF If the detail logging is set to ON, all the details of transaction are logged. If the detail logging is set to OFF, the Central Logger records the high level transaction. The default value is Detail Logging OFF

Transport Properties

To set the Transport properties, follow these steps:

1.	Select the Gateway Engine Properties from the drop-down list.

2.	Click the Transport link.

Table 61 Transport Properties

Property	Description
Facade
Port	Specifies the port through which the gateway accepts the HTTP requests from the client. The default value is 9222
Active Spaces
Transport Type	Type of the transport for Global Throttle Manager and Central Logger. Select AS from the drop-down list.
Metaspace Name	The name of the ActiveSpaces Metaspace to connect to. A metaspace is a a logical group of spaces—a cluster of hosts and processes that share the same metaspace name and set of discovery transport attributes. The hosts and processes in a metaspace work together by joining the same spaces. Refer to the TIBCO ActiveSpaces Developer's Guide for details on Metaspaces. The default value for the metaspace name is GTM.
Discovery URL	Specifies the discovery URL to use to discover spaces in the cluster. The TCP discovery has the following format: tcp://ip1[:port1];ip2[:port2],... where any number of ip[:port] well-known addresses can be listed. If no port isspecified, the default port number value of 50000 is assumed. For example, tcp://127.0.0.1:13000 Refer to the TIBCO ActiveSpaces Developer's Guide for details on the discovery URLs.
Listen URL	Specifies a URL that is used for direct communication between the members of the metaspace. To use a listen URL, use a string of the form: tcp://[interface[:port]] This syntax specifies that the member should bind to the specified interface and the specified port when creating the TCP socket that will be used for direct communication between the members of the metaspace. If not specified, it will default to 0.0.0.0 (INADDR_ANY) for the interface and to the first available port starting from port 5000 and above. For example, tcp://127.0.0.1:13000-*/
Log Level	The logging level of the messages when the ActiveSpaces channel is used. The default value is INFO. The possible values are as follows: INFO WARN ERROR FATAL FINE FINER FINEST NONE
Log Directory	The directory to store the log files. The log files contain the messages when the ActiveSpaces channel is used. The default value is ASG_CONFIG_HOME/logs For example, C:/TIBCO_HOMEAPIXCONFIG/tibco/cfgmgmt/asg/logs
SSL
Port	Specifies the port through which the gateway accepts SSL enabled HTTP requests from client. The default value is 9233
Use SSL	This is a boolean field which indicates if SSL should be enabled for accepting the HTTPS requests. If this is set to true, SSL is enabled to accept the requests using the HTTPS transport.
Identity Resource	Specifies an identity resource which is used by FacadeHTTPSSLConnection HTTP shared resource to provide the SSL properties.
Identity File Type	Specifies the type of identity resource. The possible values are as follows: − Identity File − Certificate/Private Key • If Identity File Type is of the Identity File type, enter the Identity Type, Identity URL, and Identity File Password parameters. • If Identity File Type is of the Certificate/Private Key type, enter Certificate URL, Key URL, and Key Password parameters.
Identity Type	Specifies the type of the keystore if the Identity File Type is of the Identity File type. The supported values are as follows: − JCEKS − JKS − PEM − PKCS12
Identity URL	Specifies the URL to the identity file if Identity File Type is of the Identity File type. For example, C:\asgserver.pfx
Identity File Password	Specifies the password for the identity file used for the SSL connection if Identity File Type is of the Identity File type.
Certificate URL	Specifies the URL to the certificate file if Identity File Type is of the Certificate/Private Key type.
Key URL	Specifies the URL to the private key in the certificate file if Identity File Type is of the Certificate/Private Key type.
Key Password	Specifies the password for the private key used for the SSL connection if Identity File Type is of the Certificate/Private Key type.
Requires Client Authentication	Indicates a boolean flag to enable or disable mutual SSL authentication for HTTPs transport between the client and the gateway. When this field is set to true, the Trusted Certificates Folder becomes enabled so that you can specify a location containing the list of trusted certificate authorities.
Truststore Password	Specifies the password to access the certificate stored in the folder defined by Trusted Certificate Folder field.
Trusted Certificate Folder	Specifies a folder containing one or more certificates from trusted certificate authorities, which is required for mutual SSL authentication. Required when the RequiresClientAuthentication property is set to true.
JMS Facade ESB Connection
JMS Provider URL	Specifies the connection URL for the EMS Server used for facade operation requests from the ESB communication domain. The ESB communication uses JMS transport with XML. The default value is tcp://localhost:7222
JNDI Context URL	Specifies the URL to the JNDI service provider used for facade operation requests with ESB communication domain. The default value is tibjmsnaming://localhost:7222
Topic Connection Factory Name	Specifies the name of TopicConnectionFactory object stored in JNDI. This object is used to create a topic connection with ESB services at the facade side. The default value is TopicConnectionFactory
Queue Connection Factory Name	Specifies the name of QueueConnectionFactory object stored in JNDI. This object is used to create a queue connection with ESB services at the facade side. The default value is QueueConnectionFactory
JNDI Username	Specifies the user name for logging into the JNDI server in the ESB communication domain at the facade side. If the JNDI provider does not require access control, this field can be empty. The default value is admin
JNDI Password	Specifies the password for logging into the JNDI server in the ESB communication domain at the facade side. If the JNDI provider does not require access control, this field can be empty.
JMS Username	Specifies the user name for logging into the EMS server in the ESB communication domain at the facade side. The default value is admin
JMS Password	Specifies the password for logging into the EMS server in the ESB communication domain at the facade side.
Request Queue	Specifies the queue name for an ESB channel (one) communication for the target operation request. The default value is asg.out.request
Reply Queue	Specifies the queue name for ESB channel (one) communication for the response from the target operation. The default value is asg.out.request.reply.0.0
JMS Target ESB Connection Primary
JMS Provider URL	Specifies the connection URL for the EMS Server used for facade operation requests from ESB communication domain. ESB communication uses JMS transport with XML. The default value is tcp://localhost:7222
JNDI Context URL	Specifies the URL to the JNDI service provider used for facade operation requests with ESB communication domain. The default value is tibjmsnaming://localhost:7222
Topic Connection Factory Name	Specifies the name of TopicConnectionFactory object stored in JNDI. This object is used to create a topic connection with ESB services at the facade side. The default value is TopicConnectionFactory
Queue Connection Factory Name	Specifies the name of QueueConnectionFactory object stored in JNDI. This object is used to create a queue connection with ESB services at the facade side. The default value is QueueConnectionFactory
JNDI Username	Specifies the user name for logging into the JNDI server in the ESB communication domain at the facade side. If the JNDI provider does not require access control, this field can be empty. The default value is admin
JNDI Password	Specifies the password for logging into the JNDI server in the ESB communication domain at the facade side. If the JNDI provider does not require access control, this field can be empty.
JMS Username	Specifies the user name for logging into the EMS server in the ESB communication domain at the facade side. The default value is admin
JMS Password	Specifies the password for logging into the EMS server in the ESB communication domain at the facade side.
Request Queue	Specifies the queue name for an ESB channel (one) communication for the target operation request. The default value is asg.out.request
Reply Queue	Specifies the queue name for the ESB channel (one) communication for the response from the target operation. The default value is asg.out.request.reply.0.0
JMS Target ESB Connection Secondary
JMS Provider URL	Specifies the connection URL for the EMS Server used for facade operation requests from the ESB communication domain. The ESB communication uses JMS transport with XML. The default value is tcp://localhost:7222
JNDI Context URL	Specifies the URL to the JNDI service provider used for facade operation requests with ESB communication domain. The default value is tibjmsnaming://localhost:7222
Topic Connection Factory Name	Specifies the name of TopicConnectionFactory object stored in JNDI. This object is used to create a topic connection with ESB services at the facade side. The default value is TopicConnectionFactory
Queue Connection Factory Name	Specifies the name of QueueConnectionFactory object stored in JNDI. This object is used to create a queue connection with ESB services at the facade side. The default value is QueueConnectionFactory
JNDI Username	Specifies the user name for logging into the JNDI server in the ESB communication domain at the facade side. If the JNDI provider does not require access control, this field can be empty. The default value is admin
JNDI Password	Specifies the password for logging into the JNDI server in the ESB communication domain at the facade side. If the JNDI provider does not require access control, this field can be empty.
JMS Username	Specifies the user name for logging into the EMS server in the ESB communication domain at the facade side. The default value is admin
JMS Password	Specifies the password for logging into the EMS server in the ESB communication domain at the facade side.
Request Queue	Specifies the queue name for an ESB channel (one) communication for the target operation request. The default value is asg.out.request
Reply Queue	Specifies the queue name for ESB channel (one) communication for the response from the target operation. The default value is asg.out.request.reply.0.0
JMS Target ESB Connection Tertiary
JMS Provider URL	Specifies the connection URL for the EMS Server used for facade operation requests from the ESB communication domain. The ESB communication uses JMS transport with XML. The default value is tcp://localhost:7222
JNDI Context URL	Specifies the URL to the JNDI service provider used for facade client requests with the ESB communication domain. The default value is tibjmsnaming://localhost:7222
Topic Connection Factory Name	Specifies the name of TopicConnectionFactory object stored in JNDI. This object is used to create a topic connection with ESB services at the facade side. The default value is TopicConnectionFactory
Queue Connection Factory Name	Specifies the name of QueueConnectionFactory object stored in JNDI. This object is used to create a queue connection with ESB services at the facade side. The default value is QueueConnectionFactory
JNDI Username	Specifies the user name for logging into the JNDI server in the ESB communication domain at the facade side. If the JNDI provider does not require access control, this field can be empty. The default value is admin
JNDI Password	Specifies the password for logging into the JNDI server in the ESB communication domain at the facade side. If the JNDI provider does not require access control, this field can be empty.
JMS Username	Specifies the user name for logging into the EMS server in the ESB communication domain at the facade side. The default value is admin
JMS Password	Specifies the password for logging into the EMS server in the ESB communication domain at the facade side.
Request Queue	Specifies the queue name for an ESB channel (one) communication for the target operation request. The default value is asg.out.request
Reply Queue	Specifies the queue name for ESB channel (one) communication for the response from the target operation. The default value is asg.out.request.reply.0.0
JMS SOAP Connection North
JMS Provider URL	Specifies the connection URL for the EMS Server used for facade operation requests from the ESB communication domain. The ESB communication uses JMS transport with XML. The default value is tcp://localhost:7222
JNDI Context URL	Specifies the URL to the JNDI service provider used for facade client requests with the ESB communication domain. The default value is tibjmsnaming://localhost:7222
Topic Connection Factory Name	Specifies the name of TopicConnectionFactory object stored in JNDI. This object is used to create a topic connection with ESB services at the facade side. The default value is TopicConnectionFactory
Queue Connection Factory Name	Specifies the name of QueueConnectionFactory object stored in JNDI. This object is used to create a queue connection with ESB services at the facade side. The default value is QueueConnectionFactory
JNDI Username	Specifies the user name for logging into the JNDI server in the ESB communication domain at the facade side. If the JNDI provider does not require access control, this field can be empty. The default value is admin
JNDI Password	Specifies the password for logging into the JNDI server in the ESB communication domain at the facade side. If the JNDI provider does not require access control, this field can be empty.
JMS Username	Specifies the user name for logging into the EMS server in the ESB communication domain at the facade side. The default value is admin
JMS Password	Specifies the password for logging into the EMS server in the ESB communication domain at the facade side.
Request Queue	Specifies the queue name for an ESB channel (one) communication for the target operation request. The default value is asg.out.request
Reply Queue	Specifies the queue name for the ESB channel (one) communication for the response from the target operation. The default value is asg.out.request.reply.0.0
JMS SOAP Connection South
JMS Provider URL	Specifies the connection URL for the EMS Server used for facade operation requests from the ESB communication domain. The ESB communication uses JMS transport with XML. The default value is tcp://localhost:7222
JNDI Context URL	Specifies the URL to the JNDI service provider used for facade client requests with the ESB communication domain. The default value is tibjmsnaming://localhost:7222
Topic Connection Factory Name	Specifies the name of TopicConnectionFactory object stored in JNDI. This object is used to create a topic connection with ESB services at the facade side. The default value is TopicConnectionFactory
Queue Connection Factory Name	Specifies the name of QueueConnectionFactory object stored in JNDI. This object is used to create a queue connection with ESB services at the facade side. The default value is QueueConnectionFactory
JNDI Username	Specifies the user name for logging into the JNDI server in the ESB communication domain at the facade side. If the JNDI provider does not require access control, this field can be empty. The default value is admin
JNDI Password	Specifies the password for logging into the JNDI server in the ESB communication domain at the facade side. If the JNDI provider does not require access control, this field can be empty.
JMS Username	Specifies the user name for logging into the EMS server in the ESB communication domain at the facade side. The default value is admin
JMS Password	Specifies the password for logging into the EMS server in the ESB communication domain at the facade side.
Request Queue	Specifies the queue name for an ESB channel (one) communication for the target operation request. The default value is asg.out.request
Reply Queue	Specifies the queue name for an ESB channel (one) communication for the response from the target response. The default value is asg.out.request.reply.0.0
Show SSLProperties Use the Show SSL Properties button to configure the SSL connection parameters for JMS transport at the facade and target side.
Use SSL	A boolean field to indicate if SSL is enabled for accepting requests using the JMS transport. Set this to true to enable SSL for the JMS transport.
Trusted Certificate Folder	Specifies a location of the trusted certificates on this machine. The trusted certificates are a collection of certificates from servers with which you establish connections. If the server with which the connection is going to be established, presents a certificate that does not match one of your trusted certificates, the connection is refused. This prevents connections to unauthorized servers. Import the trusted certificates into a folder before you select the folder in this field.
Identity Resource	Specifies an identity resource used to provide the SSL properties for JMS transport. For example, /DefaultImplementation/SharedResources/JMS/Target_ESB0ConnIdentityResource.id
TrustStorePassword	Specifies the password to access the certificate stored in the folder defined by the Trusted Certificate Folder field.
Trace	Specifies whether SSL tracing should be enabled during the connection. If checked, the SSL connection messages are logged and sent to the console.
Debug Trace	Specifies whether SSL debug tracing should be enabled during the connection. Debug tracing provides more detailed messages than standard tracing.
Verify Host Name	Specifies whether the host you are connecting to is the expected host. The host name in the host’s digital certificate is compared against the value in the Expected Host Name field. If the host name does not match the expected host name, the connection is refused. Note: The default context factories for TIBCO Enterprise Message Service automatically determine if host name verification is necessary. If you are using a custom implementation of the context factories, your custom implementation must explicitly set the verify host property to the correct value. For example:   com.tibco.tibjms.TibjmsSSL.setVerifyHost(false)
Expected Host Name	Specifies the name of the host you are expecting to connect to. This field is only relevant if the Verify Host Name field is also checked. If the name of the host in the host’s digital certificate does not match the value specified in this field, the connection is refused. This prevents hosts from attempting to impersonate the host you are connecting to.
Strong Cipher Suites Only	When checked, this field specifies that the minimum strength of the cipher suites used can be specified with the bw.plugin.security.strongcipher.minstrength custom engine property. See TIBCO ActiveMatrix BusinessWorks Administration for more information about this property. The default value of the property disables cipher suites with an effective key length below 128 bits. When this field is unchecked, only cipher suites with an effective key length of up to 128 bits can be used.
Identity Type	Speicifies the type of identity resource. The possible values are: − certPlusKeyURL − url − usernamePassword
Certificate/Private Key Identity Use this option if the private key and the certificate are in two separate files.
Certificate URL	Specifies the URL to the certificate file if the Identity Type is of the certPlusKeyURL type.
Key URL	Specifies the URL to the private key in the certificate file if the Identity Type is of the certPlusKeyURL type.
Key Password	Specifies the password for the private key used for SSL connection if the Identity Type is of the certPlusKeyURL type.
Username/Password Use this option if you want to use a username and password for authentication instead of a certificate.
Identity User Name	Name of the user for this identity.
Identity Password	Password for the user for this identity.
url Use this option if the certificate includes the private key information in the same file.
Identity URL	Specifies the location of the certificate (which includes the private key) if Identity Type is of url type. For example, C:\asgserver.pfx
Identity File Type	Specifies the type of certificate file if Identity Type is of url type. Choose the certificate file type from the drop-down list: − Entrust − JCEKS − JKS − PEM − PKCS12
Key Password	Password for the certificate if Identity Type is of url type.

Database Properties

To set the Database properties, follow these steps:

1.	Select the Gateway Engine Properties from the drop-down list.

2.	Click the Database link.

Table 62 Database Properties

Property	Description
Connection Check Interval	Specifies the time interval (in seconds) for the Central Logger to connect to the database server.
Connection Retry Count	Specifies the number of attempts to be made for the Central Logger to connect to the database server if the database server goes down.
DB Driver	Specifies the database driver for the database server used by the Central Logger.
DB URL	Specifies the database server connection URL for the Central Logger. For example, for the MS SQL server, the following value is used: jdbc:sqlserver://10.107.174.56:1433;databaseName=asgstat
DB Username	Specifies the username for the Central Logger to connect to the database server. The default value is asguser
DB Password	Specifies the password for the Central Logger to connect to the database server. The default value is asguser
DB Schema

Security Properties

To set the Security properties, follow these steps:

1.	Select the Gateway Engine Properties from the drop-down list.

2.	Click the Security link:

Table 63 Security Properties

Property	Description
Common
Anonymous Partner Name	Specifies a default partner name for the unauthenticated requests.
OAuth
Transport Scheme	• Specifies the transport type used to connect to for TIBCO API Exchange Gateway OAuth server. The possible values are: − HTTP − HTTPS • See OAuth HTTP Transport to set the OAuth HTTP transport settings. • See OAuth WebApps SSL to set the OAuth HTTPS (SSL) transport settings.
OAuth HTTP Transport
Port	Specifies the non-SSL port number of the TIBCO API Exchange Gateway OAuth Server. The default value is 9322.
OAuth WebApps SSL Properties are shown if the transport scheme is selected as HTTPS.
Host	Specifies the IP address of the TIBCO API Exchange Gateway OAuth Server.
Port	Specifies the SSL port number of the TIBCO API Exchange Gateway OAuth Server. The default value 9333.
Use SSL	This is a boolean field which indicates if SSL should be enabled for accepting HTTPS requests for OAuth APIs and servlets. If set to true, SSL is enabled to accept the requests using HTTPS transport for the OAuth server. The default value is true.
Identity Resource	Specifies an identity resource used by OAuthWebappsSSLConnection HTTP shared resource to provide SSL properties for the OAuth servlets and APIs. The default value is /DefaultImplementation/SharedResources/HTTP/OAuthIdentityResource.id
Identity File Type	Specifies the type of identity resource used by OAuthWebappsSSLConnection HTTP shared resource. The possible values are as follows: − Identity File − Certificate/Private Key • If Identity File Type is of the Identity File type, enter the Identity Type, Identity URL, and Identity File Password parameters. • If Identity File Type is of the Certificate/Private Key type, enter Certificate URL, Key URL, and Key Password parameters.
Identity Type	Specifies the type of the keystore if the Identity File Type is of the Identity File type.The supported values are as follows: − JCEKS − JKS − PEM − PKCS12
Identity URL	Specifies the URL to the identity file used for the OAuth server SSL connection if the Identity File Type is of the Identity File type. For example, C:\keystore.jks
Identity File Password	Specifies the password for the identity file used for the OAuth server SSL connection if the Identity File Type is of the Identity File type.
Certificate URL	Specifies the URL to the certificate file used for the OAuth server SSL connection if Identity File Type is of the Certificate/Private Key type.
Key URL	Specifies the URL to the private key in certificate file used for the OAuth server SSL connection if Identity File Type is of the Certificate/Private Key type.
Key Password	Specifies the password for the private key used for the OAuth server SSL connectionif Identity File Type is of the Certificate/Private Key type.
Requires Client Authentication	Indicates a boolean flag to enable or disable mutual SSL authentication for HTTPs transport used for OAuth server requests from the requestor. When this field is set to true, the Trusted Certificates Folder becomes enabled so that you can specify a location containing the list of trusted certificate authorities.
Truststore Password	Specifies the password to access the certificate stored in the folder defined by the Trusted Certificate Folder field.
Trusted Certificate Folder	Specifies a folder containing one or more certificates from trusted certificate authorities, which is required for mutual SSL authentication. Required when the RequiresClientAuthentication property is set to true.
Portal Engine Integration Properties
Engine URL	Specifies the URL of the portal engine if used as a client. For example, the engine URL can be specified as follows: http://portal_host_name:9122 where portal_host_name is the host machine running the portal engine.
General
WebApps Path	• Specifies the location of the OAuth web application. • Change web.xml file if you want to add custom login page or access grant page to the OAuth server. • Do not remove the content of this war file.
OAuth Data Space
Access Token Retention Period
	Specifies the expiration time (in minutes) for an access token. The default value is 60 minutes. When the access token passes expiration time as specified by this property, it is no longer valid but still remains in the database.
MetaSpace Name
	• Specifies the metaspace name used by the OAuth server. • The default value is ASG-OAuth-Tokens
Local Discovery URL
	Specifies the discovery URL for this OAuth instance of the metaspace discovers the current metaspace members. For example, tcp://machine1_IP_Address:6300;machine2_IP_Address:6300
Local Listen URL
	Specifies the listening URL for this OAuth instance of the metaspace. For example, tcp://machine1_IP_Address:6300
Batch Size
	Specifies the maximum number of entries to return when querying the data such as access token details.
Properties For OAuth Persister
Persister Store
	• Defines the type of persistence store. The possible values are: − InMemory − Database • You can select the type of persistence store from a drop-down list. When the Database is selected, you must define the properties for database server connection. See Database Connection Properties for OAuth Persister as Database.
Database Connection Properties for OAuth Persister as Database Set the properties if the OAuth Persister is selected as Database type.
Driver
	Specifies the database JDBC driver when Database is used as OAuth persistence store.
JDBC URL
	Specifies the JDBC url for the database server when Database is used as the OAuth persistence store.
JDBC User Name
	Specifies the user name to connect to the database server when Database is used as the OAuth persistence store.
JDBC Password
	Specifies the password of the user to connect to the database server when Database is used as the OAuth persistence store.
Properties For OAuth Adapters
Resource Path Name
	Specifies the directory from where the custom adapters loads the resources such as properties file used by adapters. This directory location is relative to the ASG_HOME. For example, if the value is specified as /examples/OAuth/resources, the custom adapter looks for the resources such as properties file in the ASG_HOME/examples/OAuth/resources directory.
Owner Adapter
	• Specifies the class that provides the owner adapter interface. This adapter is used to authenticate the resource owner and provide the login and access grant pages. See the Owner Service Provider Interface for details. For example, for the file based owner adapter interface, the value is specified as: com.tibco.asg.oauth.identity.provider.file.OwnerAdapterService • The jar file that contains this adapter implementation must be placed in a directory in the classpath set in the ASG_HOME/bin/asg-engine.tra file. See How to Deploy Custom Adapters for details.
Client Adapter
	• Specifies the class that provides the client adapter interface. This adapter is used to authenticate the client and to retrieve the client attributes. See Client Service Provider Interface for details. For example, for the file based client adapter interface, the value is specified as: com.tibco.asg.oauth.identity.provider.file.ClientAdapterService • The jar file that contains this adapter implementation must be placed in a directory in the classpath set in the ASG_HOME/bin/asg-engine.tra file. See How to Deploy Custom Adapters for details.
Scope Adapter
	• Specifies the class that provides the Scope Adapter interface. This adapter is used to retrieve the scope description and the scope from a specific resource for a given owner. See Scope Service Provider Interface for details. For example, for the file based scope adapter interface, value is specified as: com.tibco.asg.oauth.identity.provider.file.ScopeAdapterService • The jar file that contains this adapter implementation must be placed in a directory in the classpath set in the ASG_HOME/bin/asg-engine.tra file. See How to Deploy Custom Adapters for details.
Portal Engine Integration Properties
Engine URL
	Specifies the URL of the portal engine. For example, the engine URL can be specified as: http://portal_host_name:9122

 

Copyright © Cloud Software Group, Inc. All Rights Reserved