gdata.io.handleScriptLoaded({"version":"1.0","encoding":"UTF-8","feed":{"xmlns":"http://www.w3.org/2005/Atom","xmlns$openSearch":"http://a9.com/-/spec/opensearchrss/1.0/","xmlns$gd":"http://schemas.google.com/g/2005","xmlns$georss":"http://www.georss.org/georss","xmlns$thr":"http://purl.org/syndication/thread/1.0","xmlns$blogger":"http://schemas.google.com/blogger/2008","id":{"$t":"tag:blogger.com,1999:blog-3275735"},"updated":{"$t":"2023-07-27T06:18:49.198-05:00"},"category":[{"term":"Windows"},{"term":"Website"},{"term":"webMethods"}],"title":{"type":"text","$t":"VismiT"},"subtitle":{"type":"html","$t":"means Amaze (विस्मित)."},"link":[{"rel":"http://schemas.google.com/g/2005#feed","type":"application/atom+xml","href":"https://www.blogger.com/feeds/3275735/posts/default/-/webMethods?alt\u003djson-in-script\u0026max-results\u003d6"},{"rel":"self","type":"application/atom+xml","href":"https://www.blogger.com/feeds/3275735/posts/default/-/webMethods?alt\u003djson-in-script\u0026max-results\u003d6"},{"rel":"alternate","type":"text/html","href":"http://vismit.khapre.org/search/label/webMethods"},{"rel":"hub","href":"http://pubsubhubbub.appspot.com/"}],"author":[{"name":{"$t":"Vishal Khapre"},"email":{"$t":"noreply@blogger.com"},"gd$image":{"rel":"http://schemas.google.com/g/2005#thumbnail","width":"35","height":"35","src":"//www.blogger.com/img/blogger_logo_round_35.png"}}],"generator":{"version":"7.00","uri":"https://www.blogger.com","$t":"Blogger"},"openSearch$totalResults":{"$t":"4"},"openSearch$startIndex":{"$t":"1"},"openSearch$itemsPerPage":{"$t":"6"},"entry":[{"id":{"$t":"tag:blogger.com,1999:blog-3275735.post-112125981101656719"},"published":{"$t":"2005-07-13T07:43:00.000-05:00"},"updated":{"$t":"2015-01-29T10:48:54.863-05:00"},"category":[{"scheme":"http://www.blogger.com/atom/ns#","term":"webMethods"}],"title":{"type":"text","$t":"webMethods File Structure."},"content":{"type":"html","$t":"\u003cdiv dir\u003d\"ltr\" style\u003d\"text-align: left;\" trbidi\u003d\"on\"\u003e\nwebMethods Integration Server has a specific structure on file system. That is how it will work consistently. It is strongly advised not to change any files without proper understanding and testing.\nwebMethods Integration Server has following folders\u003cbr /\u003e\n\u003ctable border\u003d\"1\" bordercolor\u003d\"gray\" cellspacing\u003d\"0\" id\u003d\"DataGrid1\" rules\u003d\"all\" style\u003d\"border-collapse: collapse; border: 1px solid gray; width: 80%;\"\u003e\u003ctbody\u003e\n\u003ctr\u003e\u003ctd\u003eaudit\u003c/td\u003e\u003ctd\u003eUsed for Audit store and auditing schemas.\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003ebin\u003c/td\u003e\u003ctd\u003eLocation for executables for wM as service \u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003econfig\u003c/td\u003e\u003ctd\u003ewM configuration files.\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003edatastore\u003c/td\u003e\u003ctd\u003eService cache data\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003edoc\u003c/td\u003e\u003ctd\u003eDocumentation for wM integration server\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003eDocumentStore\u003c/td\u003e\u003ctd\u003eIS document store. Persisting documents published to IS.\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003ejvm\u003c/td\u003e\u003ctd\u003eDirecotry for JVM, if you are using webMethods provided JVM.\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003elib\u003c/td\u003e\u003ctd\u003eLocation for library files (Jars, dlls etc.) \u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003elogs\u003c/td\u003e\u003ctd\u003eLocation for all log files wM creates with all logs.\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003epackages\u003c/td\u003e\u003ctd\u003eLocation for storing all packages.\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003epipeline\u003c/td\u003e\u003ctd\u003eDefault location for storing pipelines when you use savePipelineToFile.\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003ereplicate\u003c/td\u003e\u003ctd\u003eLocation for incoming or outgoing packages, realases, salvage folders.\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003ereposerver\u003c/td\u003e\u003ctd\u003eLocation for wM Repository server.\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003esdk\u003c/td\u003e\u003ctd\u003eLocation for wM SDK files, like C or C++ SDKs.\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003esupport\u003c/td\u003e\u003ctd\u003ewM support files to native operations.\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003eupdates\u003c/td\u003e\u003ctd\u003elocation for new realease, which will be included in server classpath.\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003eweb\u003c/td\u003e\u003ctd\u003eLocation for wM Tomcat cache.\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003eWmRepository2\u003c/td\u003e\u003ctd\u003eRepository folder.\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003eWmRepository4\u003c/td\u003e\u003ctd\u003eRepository folder.\u003c/td\u003e\u003c/tr\u003e\n\u003c/tbody\u003e\u003c/table\u003e\n\u003cbr /\u003e\nUnder packages folder, IS will be looking for all the packages that are available for execution or activation. Each package has a defined structure. This will also have packages from wM. For example,\u003cbr /\u003e\n\u003ctable border\u003d\"1\" bordercolor\u003d\"gray\" cellspacing\u003d\"0\" id\u003d\"DataGrid1\" rules\u003d\"all\" style\u003d\"border-collapse: collapse; border: 1px solid gray; width: 80%;\"\u003e\u003ctbody\u003e\n\u003ctr\u003e\u003ctd\u003ecode\u003c/td\u003e\u003ctd\u003eThis folder has subfolders as code, source and jars. Code is where the comiled class for Java services in that perticular package will be stored. jars is place wher you can include external jars \u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003econfig\u003c/td\u003e\u003ctd\u003eAny package related config files\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003edoc\u003c/td\u003e\u003ctd\u003eDocumentation for the package\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003elib\u003c/td\u003e\u003ctd\u003eExternal/internal libraries for the package\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003emanifest.v3\u003c/td\u003e\u003ctd\u003ePackage manifest, loaded into mamory when the package is loaded.\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003ens\u003c/td\u003e\u003ctd\u003eThis folder has all the code for the pcakege. Except for the java services\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003epub\u003c/td\u003e\u003ctd\u003eWhere the presentation is stored. Usually all the .dsp files are stored in this folder. .access file determines which file can be accessed from the web front end. Define file/folder and ACL in the file to provide specific accesses.\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003eresources\u003c/td\u003e\u003ctd\u003eStill searching what can good use of this folder.\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003etemplates\u003c/td\u003e\u003ctd\u003eAny output templates for the services will be stored in this folder.\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\u003ctd\u003eweb\u003c/td\u003e\u003ctd\u003eThe wMTomcat package uses this folder. Provide the JSP application in this folder that you want to use as the web application under wMTomcat. If there is an application under this folder, the web cache for Tomcat will be in \u003cwm_root\u003e\\IntegrationServer\\web.\u003c/wm_root\u003e\u003c/td\u003e\u003c/tr\u003e\n\u003c/tbody\u003e\u003c/table\u003e\n\u003cbr /\u003e\n\u003cb\u003enode.idf\u003c/b\u003e\nUnder ns folder of your package, you will find the complete structure of the namespace you define in developer. Every package, folder and service will have its own folder. Each folder will have a node.idf file or I would guess something like \"interface definition file\". This file must be something similar to define that it is another branch. You might sometimes see the node namespace entries there, but still a mystery where that is needed.\n\u003cbr /\u003e\n\u003cb\u003enode.ndf \u0026amp; flow.xml\u003c/b\u003e\nFor each flow service you will find the flow.xml file along with node.ndf. For my reference I use, ndf as \"Node Definition File\". This is really used to define the node in your name space. They also have the access information, audit information or service level properties that you define in developer. The actual flow.xml file will contain the steps for the flow service. So all the steps you write in a flow service are embeded in sort of the nodes/elements in the flow.xml. You can see that it has some MAP, COMMENT, SEQUENCE and BRANCH as elements. All of these XML nodes are translated in executable code by webMethods in the form of static classes. I believe the way, classes are loaded as static classes, they enhance all the performance.\nFor a wM document, all we have is a node.ndf file. This file will describe the complete structure of the document.\n\n\u003cbr /\u003e\n\u003cb\u003ejava.frag\u003c/b\u003e\nEvery Java service has its own java.frag file. This file is compiled version of the Java service. As we all know, every java service in wM is merely a method in Java class which is named after the folder name where the service resides. This java.frag file in my guess, is only the pointer/redirection to the compiled class under \u003cpackage_root\u003e\\code\\classes folder. If you do not have this file or the .class file, try using jcode.bat file under \u003cwm_root\u003e\\IntegrationServer\\bin. This will update/compile any java services in the package.\n\nWe really do not need to modify any of these files, as the developer provides the best way to look at and edit them. They perserve the format which is understood by IS and developer too. This means if we try to edit that outside the standard wM editors, we might loose the consistency.\n\u003cbr /\u003e\n\u003cb\u003e.cnf files\u003c/b\u003e\nThese are mainly the configuration files. Most of the cnf files are stored in \u003cwm_home\u003e\\IntegrationServer\\config folder. There can be some cnf files in config folder of each webMethods product. This also means that TNConsole or workflow server will have it's specific cnf files. It is possible that each Wm* package under Integration Server also can have its configuration files. These files are loaded in memory when the server, packages, products are loaded in memory and flushed back to file system when these servers, packages, products are shutdown. All the changes in settings of the product are made in memory and flushed only at shutdown. So do not attempt to make changes in those cnf files when the product is running (I would say do not make changes at all in files directly). There are some more cnf files in config\\jdbc folder. They are for the JDBC pools of the server.\nNote: Everytime the IntegrationServer comes up, it backs up all the cnf files in the backup folder.\n\u003cbr /\u003e\n\u003cb\u003eIntegrationServer\\datastore\\ServiceCache\u003c/b\u003e\nI believe this file is used to make store the cached the service output. This is an encrypted file, as the data is not much visible in clear text.\n\u003cbr /\u003e\n\u003cb\u003eIntegrationServer\\web\\conf\\web.xml\u003c/b\u003e\nMost of the web interfaces in IS are managed by integrated Tomcat server. This is needed even for running the WmMonitor. The explicitely created web applications are deployed under the pub folder. At the time of loading that web context the IS creates the compiled classes under web\\work\\\u003cserver_name\u003e\\\u003cpackage_name\u003e.\nThis web.xml under conf folder is very similar to one under Jakarta Tomcat server. You can modify the same for servlet mapping, logging configurations, mime-mappings and security constraints of web applications.\n\u003ci\u003e.access\u003c/i\u003e files are also used to define security constraints under each \u003cpackage_name\u003e\\pub\\... folder to define ACLs that are allowed to access the files or subfolders at the same level as the .access file.\u003c/package_name\u003e\u003c/package_name\u003e\u003c/server_name\u003e\u003c/wm_home\u003e\u003c/wm_root\u003e\u003c/package_root\u003e\n\u003cbr /\u003e\nNote:\n\u003cbr /\u003e\n\u003cblockquote\u003e\nAll references made to webMethods products are intellectual property of \u003ca href\u003d\"http://www.webmethods.com/\"\u003ewebMethods\u003c/a\u003e. We or webMethods is not responsible for any of the content on this post. All the content on this post is based on merely the observation/experience while working on webMethods platform and must be used, if needed, for supporting, developing on a licensed webMethods product only. The development/support/research made with reference to this post cannot be used as authentic reference or knowledge module anywhere. Nobody can be held responsible including us or webMethods in case of irresponsive system due to changes made with this information.\n\u003c/blockquote\u003e\n\u003c/div\u003e\n"},"link":[{"rel":"replies","type":"application/atom+xml","href":"http://vismit.khapre.org/feeds/112125981101656719/comments/default","title":"Post Comments"},{"rel":"replies","type":"text/html","href":"https://www.blogger.com/comment.g?blogID\u003d3275735\u0026postID\u003d112125981101656719","title":"6 Comments"},{"rel":"edit","type":"application/atom+xml","href":"https://www.blogger.com/feeds/3275735/posts/default/112125981101656719"},{"rel":"self","type":"application/atom+xml","href":"https://www.blogger.com/feeds/3275735/posts/default/112125981101656719"},{"rel":"alternate","type":"text/html","href":"http://vismit.khapre.org/2005/07/webmethods-file-structure.aspx","title":"webMethods File Structure."}],"author":[{"name":{"$t":"Vishal Khapre"},"email":{"$t":"noreply@blogger.com"},"gd$image":{"rel":"http://schemas.google.com/g/2005#thumbnail","width":"35","height":"35","src":"//www.blogger.com/img/blogger_logo_round_35.png"}}],"thr$total":{"$t":"6"}},{"id":{"$t":"tag:blogger.com,1999:blog-3275735.post-110841113417603197"},"published":{"$t":"2005-02-14T14:34:00.000-05:00"},"updated":{"$t":"2007-07-12T10:05:26.708-05:00"},"category":[{"scheme":"http://www.blogger.com/atom/ns#","term":"webMethods"}],"title":{"type":"text","$t":"webMethods and Microsoft .Net"},"content":{"type":"html","$t":"webMethods 6.1 has opened an interface to Microsoft .Net. This makes it very easier to make calls to components that are very hard to create from Java Runtime. This also allows easier IS client creation from MS.Net. I would not take the client creation as the feature because, anyways it was easier earlier, using InterOps, though by having managed interface, it is now faster than earlier. \n\u003cbr\u003e\u003cbr\u003e\n\u003cb\u003ewebMethods does not allow calling Global Assembly Cache\u003c/b\u003e\u003cbr\u003e\nwebMethods can call any service, so the new .Net services can call the .Net assembly classes. The assembly name has to be hard coded in the .Net properties of the service. This makes it further difficult in migration activities. After a considerable research, I could make out that the assembly path can be relative to \u003ci\u003eINTEGRATION_SERVER\u003c/i\u003e folder also than using absolute path.\n\u003cbr\u003e\u003cbr\u003e\n\u003cb\u003ewebMethods creates a service for each method selected for interfacing\u003c/b\u003e\u003cbr\u003e\nWhen creating a .Net service and we need to select assembly, it marks out the classes and their respective methods in the assembly. All selected methods are create a .Net service in the specified folder. So for example, when an assembly has two classses with same procedures/methods with same name, they create a conflict in namespace, so either they have to be in a different logical folder or they have to manually created. This also makes the integration server runtime little heavier I believe, as each method will create a service and then it will be statically loaded in memory when server starts. So it is recommended to create the .Net services for the methods need to be called. I would always avoid calling the .Net service directly, as that will make my application hard to reengineer in case of .Net CLR has performance problems when called from wM.\n\u003cbr\u003e\u003cbr\u003e\n\u003cb\u003eEvery assembly load has a CPU spike\u003c/b\u003e\u003cbr\u003e\nSo far I have seen every assembly load, means appdomain load, has a considerable CPU spike. This spike is due to creation of reflection object loading on the CLR. As long as the  class lifetime is managed properly, we are cool from infrastucture point of view, other wise .Net usage has to be revisited for the consideration."},"link":[{"rel":"replies","type":"application/atom+xml","href":"http://vismit.khapre.org/feeds/110841113417603197/comments/default","title":"Post Comments"},{"rel":"replies","type":"text/html","href":"https://www.blogger.com/comment.g?blogID\u003d3275735\u0026postID\u003d110841113417603197","title":"0 Comments"},{"rel":"edit","type":"application/atom+xml","href":"https://www.blogger.com/feeds/3275735/posts/default/110841113417603197"},{"rel":"self","type":"application/atom+xml","href":"https://www.blogger.com/feeds/3275735/posts/default/110841113417603197"},{"rel":"alternate","type":"text/html","href":"http://vismit.khapre.org/2005/02/webmethods-and-microsoft-net.aspx","title":"webMethods and Microsoft .Net"}],"author":[{"name":{"$t":"Vishal Khapre"},"email":{"$t":"noreply@blogger.com"},"gd$image":{"rel":"http://schemas.google.com/g/2005#thumbnail","width":"35","height":"35","src":"//www.blogger.com/img/blogger_logo_round_35.png"}}],"thr$total":{"$t":"0"}},{"id":{"$t":"tag:blogger.com,1999:blog-3275735.post-109037084544489693"},"published":{"$t":"2004-07-20T19:47:00.000-05:00"},"updated":{"$t":"2007-07-12T10:05:26.708-05:00"},"category":[{"scheme":"http://www.blogger.com/atom/ns#","term":"webMethods"}],"title":{"type":"text","$t":""},"content":{"type":"html","$t":"\u003ch5\u003eChanging the \u003ca href\u003d\"http://www.webmethods.com\"\u003ewebMethods\u003c/a\u003e JDBC Adapter Connection\u003c/h5\u003e\nNot sure how many people in software world look around for webMethods help on Internet. Actually, being a google fan, I am used search all the problems and all the knowledge on the Great Internet. Surely tried to search for some solutions on Internet, I got some of them, but not all of them. As we know everything is an node.ndf and/or flow.xml on file system in the little world of webMethods.\u003cbr\u003eConsidering the basic fact webMEthods does not support any version control tool integrated with \"webMethods Developer\".  So we have to manage version control for multi developer shop on the basis understanding and coordination. (Offcourse lot of software consultants don;t have that). Then we have more than 3-4 environments and needs to have concurrent development practice. This compelled all around to ding in more and find some way of dynamically creating and destroying local development environments. This allows local development and then uploading that on servers\u003cbr\u003eThe compulsion gave rise for the need of using the scripts and or programs to get the automation in place. One of the biggest pain all the time was to modify the JDBC Connections, so that we can script the deployment on webMethods environments.\u003cbr\u003e\u003cbr\u003e\n\u003ca href\u003d\"http://www.webmethods.com\"\u003ewebMethods\u003c/a\u003e uses the \u003ca href\u003d\"http://dictionary.reference.com/search?q\u003djdbc\u0026r\u003d67\" title\u003d\"See what is JDBC?\"\u003eJDBC\u003c/a\u003e adapter services to connect to databases. As we all know we need to use the JDBC connection defined. This means when we move the code from one environment to other, we have to manually, change connection properties. Scott Conely from \u003ca href\u003d\"http://www.ThoughtWorks.com\"\u003eThoughtWorks\u003c/a\u003e introduced me to a new way of working with node.ndf files which reside for each service in webMethods. \u003cbr\u003e\u003cbr\u003e\nEvery node.ndf file is basically the XML file internally, which stores the information about the service is all about. If you open this with a any \u003ca href\u003d\"http://dictionary.reference.com/search?q\u003dxml\u0026r\u003d67\" title\u003d\"What's XML?\"\u003eXML\u003c/a\u003e editor, we can definitely see the data that webMethods needs for its working. This serialized XML element is \u0026lt;value name\u003d\u0026quot;IRTNODE_PROPERTY\u0026quot;\u0026gt; which stores the whole serialized object which has information about the JDBC connection. If we could deserialize that object. We can see all the properties of the connection set up from the JDBC Adapters menu of IS Administrator UI. The idea of changing the adapter connection can allow connection manipulation task through scripting. If one can deserialize the data in that element, the changing the connection properties are easier. Then serialize it back and then put that back into node.ndf. Done ... we have modified the node.ndf of connection successfully. \u003cbr\u003e\u003cbr\u003e\n\nLet see if we can do this. Use \u003cb\u003ecom.wm.util.coder.XMLCoder\u003c/b\u003e, offcourse gets installed with webMethods installation, to deserialize the element.  Basically, this is how it would look loke after the object is deserialized.\u003cbr\u003e\n\n\u003cblockquote\u003e \u003e\u003e\u003eBasicData:connectionNodeVersion\u003d1, adapterTypeName\u003dJDBCAdapter, connectionFactoryTypeName\u003d com.wm.adapter.wmjdbc.connection.JDBCConnectionFactory, connectionProperties\u003d \u003e\u003e\u003eBasicData:transactionType\u003dNO_TRANSACTION, datasourceClass\u003d com.microsoft.jdbcx.sqlserver.SQLServerDataSource, serverName\u003dohclests5337a, user\u003dUSER_NAME, password\u003dO/EO8SEgPac\u003dHnSdKdaf6Cs\u003d, databaseName\u003dkpiSchema6, portNumber\u003d1433, networkProtocol\u003d, otherProperties\u003d\u003c\u003c\u003c, connectionManagerProperties\u003d \u003e\u003e\u003eBasicData:poolable\u003dtrue, minimumPoolSize\u003d1, maximumPoolSize\u003d10, poolIncrementSize\u003d1, blockingTimeout\u003d1000, expireTimeout\u003d1000\u003c\u003c\u003c, connectionEnabled\u003dtrue, xflds\u003d[0]password\u003c\u003c\u003c \u003c/blockquote\u003e\n\nSo if you can change these objects and its data elements, the modification is done. Beware when youa re doing it, rememebr that the the whole object you receive is nested IData. if you don't handle this carefully this will spoil the whole connection setup, but who care we can definitely recreate those connections when testing out the program. I did this in Java ... and when I checked with Scott, seems he also did the same way. Finally, Scott showed me something as the password which cannot be modified as it is encrypted in the IData object. Simple solution is change it to new encrypted value, instead of finding encryption. Smart guys ... know how to get the encrypted password before scripting. \n\u003cbr\u003e\nGood Luck !!!"},"link":[{"rel":"replies","type":"application/atom+xml","href":"http://vismit.khapre.org/feeds/109037084544489693/comments/default","title":"Post Comments"},{"rel":"replies","type":"text/html","href":"https://www.blogger.com/comment.g?blogID\u003d3275735\u0026postID\u003d109037084544489693","title":"2 Comments"},{"rel":"edit","type":"application/atom+xml","href":"https://www.blogger.com/feeds/3275735/posts/default/109037084544489693"},{"rel":"self","type":"application/atom+xml","href":"https://www.blogger.com/feeds/3275735/posts/default/109037084544489693"},{"rel":"alternate","type":"text/html","href":"http://vismit.khapre.org/2004/07/changing-webmethods-jdbc-adapter.aspx","title":""}],"author":[{"name":{"$t":"Vishal Khapre"},"email":{"$t":"noreply@blogger.com"},"gd$image":{"rel":"http://schemas.google.com/g/2005#thumbnail","width":"35","height":"35","src":"//www.blogger.com/img/blogger_logo_round_35.png"}}],"thr$total":{"$t":"2"}},{"id":{"$t":"tag:blogger.com,1999:blog-3275735.post-107798413441552072"},"published":{"$t":"2004-02-28T11:02:00.000-05:00"},"updated":{"$t":"2007-07-12T10:05:26.708-05:00"},"category":[{"scheme":"http://www.blogger.com/atom/ns#","term":"webMethods"}],"title":{"type":"text","$t":""},"content":{"type":"html","$t":"\u003ch5\u003e\u003ca href\u003d\"http://cert.webmethods.com/\"\u003ewebMethods 6 Certified Developer\u003c/a\u003e\u003c/h5\u003e\nI am primarily a Microsoft Technologies based application developer, the systems based programming interest me more than anything. But due to some recent developments in existing assignment, \u003cimg width\u003d\"100\" height\u003d\"48\" src\u003d\"http://cert.webmethods.com/CertCandidate/certified-small.gif\" vspace\u003d\"3\" hspace\u003d\"5\" align\u003d\"right\"\u003eI have to learn \u003ca href\u003d\"http://www.webmethods.com/\"\u003ewebMethods\u003c/a\u003e, which is a fastest growing integration platform. Taking this as an opportunity I passed \"webMethods 6 Developer Certification\" exam. The exam is online and free tot ake but needs some work experience on the technology. \u003cbr\u003e\nBeing totally Java based immune to convert the ideologies in EAI arena, webMethods can be known more at its \u003ca href\u003d\"http://advantage.webmethods.com/\"\u003eadvantage website\u003c/a\u003e. I will keep on writing more about this technology more and more in future."},"link":[{"rel":"edit","type":"application/atom+xml","href":"https://www.blogger.com/feeds/3275735/posts/default/107798413441552072"},{"rel":"self","type":"application/atom+xml","href":"https://www.blogger.com/feeds/3275735/posts/default/107798413441552072"},{"rel":"alternate","type":"text/html","href":"http://vismit.khapre.org/2004/02/webmethods-6-certified-developer-i-am.aspx","title":""}],"author":[{"name":{"$t":"Vishal Khapre"},"email":{"$t":"noreply@blogger.com"},"gd$image":{"rel":"http://schemas.google.com/g/2005#thumbnail","width":"35","height":"35","src":"//www.blogger.com/img/blogger_logo_round_35.png"}}]}]}});