|
1
|
Network and Infrastructure Planning
a) Identify where to host the EMP servers
b) Identify the broadband or connectivity requirements of the HQ
c) Identify the connectivity requirements of the remote access users.
d) Identify if there's any backup connectivity required
|
|
Signature:
Date:
|
Signature
Date:
|
|
4.
|
Check the network setup:
a) Internet Connection
b) Modem / modem-router
Determine if it is a modem or a modem-router, this is straight
forward, login to the modem or modem router to look at the
functionality and features, e.g. dynamic dns, port forwarding, DMZ etc.
Look at the external IP and internal IP if it is a modem-router.
c) Router
Make sure the port forwarding / DMZ and dynamic dns (if applicable) is properly configured.
d) Local Area Network
Make sure there's no conflicting IP address with the server.
* Note, if you are doing port forwarding or dynamic DNS, some of the
routers that have been tested successfully are SMC, DLink, Linksys.
Other routers may work, but some brands are known to be not functioning
properly.
|
Write down the following:
a) external IP or dynamic dns hostname
b) server IP, netmask, gateway
c) Router IP address
|
Signature:
Date:
|
Signature:
Date:
|
|
6.
|
Security and System Hardening
a) Protect JBOSS JMX Page from being accessed by users
- Replace with a redirector to wavelet.biz website.
b) Modify /etc/ssh/ssh_config
- Disable root ssh access, only normal user could login
- Create a username: vincent, password: wavelet, then email the
username password to vincent@wavelet.biz with IP address or dyndns
hostname.
c) Disable apache web server.
d) nmap localhost to check if http port is opened.
|
|
Signature:
Date:
|
Signature:
Date:
|
|
8.
|
Database Optimization and Clearing Memory
a) Produce a cron script to "vacuum" the database every night
b) If there are jboss memory that needs to be cleared, we could do a server reboot in the middle of the night to clean it up.
c) Ensure the cron job is vacuuming the correct database, as it may
not be " wsemp". See
/usr/java/jboss/server/default/deploy/postgres-ds.xml
|
|
Signature:
Date:
|
Signature:
Date:
|
|
10
|
Fine Tuning JBoss Application Server
a) Java Virtual Machine Heap size
Modify /usr/java/jboss/bin/run.conf
Modify the stock size from 128M to 512M or 1024M based on the available RAM in the system (50% of the RAM).
b) Ensure updated version of J2SDK.
c) Ensure the JDBC driver for PostgreSQL is correct. If the database
is using version 8.1. A copy of the jdbc drivers could be obtained
inside emp6/lib directory when you check out the cvs, you can use it to
replace the pg7.4jdbc.jar inside /usr/java/jboss/server/default/lib directory.
d) Ensure the JBoss root context is redirected to www.wavelet.biz.
Click here to see more details:
|
|
Signature:
Date:
|
Signature:
Date:
|
|
11
|
Adding company logo
a) Obtain the image file from merchant
b) Add this file to emp6/src/web/custom/<merchant-name>/<image-file-name>
c) CVS checkin and commit
d) Deploy at merchant server
e) Login and configure the Branch Settings under DEVELOPER -> BRANCH LISTING -> EDIT BRANCH
|
|
Signature:
Date:
|
Signature:
Date:
|
