Meta tags:

Headings (most frequently used words):

the, magiclamp, corner, friday, august, 21, 2009, followers, blog, archive, about, me, production, deployments, of, your, esb, applications,

Text of the page (most frequently used words):
the (45), that (14), esb (13), project (11), this (7), production (6), server (6), and (6), deployment (6), #deploy (6), task (6), magiclamp (5), your (5), for (5), with (5), application (4), have (4), should (4), step (4), source (4), version (4), service (4), plan (4), created (4), ant (4), services (4), team (3), about (3), deployments (3), applications (3), august (3), 2009 (3), posts (3), are (3), control (3), very (3), important (3), will (3), new (3), located (3), jdeveloper (3), what (3), you (3), xml (3), file (3), all (3), files (3), software (2), corner (2), when (2), deploying (2), best (2), into (2), folder (2), any (2), there (2), tagging (2), has (2), ensure (2), get (2), true (2), false (2), take (2), corresponding (2), directory (2), oracle (2), suitcase (2), main (2), following (2), properties (2), sometime (2), based (2), target (2), creating (2), which (2), jca (2), time (2), changes (2), user (2), using (2), build (2), been (2), pretty (2), code (2), web (2), skip (2), view, complete, profile, march, april, blog, archive, followers, subscribe, atom, home, older, newer, comments, posted, some, last, thoughts, first, look, j2ee, persistence, signs, contention, may, occurred, during, running, desired, contentions, stored, area, dealt, before, redeployment, happen, default, nothing, once, final, completed, gone, tag, versioning, system, accordingly, required, able, back, particular, forceddeployment, value, forcing, deploymentplanfilename, sourcedirectory, esbmetadataserverport, port, listening, esbmetadataserverhostname, host, url, used, send, entire, requires, entities, can, generate, guids, themselves, entity, entry, create, plans, fact, doing, one, large, contains, representation, single, esbsvc, includes, operations, associated, each, note, every, related, information, run, reflected, steps, assume, everything, local, current, xsl, wsdl, external, then, pre, compile, perform, multiple, customizedocument, schema, location, set, properly, how, does, deal, going, found, solution, implement, tasks, scripts, far, life, easy, but, happens, its, environment, network, issues, consider, possibly, firewall, rules, contend, credentials, general, not, enough, think, also, issue, keeping, track, correct, base, being, deployed, keep, mind, cannot, nicely, archived, ear, like, those, now, probably, working, away, quite, adapters, calls, chaining, them, together, routing, friday, sidebar,

Text of the page (random words):
the magiclamp corner august 2009 skip to main skip to sidebar friday august 21 2009 production deployments of your esb applications by now you probably have been working away for quite sometime using jdeveloper to build your adapters web service calls and chaining them all together with routing services so far life has been pretty easy but what happens when its time to deploy your project to a production environment you have network issues to consider possibly firewall rules to contend with and what about user credentials in general if that is not enough to think about there is also the issue of keeping track of the correct version of the code base being deployed keep in mind that esb code cannot be nicely archived up into a pretty ear file like those of web based applications so how does magiclamp deal with going to production we have found that the best solution for this is to implement ant tasks build scripts and version control tagging the following steps assume that everything is local to the current project if the project is using xsl or wsdl files located on an external server then a pre compile target should be created which will perform multiple customizedocument ant task s on files to ensure that the schema location is set properly step 1 create deployment plans by creating a deployment plan what you are in fact doing is creating one large xml file which contains the xml representation of all of the single esbsvc files located in your project this includes all of the jca operations and properties associated with each service it is very important to note that every time jca related information changes in a service by jdeveloper that the user re run the deployment plan ant task so that the new changes are reflected in the deployment plan xml file step 2 un deploy esb entities un deploying the esb services task can take sometime to generate this task is based on the guids of the services themselves so it is very important that as new services get created in jdeveloper a corresponding un deploy esb entity entry be created in the un deploy target for the project step 3 deploy esb suitcase the deploy esb suitcase is the main ant task used to send the entire project to the esb server this task requires the following properties esbmetadataserverhostname the host url of the oracle esb application server esbmetadataserverport the port that the oracle esb application server is listening on sourcedirectory the directory that the project source is located deploymentplanfilename the corresponding deployment plan created for the source directory forceddeployment true false a true of false value forcing the esb server to take the new service step 4 source control tagging once the final version of the project has completed qa and gone to production it is very important to tag the source control versioning system accordingly this will ensure that if required the deployment team will be able to get back to a particular version of a project that is in production some last thoughts on deployments when re deploying an esb application project it is best to first look into the j2ee persistence folder of the application server for any signs of contention that may have occurred during the running of the desired project contentions are stored in this area and should be dealt with before any redeployment should happen by default there should be nothing in this folder posted by magiclamp software team at 5 28 pm no comments newer posts older posts home subscribe to posts atom the magiclamp corner followers blog archive 2009 4 august 1 production deployments of your esb applications april 1 march 2 about me magiclamp software team view my complete profile