Alpaca 4.0

Configuration

The Alpaca configuration is an XML document that is divided into a number of major categories.

  • <systemproperty>: This gets the value of a JVM system property.
  • <core>: This is configuration for the BroadWorks server, requests, and responses. These settings will apply universally.
  • <helper>: Configuration for code written in the helper package. There are a number of tools that place their configuration within this tag.
  • <shell>: Configuration of the Alpaca CLI.

Core

BroadWorks

  • connectionTimeoutMillis: How long to wait before failing out during connection tests to the BroadWorks system.
<broadworks>
    <connectionTimeoutMillis>5000</connectionTimeoutMillis>
</broadworks>

Request

  • encoding: The encoding to use for the outgoing and incoming parsing of BroadWorks messages.
  • timeoutMillis: How long to wait before failing out during request-response transactions.
  • maxPerSecond: The maximum number of requests to send per second through a single BroadWorksServer object. This is a blocking operation that will limit the overall speed of the code if attempting to perform too many operations per second.
  • validateOnFire: Sets if JSR 303 Bean Validation will be used to verify that a request is valid per the XML spec before sending it to BroadWorks. An exception will be thrown from the .fire() call alerting to the invalid request.
  • bundlerAutoFireTimeoutMillis: When using a RequestBundler this timeout controls how long to wait before firing a request with less than 15 entries.
<request>
    <encoding>UTF-8</encoding>
    <timeoutMillis>10000</timeoutMillis>
    <maxPerSecond>40</maxPerSecond>
    <validateOnFire>false</validateOnFire>
    <bundlerAutoFireTimeoutMillis>1000</bundlerAutoFireTimeoutMillis>
</request>

Service

  • asyncLoadTimeout: How long to block if a request for user service information is created while waiting for asynchronous load. 
<service>
    <asyncLoadTimeout>120000</asyncLoadTimeout>
</service>

Clusters - Cluster

  • nickName: The nickname for the Broadworks server.
OCI
  • hostName: The address to connect to the BroadWorks server.
  • userName: The connection userName. This can be a user, provisioning admin, or system admin. However, most commands will require admin level access.
  • password: The connection password for the provided userName.
TimesTen
  • hostName: The address for the application server where the TimesTen installation is contained.
  • DSN: Name of the DSN to connect to.
  • port: Specify the port number to use for the connection.
  • userId: userID to connect to the TimesTen database.
  • password: The password for the provied userId.
<clusters>
    <cluster nickName="Production">
        <oci hostName="hostname" userName="userName" password="password" />
        <timesten hostName="hostname" DSN="AppServer" port="11203"
            userId="userId" password="password" />
    </cluster>
    <cluster nickName="Lab">
        <oci hostName="hostname" userName="username" password="password" />
        <timesten hostName="hostname" DSN="AppServer" port="11203"
            userId="userId" password="password" />
    </cluster>
</clusters>

Helper

  • timesTenEnabled: Toggle whether or not TimesTen is enabled.
<timesTenEnabled>false</timesTenEnabled>

User

  • asyncBundleTimeoutMillis: This is a distinct timeout for asynchronous bundles used by the User helper. In most cases this should match the load timeout for other service calls.
  • usernameLength: The length of username to generate when randomizing the authentication username field.
  • announcement/repositoryUsername: The username to retrieve voice portal audio and video files from for migration procedures.
  • announcement/repositoryPassword: The password to retrieve voice portal audio and video files from for migration procedures.
<user>
    <asyncBundleTimeoutMillis>120000</asyncBundleTimeoutMillis>
    <usernameLength>10</usernameLength>
    <announcement>
        <repositoryUsername>BoNjOuRlEsAmIs049</repositoryUsername>
        <repositoryPassword>viveLEROILouis14</repositoryPassword>
    </announcement>
</user>

Access Device

  • authenticationPasswordChangeable: When randomizing a user's authentication password, the user's access device type must match the provided regular expression.
  • authenticationUsernameChangeable: When randomizing a user's authentication username, the user's access device type must match the provided regular expression.
  • migration/rebootDelayMillis: The delay in milliseconds between rebooting the device and performing the migration procedure.
  • migration/fileRules: Migration file rules consist of device types matched to the files that should be migrated with the device. There can be any number of file rules that specify the desired files to be migrated.
  • migration/fileRule/deviceType: This is the file rule device type specified by regular expression.
  • migration/fileRule/file: Any number of files can be specified by exact name.
  • resetwatcher/deviceTypeFilter: When resetting devices with the ResetWatcher device types must match the provided regular expression.
  • resetwatcher/timeoutMillis: The total time to wait for a device to re-register after being sent a reset command.
  • resetwatcher/delayMillis: The time to wait between polling the registration information to detect the re-register.
<accessdevice>
    <authenticationPasswordChangeable>.*(Polycom|Linksys|Cisco).*</authenticationPasswordChangeable>
    <authenticationUsernameChangeable>.*(Polycom|Linksys|Cisco).*</authenticationUsernameChangeable>
    <migration>
        <rebootDelayMillis>5000</rebootDelayMillis>
        <filerules>
            <filerule>
                <deviceType>Polycom.*</deviceType>
                <file>%BWMACADDRESS%-directory.xml</file>
                <file>%BWMACADDRESS%-calls.xml</file>
            </filerule>
        </filerules>
    </migration>
    <resetwatcher>
        <deviceTypeFilter>.*Polycom.*</deviceTypeFilter>
        <timeoutMillis>300000</timeoutMillis>
        <delayMillis>10000</delayMillis>
    </resetwatcher>
</accessdevice>

Cache

  • blfGroupTimeoutInHours: How long a Busy Lamp Field is considered valid in the cache.
<cache>
    <blfGroupTimeoutInHours>24</blfGroupTimeoutInHours>
</cache>

Report - Email

  • useAuthentication: Whether to use SMTP authentication when sending emails.
  • smtpHostName: The mail server hostname.
  • smtpUserName: The mail server username.
  • smtpPassword: The mail server password.
  • smtpPort: The mail server port.
  • useTLS: Whether the mail server uses TLS.
  • fromAddress: The FROM portion of emails sent from Alpaca.
  • toAddresses: The TO portion of emails is able to be determined by address entries. All valid address entries will be included.
  • toAddresses/address: Addresses have a priority and type. Emails will be sent to all addresses at the lowest priority. A priority of * will always be sent. The address type can be either UserProfile, VoicemailCarbonCopy or Static. UserProfile will look for an email address in the user profile for the modified user. VoicemailCarbonCopy will look in the voice messaging carbon copy field for the modified user. Static is an email address designated in the config.
  • subjectPrepend: A text prepend in the subject of outbound emails.
  • usePlainText: Whether to send the email as plain text.
  • template: These are CDATA templates for outbound emails. Templates can contain the following tags:
    • %ALPACAPRIORITY%: The priority of the event.
    • %ALPACAEVENTMESSAGE%: The message for the event.
    • %ALPACAEVENTSUBJECT%: The subject for the event.
    • %ALPACAVERSION%: The version of Alpaca.
    • %BWNAME%: The first and last name of the user.
    • %BWFIRSTNAME%: The first name of the user.
    • %BWLASTNAME%: The last name of the user.
    • %BWDN%: The phone number of the user.
    • %BWID%: The ID of the user.
    • %BWEXTENSION%: The extension of the user.
<report>
    <email>
        <useAuthentication>true</useAuthentication>
        <smtpHostName>smtp.gmail.com</smtpHostName>
        <smtpUserName></smtpUserName>
        <smtpPassword></smtpPassword>
        <smtpPort>587</smtpPort>
        <useTLS>true</useTLS>
        <fromAddress></fromAddress>
        <toAddresses>
            <address priority="1" type="UserProfile"/>
            <address priority="2" type="VoicemailCarbonCopy"/>
            <address priority="*" type="Static">admin@mycompany.com</address>
        </toAddresses>
        <subjectPrepend>[AlpacaEvent]</subjectPrepend>
        <usePlainText>false</usePlainText>
        <template>
            <userEvent>
                <![CDATA[
                <html>
                <body>
                %ALPACAEVENTMESSAGE%<br>                
                ---<br>
                Alpaca Version: %ALPACAVERSION%<br>
                </body>
                </html>
                ]]>
            </userEvent>
        </template>
    </email>
</report>

Shell

Core

  • bellEnabled: Sets the terminal bell active.
  • keepAlive: Enabled a periodic background request that maintains a connection to the BroadWorksServer.
<core>
    <bellEnabled>true</bellEnabled>
    <keepAlive>true</keepAlive>
</core>

Daemon

  • port: The port designated for the Alpaca daemon.
<daemon>
    <port>4550</port>
</daemon>

Commands

User

ModifyPasscode
  • emailUpdateByDefault: Sets the default behavior for the modify passcode command regarding sending an update email.
  • emailTemplate: The template to use for the email update. This template supports the same tags seen in the Report - Email category.
<modifyPasscode>
    <emailUpdateByDefault>true</emailUpdateByDefault>
    <emailTemplate>
        <![CDATA[
        <html>
        <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap.min.css">
        <body>
        <div class="container-fluid">
        This is an automated event notification for <strong>User Voice Portal</strong> passcode modification.<br>
        <br>
        <dl class="dl-horizontal">
        <dt>Priority</dt>
        <dd>%ALPACAPRIORITY%</dd>
        <dt>User ID</dt>
        <dd>%BWID%</dd>
        <dt>Name</dt>
        <dd>%BWFIRSTNAME% %BWLASTNAME%</dd>
        <dt>DN</dt>
        <dd>%BWDN%</dd>
        <dt>New Passcode</dt>
        <dd>%ALPACAEVENTMESSAGE%</dd>
        </dl>
        <br>
        <img src = "http://www.e-c-group.com/wp-content/themes/dawn/images/logo.png"><br>
        <h5>Alpaca <small>Version %ALPACAVERSION%</small></h5>
        </div>
        </body>
        </html>
        ]]>         
    </emailTemplate>
</modifyPasscode>
ModifyPassword
  • emailUpdateByDefault: Sets the default behavior for the modify password command regarding sending an update email.
  • emailTemplate: The template to use for the email update. This template supports the same tags seen in the Report - Email category.
<modifyPassword>
    <emailUpdateByDefault>true</emailUpdateByDefault>
    <emailTemplate>
        <![CDATA[
        <html>
        <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap.min.css">
        <body>
        <div class="container-fluid">
        This is an automated event notification for <strong>User Web Access</strong> password modification.<br>
        <br>
        <dl class="dl-horizontal">
        <dt>Priority</dt>
        <dd>%ALPACAPRIORITY%</dd>
        <dt>User ID</dt>
        <dd>%BWID%</dd>
        <dt>Name</dt>
        <dd>%BWFIRSTNAME% %BWLASTNAME%</dd>
        <dt>DN</dt>
        <dd>%BWDN%</dd>
        <dt>New Password</dt>
        <dd>%ALPACAEVENTMESSAGE%</dd>
        </dl>
        <br>
        <img src = "http://www.e-c-group.com/wp-content/themes/dawn/images/logo.png"><br>
        <h5>Alpaca <small>Version %ALPACAVERSION%</small></h5>
        </div>
        </body>
        </html>
        ]]>         
    </emailTemplate>
</modifyPassword>