Installation for CentOS & RedHat


  • Java JDK 1.8
    • The newest release can be found on Oracle's webpage.
  • Oracle TimesTen
    • See below for specific instructions.
  • The IP address of the Alpaca system must be in an access control list on the BroadWorks profile server.
    • Login to the Profile Server.
    • In the BWCLI navigate to /Applications/BroadworksFileRepos/NetworkAccessLists/WebDav
      • q all ; Applications;BroadworksFileRepos;NetworkAccessLists;WebDav
    • Add the IP address from which the Alpaca migration tools will be connecting.
      • add {IP} description {description}
      • E.g., if there's no NAT and you're running Alpaca on, you could do:
        add "Alpaca workstation"

TimesTen Installation

  • Download the TimesTen installation archive from here.
  • Extract the archive.
  • Run the script in the extracted directory.
  • Follow the setup instructions. TimesTen can be installed in client only mode. Most other items can be default.
  • The TimesTen lib directory must be set in the ALPACA_TT_LIB environment variable for Alpaca to retrieve.
    • echo "export ALPACA_TT_LIB=/opt/TimesTen/tt1122/lib" >> /etc/bashrc
    • To add the path to the current shell run source /etc/bashrc
  • Add TimesTen lib directory to the linux library linking path.
    • echo "/opt/TimesTen/tt1122/lib" > /etc/
    • Verify that the TimesTen library is loaded by ldconfig -v | grep TimesTen -A 20. The output should display the library links being created.

Alpaca Setup

  • Download the Alpaca tarball (.tar.gz), e.g., to /tmp/alpaca-core-21sp1-5.1.5-RELEASE-bin.tar.gz
  • Extract the archive in /opt.
    • cd /opt
    • tar xzvf /tmp/alpaca-core-21sp1-5.1.5-RELEASE-bin.tar.gz
  • Create a symlink from the new alpaca directory.
    • ln -s alpaca-core-5.1.5 /opt/alpaca
  • Create alpaca user with home directory of /opt/alpaca.
    • useradd -m -d /opt/alpaca alpaca
  • Change the ownership of the /opt/alpaca directory and all of its children
    • chown -R alpaca:alpaca /opt/alpaca/
  • Change the permissions to allow the alpaca group to modify all files
    • chmod -R g+rw /opt/alpaca/
  • Move your license file (named by default ecg.license.txt) into the conf directory of the extracted archive.
    • For example, if the file is in /tmp, you would do mv /tmp/ecg.license.txt /opt/alpaca/conf
  • Edit the conf/ file to configure the BroadWorks cluster element for the desired BroadWorks install. See the configuration guide for additional information.
  • Verify installation by running ./check. See Check Tool
  • Run via ./alpaca

Setup an Alpaca Users "alice" and "bob"

  • Add the user to the Alpaca group. This allows them to run alpaca within the alpaca group.
    • usermod -G alpaca,alice alice
    • usermod -G alpaca,bob bob


Configuration Check Tool

A tool to check and verify the configurations of Alpaca.

  • Run after configuring Alpaca.
  • Run via ./check
  • Checks:
    • License file
    • Times Ten Configuration
    • Times Ten connection to Application Server
    • Connection to Broadworks
    • Profile Server Access

Upgrade Tool

A tool to copy Alpaca configurations from one Alpaca installation to another.

  • Copies properties file, license file, log4j configuration file, and cache configuration file.
  • Run via ./upgrade -i <Previous Alpaca Configuration Path>
  • Compatible with Alpaca version 4.1.0 and above.