0 évaluation0% ont trouvé ce document utile (0 vote)
20 vues1 page
Sonic MQ is a standards-based enterprise messaging system for asyn chronous communication between remote applications. It s CAA Continuous Availability Architecture ensur es system downtime while the Dynamic Routing architecture enables high scalabili ty. The Eclipse-based Sonic Workbench provides an integrated SOA toolset to streamline the lifecycle of an ESB project in complex, distributed environm ents.
Sonic MQ is a standards-based enterprise messaging system for asyn chronous communication between remote applications. It s CAA Continuous Availability Architecture ensur es system downtime while the Dynamic Routing architecture enables high scalabili ty. The Eclipse-based Sonic Workbench provides an integrated SOA toolset to streamline the lifecycle of an ESB project in complex, distributed environm ents.
Droits d'auteur :
Attribution Non-Commercial (BY-NC)
Formats disponibles
Téléchargez comme TXT, PDF, TXT ou lisez en ligne sur Scribd
Sonic MQ is a standards-based enterprise messaging system for asyn chronous communication between remote applications. It s CAA Continuous Availability Architecture ensur es system downtime while the Dynamic Routing architecture enables high scalabili ty. The Eclipse-based Sonic Workbench provides an integrated SOA toolset to streamline the lifecycle of an ESB project in complex, distributed environm ents.
Droits d'auteur :
Attribution Non-Commercial (BY-NC)
Formats disponibles
Téléchargez comme TXT, PDF, TXT ou lisez en ligne sur Scribd
Sonic MQ The Java Messaging Server (www.sonicsoftware.com) Duration : Feb 25th till date Environment : Java, JMS Server, Rational Clear quest, Win XP, Linux Description : Sonic MQ is a standards-based enterprise messaging system for asyn chronous communication between remote applications. In addition to the basic com pliance to the JMS specification, Sonic MQ provides additional features for ensu ring high performance messaging between applications and to provide guaranteed a nd efficient message delivery. It s CAA Continuous Availability Architecture ensur es system downtime while the Dynamic Routing architecture enables high scalabili ty. Sonic MQ is the backbone providing the entire messaging infrastructure for t he Sonic ESB SOA implementation. Role : Assuring the Quality of the product Activities/Responsibilities: Test Execution : Ø Writing platform compatible automation scripts using shell programming. Ø Done Install and Upgrade testing on all platforms using automation scripts. Ø Ensuring the backwards compatibility of the product with the earlier releases. T his included execution, test result analysis of the existing Automation tests. T he execution involved Linux based platforms, HP based platforms apart from Win X P and Win2000 and with various Java versions. Ø Test Result analysis and reporting was an implicit task all the time. Eclipse based Sonic Workbench (www.sonicsoftware.com) Duration : Feb 25th till date Environment : Java, ESB, XML, Sonic MQ (JMS Server), Eclipse, Rational Clear que st, Oracle, Win XP Description : The Eclipse-based Sonic Workbench provides an integrated SOA toolse t to streamline the lifecycle of an ESB project in complex, distributed environm ents. The tools enable easy development; configuration, testing and deployment o f various pieces of an ESB based enterprise application. Various categories of tools form the part of the toolset, which include, the XML editors like XML, XSLT, XSD, Xpath, XQuery editor and other editors which deal with ESB related artifacts for Content based routing(CBR) and Xpath CBR; in ESB and business Process Modeling, Custom services. Role: Assuring the Quality of the product Activities/Responsibilities: a. Test Execution : Ø Writing platform compatible automation scripts using shell programming. Ø Done Install and Upgrade testing on all platforms using automation scripts. Ø Test Result analysis and reporting was an implicit task all the time.
b. GUI test automation: Developed Automation tests for backwards compatibility t
est cases using TPTP an open source tool. This involved writing the tests in jav a and dealing with the scripts in the automation framework which normally doesn t suit backwards compatibility testing. Scripts required some tweaking to enable t he support.