as-agent Help Options detail.
Article ID: KB0089179
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveSpaces | - |
| Not Applicable | - |
Description
Resolution:
as-agent -help usage :
| -metaspace <metaspace_name> default ms | 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. |
| -discovery <url> / <url_list> default tibpgm | Refer Page 27 from AD admin guide. |
| -listen <url> default tcp | Refer Page 28 from AD admin guide. |
| -remote_listen <url> | remote_listen command to contact the remote client and accept incoming remote client connections. Remote listen url format: tcp://interface/remote_listen_port |
| -log log file path | If you include the parameter -log <log_file>, then the log filename will be log_file-<processid>.log. For example, if you enter -log as, then the log filename is as-<processid>.log. |
| -log_debug default 3 (INFO) | To specify a log level, specify: -debug <log_level> The log levels are as follows: 1 = ERROR_LEVEL 2 = WARNING_LEVEL 3 = INFO_LEVEL The default is 3 (INFO). The log information displayed on the console is minimal and cannot be controlled through this parameter. This parameter is only for log files. If a log file is not specified, then the debug (log level) value is ignored. |
| -log_limit default -1 (no limit) | File size in bytes before rollover |
| -log_count default 1 | Max number of rolling files |
| -log_append default true | Append logs or not |
| -debug <log_level> default 3 (INFO) | Log level to be used |
| -advisory_level <advisory_level> default 3 (INFO) | advisory is not enabled yet, but once it is enabled, this will be what user wants to see in advisory logs (we have console logging, file logging and finally advisory logging) |
| -name <membername> | deprecated |
| -member_name <membername> | Specifies a member name for the member. This helps to identify which member name is associated with which member ID. The show members command displays the member name if one has been assigned; otherwise, a default member name is assigned that is constructed from the member ID. |
| -data_store <directory path> | specifies the directory path where shared-nothing persistence files are stored. where directory_path specifies the directory path for the shared nothing persistence data store. |
| -worker_thread_count <count> | the number of threads that can be used for invocation. Default is 32, meaning you can have 32 invocations in parallel |
| -rx_buffer_size <size> | default tcp buffer size to receive data. Default is 2MB. If user is using large tuples, this value can be increased accordingly. If the value is smaller than what we need to receive on wire, dynamic buffer is allocated during the lifetime of the message. Once that's processes, dynamic buffer is destroyed. It is better to use a large valud to avoid context switch from dynamic to static buffer |
| -security_policy <string> | If TIBCO ActiveSpaces security is implemented and you are connecting from a domain security controller node, specify the security_policy parameter and provide the directory path and filename for the policy file. If you specify a policy file, do not specify the security_token parameter. |
| -security_token <string> | Specifies the token file for a security domain requestor that must be authenticated by a security domain controller.If TIBCO ActiveSpaces security is implemented and you are connecting from a requestor node, and the metaspace to which you are connecting requires a token file, specify the security_token parameter and provide the directory path and filename for the token file. If you specify a token file, do not specify the security_policy parameter. |
| -authentication_domain <string> | The name of the windows domain to log into. If local/ntlm account (as per the controller), "." can be used. If not windows, it will be ignored |
| -authentication_username <string> | The authentication username of the user account to be logged in as |
| -authentication_keyfile <string> | pkcs12 keyfile location of the user to be logged in as (sasl/external x509 ldap auth) |
| -authentication_password <string> | The authentication password of the user account to be logged in as or the password of the pkcs12 key file if x509 auth is used. |
| -identity_password <string> | The policy's security domain's or the token's identity password if the identity is encrypted |
| -monitor_system true|false default false | Enable the system monitor on the given member to start and advertise its performace statistics in its joined metaspace(s) scope To start performance monitoring with as-agent or as-admin, start the utility with the -monitor_system parameter set to true, for example: as-agent -monitor_system true |
| -input <filepath> | you can pass as-agent parameters through script file as input to as-agent |
| -admin | as-agent can disconnect gracefully without losing data. You will need to pass the “–admin” parameter while running as-agent from the command prompt utility. |
Issue/Introduction
as-agent Help Options detail.
Additional Information
ActiveSpaces as-agent -help
Feedback
Yes
No
Powered by
