Administer > Monitoring SA Core components > Data Access Engine monitoring

Data Access Engine monitoring

The Data Access Engine simplifies interaction with various clients in SA, such as the Command Center, system data collection, and monitoring agents on servers.

Data Access Engine port

The Data Access Engine uses port 1004 (HTTPS) externally and 1007 (the loopback interface) for SA components installed on the same server.

Multimaster Central Data Access Engine Port forwarding

SQLnet traffic between the Multimaster Central Data Access Engine in a mesh and the Model Repositories in other SA Cores in the mesh is routed over the SA Gateway mesh.

The tnsnames.ora file on the server running the Multimaster Central Data Access Engine points to a specified port on each core-side Gateway in the other SA cores. The core-side Gateway in the core running the Multimaster Central Data Access Engine forwards the connection to the core-side Gateway in each other core, which in turn forwards it to the Model Repositories in the other cores.

The port number on the core-side Gateway is calculated as 20000 + data_center_id. For example, if the Multimaster Mesh has two facilities, Facility A (facility ID 1) and Facility B (facility ID 2), the Multimaster Central Data Access Engine in Facility A connects to port 20002 on the server running the Gateway to reach the Model Repository in Facility B.

For information about the Multimaster Central Data Access Engine, see Multiple data access engines.

For information about the Gateway mesh topology, see the SA 10.51 Key Concepts Guide.

Monitoring processes for the Data Access Engine

On Linux, execute the command on the server running the Data Access Engine component:

# ps auxwww | grep -v grep | grep spin | grep -v java

Running this command should produce output similar to the following output:

root  30202  0.0  0.0  13592  1500  ?  S  Sep11 0:01  /opt/opsware/bin/

python /opt/opsware/pylibs/shadowbot/daemonbot.pyc --conf /etc/opt/opsware/spin/spin.args

root  30204  1.3  0.6  154928  25316  ?  S  Sep11  411:15  /opt/opsware/

bin/python /opt/opsware/pylibs/shadowbot/daemonbot.pyc
--conf /etc/opt/opsware/spin/spin.args

root  30256  0.1  0.3  28500  13024  ?  S  Sep11  50:35  /opt/opsware/

bin/python /opt/opsware/spin/certgenmain.pyc --start
--conf /etc/opt/opsware/spin/spin.args

Monitoring processes for the Web Services Data Access Engine

On Linux, execute the command on the server running the Command Center component and on the server running the Slice Component bundle:

# ps auxwww | grep -v grep | grep \/opt\/opsware\/twist

Running this command should produce output similar to the following output:

twist  4039  0.2  11.3  2058528  458816  ?  S  Sep11  80:51 /opt/opsware/
j2sdk1.4.2_10/bin/java -server -Xms256m -Xmx1280m -XX:MaxPermSize=192m -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger ......
twist  4704  0.0  0.0  4236  1124  ?  S  Sep11  1:28  /bin/sh /opt/
opsware/twist/watchdog.sh start 60'
twist  4743  0.0  0.6  376224  27160  ?  S  Sep11  18:31 /opt/opsware/
j2sdk1.4.2_10/bin/java -server -Xms16m -Xmx128m -Dtwist.port=1026 ...... -classpath /opt/opsware/j2sdk1.4.2_10/jre/......

Data Access Engine URLs

  • https://spin.<data_center>:1004

    To access the Data Access Engine (spin) UI, you need the browser certificate browser.p12.

    browser.p12 is located in:

    /var/opt/opsware/crypto/spin/

    on any Slice Component bundle host. Copy the file to your local machine and import browser.p12 into your browser, following your browser import certificate instructions.

  • https://spin.<data_center>:1004/ObjectBrowser.py?cls=Account&id=0

    Accessing the second URL fails when the Model Repository component is not running.

  • https://spin.<data_center>:1004/sys/dbstatus.py

    Accessing this URL shows the database connection status in the HTML page. Your automatic monitoring system can use a regular expression to extract the number of active database connections.

Data Access Engine logs

The Data Access Engine logs are in the following files:

  • /var/log/opsware/spin/spin.err* (The main Data Access Engine error file)
  • /var/log/opsware/spin/spin.log* (The main Data Access Engine log file)
  • /var/log/opsware/spin/spin_db.log
  • /var/log/opsware/spin/daemonbot.out (Output from the application server)

In a core with multiple Data Access Engines, each server running a Data Access Engines has a set of these log files.

Send Help Center feedback