User guide

User Script Parameters
Deploying and configuring JBoss Enterprise Application Platform using the User Data field provides for
flexibility and ease of management of multiple configurations. T he flexibility comes from the use of
various parameters which can be used to configure the platform or in the deployment of your custom
application.
A.1. Permanent Configuration Parameters
The following parameters can be used to influence the configuration and operation of JBoss Enterprise
Application Platform. Their contents are written to /etc/sysconfig/jbossas and /etc/sysconfig/jon-agent-
ec2.
Name Description Default
JBOSS_JGROUPS_S3_PING_A
CCESS_KEY
Amazon AWS user account
access key for S3_PING
discovery if clustering is used.
N/A
JBOSS_JGROUPS_S3_PING_S
ECRET_ACCESS_KEY
Amazon AWS user account
secret access key.
N/A
JBOSS_JGROUPS_S3_PING_B
UCKET
Amazon S3 bucket to be used
for S3_PING discovery.
N/A
JBOSS_CLUSTER_ID ID of cluster member nodes.
Only used for clustering.
Accepted values are (in order):
a valid cluster ID number in
the range 0-1023
a network interface name
who's IP last octet is used
as the value
"S3" as a value would
coordinate ID usage through
the S3 bucket used for
jgroups' S3_PING It's
recommended to use the last
octet of IP (i.e. the default)
when all cluster nodes are
located in the same 24 or
more bits subnet (for
example in a VPC subnet).
Last octet of eth0's IP address.
MOD_CLUSTER_PROXY_LIST Comma-delimited list of
IPs/hostnames of mod_cluster
proxies if mod_cluster is to be
used.
N/A
PORTS_ALLOWED List of incoming ports to be
allowed by firewall in addition to
the default ones.
N/A
JBOSSAS_ADMIN_PASSWORD JBoss EAP password for
"admin" user.
N/A
JON_SERVER_ADDR JON server hostname or IP with
which to register. T his is only
N/A
JBoss Enterprise Application Platform 5 Getting Started on Amazon EC2
28