How do I stop and start Eclipse services on Linux?

Stop Eclipse

  • Stop VSIFAX:
vfxsched stop
  • Stop samba:
service smb stop
  • Stop PostgreSQL:
service postgresql-8.4 stop

RHEL7

systemctl stop postgresql-9.5
  • Stop SYSTEM.ADMIN, phantoms, JBoss:
service monit stop
service eclipse-jboss stop
service eclipse-system-admin stop

RHEL7

systemctl stop eclipse-api-release
systemctl stop eclipse-jboss.service 
systemctl stop eclipse-system-admin.service 
For secondary accounts (play, train, stage, etc.), substitute “eclipse” for the account name. For example, a “train” account services would be referred to as train-jboss and train-system-admin.
  • Stop UV processes:
cd /u2/uv
bin/uv
#ESC
MASTER OFF ALL
Q
  • Stop remaining phantoms, UV processes:
ps -ef|grep phantom|awk '{print $2}'|xargs -i kill -4 {}
  • Stop UV:
service uv.rc stop

RHEL7

systemctl stop  universe
  • If UV complains that there are open processes, check:
lsof /u2
ipcs -mop|grep 0xaceb

Start Eclipse

  • Start UV:
service uv.rc start

RHEL7

systemctl start  universe
  • Start PostgreSQL:
service postgresql-8.4 start

RHEL7

systemctl start postgresql-9.5
  • Start SYSTEM.ADMIN, phantoms, JBoss:
service monit start
service eclipse-system-admin start
service eclipse-jboss start

RHEL7

systemctl start eclipse-system-admin.service 
systemctl start eclipse-jboss.service 
systemctl start eclipse-api-release
For secondary accounts (play, train, stage, etc.), substitute “eclipse” for the account name. For example, a “train” account services would be referred to as train-jboss and train-system-admin.
  • Start samba:
service smb start

RHEL7

systemctl start smb
  • Start VSIFAX:
vfxsched start

How do I shut down Eclipse on my AIX server?

  • Stop VSIFAX:
vfxsched stop
  • Stop samba:
vi /etc/inetd.conf
  • Comment out netbios lines
refresh -s inetd
  • Kill existing sessions:
ps -ef|grep mbd|awk '{print $2}'|xargs -i kill {}
  • Stop APC PowerChute:
ps -ef|grep ups|awk '{print $2}'|xargs -i kill {}
  • Stop PostgreSQL:
su - postgres -c "/u2/pgsql/bin/pg_ctl stop -l logfile -D /u2/pgsql/data"
  • Stop SYSTEM.ADMIN, phantoms, JBoss:
/u2/eclipse/modules/bin/services.sh -k -d all
  • Stop UV processes:
cd /u2/uv
bin/uv
#ESC
MASTER OFF ALL
Q
  • Stop remaining phantoms, UV processes:
ps -ef|grep phantom|awk '{print $2}'|xargs -i kill -4 {}
who -u |grep -v root|awk '{print $7}'|xargs -i kill -4 {}
  • Stop UV:
uv.rc stop
  • If UV complains that there are open processes, check:
lsof /u2
ipcs -mop|grep 0xaceb
  • Kill each remaining process, as shown in the example below, and try to stop UniVerse again:
kill -4 12345

Which directories should I backup on my Eclipse servers?

The following directories contain the most critical files necessary to recover your Eclipse systems:

  • Database server (AIX, RHEL):
    • /u2 (contains your Eclipse database, UniVerse, JBoss and VSIFAX)
    • /snap/u2 (if using snapshots, this contains the same data as above, but frozen in time)
    • /etc (contains your operating system configuration files)
    • /home (contains your users’ home directories)
    • /usr/spool/uv (contains your legacy UniVerse printer configuration files)
  • Forms server (Windows):
    • C:\Program Files\EclipseForms (contains your Eclipse Forms software)
    • C:\Users\All Users\Application Data\EclipseForms (contains your Eclipse Forms configuration files)
  • Internet Gateway (IGATE) server (Windows):
    • All shared directories containing Eclipse web sites (ex IIS shared directories, etc.)
  • Imaging server (Windows):
    • All shared directories containing Eclipse file shares (ex image attachments, signature scans, etc.)

The UniVerse database must be stopped or suspended during backup to ensure data consistency. The standard Eclipse backup scripts have been modified to use snapshots to allow backups to take place on active systems.

While backing up the directories below should be minimally sufficient to recreate your system in the event of a disaster, backing up the entire system is always recommended when possible. By backing up the entire system, you protect against the loss of miscellaneous files or those inadvertently placed outside of their standard locations.

Eclipse Network Utilization

We are often asked how much bandwidth is used by Eclipse for planning new deployments. Here are some guidelines for estimating the network utilization of Eclipse users based on real-world data we’ve gathered from existing Eclipse customers:

  • Solar customers: 3 KB/s (24 kbps) per user
  • Eterm customers: 1 KB/s (8 kbps) per user

As you can see, the bandwidth requirements for Eclipse are quite low, but it’s important to take into consideration that users’ Internet usage is not limited to Eclipse, and Eclipse performance will suffer if the software has to fight for bandwidth being used for other means (i.e. streaming video and audio, file sharing, etc.). As such, we recommend prioritizing the following protocols used by Eclipse through QoS whenever possible:

  • The Eterm client communicates using the telnet protocol (TCP port 23).
  • The Solar client communicates using a proprietary web service protocol (TCP ports 2080 and 2443).
  • The Eclipse signature capture and document imaging processes communicate over standard Microsoft file sharing protocols.
  • The Eclipse printing processes communicate over standard Windows and UNIX printer ports (i.e. socket, LPD, etc.).

During the initial Solar client installation and after each Eclipse “point” upgrade, the Solar client will perform a one-time download of approximately 20 MB of data. For branches with large numbers of users, this can cause a temporary spike in bandwidth consumption when a large number of users launch the new version of Solar for the first time.

For analyzing your users’ unique usage patterns, we recommend using your network hardware’s built-in tools bandwidth utilization monitoring, or by running Wireshark on a workstation.

How do I enable a printer in AIX?

  • Log into the server as root
  • Enable the UV print queue:
usa +o -p lp1
  • Enable the AIX print queue:
enable lp1
  • Check the status of the print queue:
lpstat -plp1
  • If the status is stuck in SENDING, run fixq, press ENTER followed by the printer name (ie: lp1):
fixq
  • If these commands do not work, it may be necessary to “power cycle” (unplug device from power and plug it back in) the printer AND print server, then repeat the commands above such as “enable lp1” or “fixq”.

You may want to try to “ping” the printer.  From the server, you can type “ping lp1” or from your PC, you can type “ping 192.168.x.x” (substitute the actual IP address for the printer). If you cannot ping the printer, check that the IP is correct, check the switch, cable, etc.  If you cannot ping the printer, it will never print from Eclipse.

Sometimes there is a job “stuck” in the queue that needs to be removed so the rest can print. This will often show up with a job stuck in “sending” when you run this command: lpstat -plp1 (lp1 is an example). You can cancel the job with the following command:

cancel (job number)

Example:

Queue   Dev   Status    Job Files              User         PP %   Blks  Cp Rnk
------- ----- --------- --- ------------------ ---------- ---- -- ----- --- ---
lp13    @lp13 SENDING    51 STDIN.46158        root                   4   1   1
              QUEUED    161 STDIN.7472         root                   4   1   2
cancel 51
To cancel all jobs on lp13, you can type: cancel lp13