chin-yeh's activity
From 09/04/2010 to 10/03/2010
10/01/2010
- 05:04 PM POC - Prototype Feature #31 (In Progress): integrate queue system with web service provider
- 05:02 PM POC - Prototype Feature #30 (Closed): build OXM utility
- checkout the trunk from http://192.168.2.13:50000/svn/commons/trunk
- 11:03 AM POC - Prototype Feature #35 (Closed): conduct integration test
- this integration test assumes that the following items are ready:
* ecosway adaptor
* jms adaptor
* web service - 10:59 AM POC - Prototype Feature #34 (Closed): develop the integration test
- build an automated integration test for the integrated components
- 10:43 AM POC - Prototype Feature #33 (Closed): develop a callback to receive synchronzation status
- the status will be updated to event table
- 10:41 AM POC - Prototype Feature #32 (Closed): develop DAO for event table
- develop a DAO for the event table which provides:
* insert
* update
* delete
* retrieve
09/30/2010
- 04:56 PM POC - Prototype Feature #31 (Closed): integrate queue system with web service provider
- 04:54 PM POC - Prototype Feature #30 (Closed): build OXM utility
- the utility will be used to serialize object to or from an XML.
- 03:42 PM POC - Prototype Feature #26 (Closed): perform load test
09/28/2010
- 06:39 PM POC - Prototype Feature #26 (In Progress): perform load test
- conduct the load test again using the development environment
- 06:36 PM POC - Prototype Feature #27 (Closed): integrate the JMS, Web Service, Adaptor
09/24/2010
- 04:12 PM POC - Prototype Feature #27: integrate the JMS, Web Service, Adaptor
- most of components are already integrated, except dot adaptor and web services
- 04:09 PM POC - Prototype Feature #26 (Resolved): perform load test
- see [[Qconnector:Load Test Prototype]] for the load test result
09/23/2010
- 11:06 AM POC - Prototype Feature #26 (In Progress): perform load test
- 09:11 AM POC - Prototype Feature #27 (In Progress): integrate the JMS, Web Service, Adaptor
09/22/2010
- 06:35 PM POC - Prototype Feature #28 (Closed): build the mimic web service
- 04:39 PM POC - Prototype Feature #7 (Closed): develop the soap adaptor
- this adaptor will receive and forward web service request in plain XML content
09/21/2010
- 04:48 PM POC - Prototype Feature #29 (Closed): build dummy web services
- 11:30 AM POC - Prototype Feature #29 (In Progress): build dummy web services
- 11:26 AM POC - Prototype Feature #29 (Closed): build dummy web services
- act as the dummy web service which receives request from JMS system.
- 11:24 AM POC - Prototype Feature #28 (Closed): build the mimic web service
- The mimic web service is act as a proxy and all of request will actually store in the JMS system.
In order to mak... - 11:19 AM POC - Prototype Feature #27 (Closed): integrate the JMS, Web Service, Adaptor
- the dot com adaptor might not included as the component is yet to be developed.
- 11:16 AM POC - Prototype Feature #26 (Closed): perform load test
- suggest the following load test:
* average message sent per second
* average message consumed per second
* maximum... - 11:13 AM POC - Prototype Feature #7 (In Progress): develop the soap adaptor
- 11:11 AM POC - Prototype Feature #8 (Closed): develop the jms adaptor
- 11:03 AM POC - Prototype Feature #8: develop the jms adaptor
- this adaptor consists of 2 components:
* message producer
* message consumer in listening mode
09/15/2010
- 03:06 PM Service Monitoring System Feature #22 (Closed): configure instant message for notification
- able to send IM to XMPP supported message server
- 03:04 PM Service Monitoring System Feature #23 (Closed): configure SMS as nagios notification
09/13/2010
- 12:15 PM POC - Prototype Feature #8 (In Progress): develop the jms adaptor
- 11:45 AM Service Monitoring System Feature #21 (Closed): simulate all of the configured alarm traps
- 11:45 AM Service Monitoring System Support #24 (Closed): prepare documentation
- the completed documentation can be found at [[Documentation]]
09/08/2010
- 09:04 AM Service Monitoring System Support #24 (In Progress): prepare documentation
- this documentation generally will be breakdown into 3 parts, which are installation, configuration and administration.
- 09:01 AM Service Monitoring System Feature #21 (Feedback): simulate all of the configured alarm traps
- all of the configured alarms are tested and the email notification will be sent to this 2 email a/c, [[wiki#Test-emai...
09/07/2010
- 06:20 PM Service Monitoring System Feature #21 (Resolved): simulate all of the configured alarm traps
- 02:18 PM Service Monitoring System Feature #21: simulate all of the configured alarm traps
- chin-yeh wrote:
> simulate the following configured traps:
> * average load
> * swap usage
> * disk space usage
... - 02:13 PM Service Monitoring System Feature #21 (In Progress): simulate all of the configured alarm traps
- 02:09 PM Service Monitoring System Feature #20 (Closed): configure the email notification
- instead of using tpm office's mail server, use recipient's relay email to send outgoing email. this is because tpm of...
- 09:12 AM Service Monitoring System Feature #20 (In Progress): configure the email notification
09/06/2010
- 07:38 PM Service Monitoring System Feature #25 (Closed): add alarm trap for jboss
- 05:52 PM Service Monitoring System Feature #25 (In Progress): add alarm trap for jboss
- add alarm trap:
* number of in-use connection in connection pool for specific data source - 04:56 PM Service Monitoring System Feature #25 (Closed): add alarm trap for jboss
- add the number of established connection for the specific data source(s)
- 05:49 PM Service Monitoring System Feature #17 (Closed): configure the DB2 alarm traps
- configured:
* db2 CONNECT - 01:56 PM Service Monitoring System Feature #17: configure the DB2 alarm traps
- use the plugin, "check_db2_health":http://labs.consol.de/lang/en/nagios/check_db2_health/
- 01:51 PM Service Monitoring System Feature #17 (In Progress): configure the DB2 alarm traps
- 01:48 PM Service Monitoring System Feature #19 (Closed): configure alarm traps for external system
- 01:42 PM Service Monitoring System Feature #19: configure alarm traps for external system
- chin-yeh wrote:
> * UPS
> ** street address validation
> ** package rating
> * Avatax
> * Authorize.net
> * dot... - 10:47 AM Service Monitoring System Feature #19 (In Progress): configure alarm traps for external system
- chin-yeh wrote:
> * UPS
> * Avatax
> * Authorize.net
add:
* dotcom mall
* dot biz mall
* usmall
- 10:37 AM Service Monitoring System Support #24 (Closed): prepare documentation
- purpose to prepare the following docs:
# define the list of the application needed to be installed in monitoring hos... - 10:07 AM Service Monitoring System Feature #16 (Closed): adjust the alarm thresholds
- 10:06 AM Service Monitoring System Feature #16 (Resolved): adjust the alarm thresholds
- 10:06 AM Service Monitoring System Feature #16: adjust the alarm thresholds
- adjusted both os and jboss alarm traps
- 09:16 AM Service Monitoring System Feature #16 (In Progress): adjust the alarm thresholds
- 09:34 AM Service Monitoring System Feature #23 (Closed): configure SMS as nagios notification
- r&d if any of the equipment or software is required in order to enable the SMS notification
- 09:30 AM Service Monitoring System Feature #22 (Closed): configure instant message for notification
- r&d if using instant message as alert notification possible or not
- 09:24 AM Service Monitoring System Feature #21 (Closed): simulate all of the configured alarm traps
- simulate the following configured traps:
1) average load
2) swap usage
3) disk space usage
4) jboss's heap memory...
Also available in: Atom