Deployment Strategies

I am working in a medium project that have in average 200 CMP entity beans. Actually,
we have a mapping between each data base table with a CMP. Every time that we
develop a new functionality the jar grows up and in fact, the deploying time grows
up. This is a big problem if we think that only we had develop the 5% of all project
and it spent much time making building of the jar. I would like to know if exist
an extrategy to control the growth of the jar, for example do not map every table
to an entity to make modules, and make build in independent form, one module for
one group of functionality. The problem is that in this project exist a group
of entities that are common for every functionality, Country, City, User, etc..
This is the only strategy in which we could think but we do not have a clear judgement
to decide which tables must to be mapped, only the ones that are not catalogs?.
If you can guide me about the better form to organize my project or show me a
knowledge base with similars problems I would thank you , very much.
Thanks in advance,
Monica A.

Which activities are taking a long time? The ejbc/appc step? or the boot of the
server and deployment of all the beans? Makes a difference, because splitting
up a large number of beans in to multiple JAR files might help with the time it
takes to create each JAR file but wouldn't help with deployment time.
I've seen applications with 300+ entity beans, and while it is a little painful
to run ejbc/appc and deploy the resulting ejb file, it wasn't bad enough to invalidate
the approach or require multiple files. How long are steps taking now? How many
beans, and what hardware are you using for the various steps in the process?
-Greg
http://www.amazon.com/exec/obidos/ASIN/047128128X/
"monica" <[email protected]> wrote:
>
I am working in a medium project that have in average 200 CMP entity
beans. Actually,
we have a mapping between each data base table with a CMP. Every time
that we
develop a new functionality the jar grows up and in fact, the deploying
time grows
up. This is a big problem if we think that only we had develop the 5%
of all project
and it spent much time making building of the jar. I would like to know
if exist
an extrategy to control the growth of the jar, for example do not map
every table
to an entity to make modules, and make build in independent form, one
module for
one group of functionality. The problem is that in this project exist
a group
of entities that are common for every functionality, Country, City, User,
etc..
This is the only strategy in which we could think but we do not have
a clear judgement
to decide which tables must to be mapped, only the ones that are not
catalogs?.
If you can guide me about the better form to organize my project or show
me a
knowledge base with similars problems I would thank you , very much.
Thanks in advance,
Monica A.

Similar Messages

ASK: Forms Server deploy strategie and version controlling...

hi:
I would like to ask people around how could i have a good forms deploy strategie that would allow me to upgrade forms fmx versions even if users where connected to forms server.
I have used hearbeat option to disconnect ifbweb60 processes, but without success. That processes just stop/end when i close all IE windows of the user that's connected to that process and not when i close that single forms browser window. May be the heartbeat is working wrongly and "thinks" that the window still open... i dont know...
How "you" users around the world deploy your forms? how you controll and upgrade them ? do you need that all users should be disconnected from forms server to upgrade ?
thankx in advance...
ricardo

oops to get old versions of jre have to use:
https://java.sun.com/products/archive/

Recommended Deployment Strategies for Building FlexStack

I have found the "Recommended deployment strategies for building flexstack"
These are the important items to consider when deploying FlexStack:
• It is recommended that the stack master not contain uplinks if it is possible to distribute the uplinks across other stack member
• When using only two uplinks in a stack of four members, put the uplinks on members that are not directly connected with FlexStack links. Directly connected members are those connected together with FlexStack connections. This is only relevant on FlexStack groups that contain four members.
– This recommendation is purely for stack bandwidth efficiency. Placing the FlexStack uplinks on directly connected members is less efficient on stack bandwidth. In a four-member stack, with members connected 1-2, 2-3, 3-4, 4-1, put the uplinks on members 2 and 4 or 1 and 3.
So For a Stack of 4 WS-C2960S If we use two links to create an etherchannel "Recommended deployment strategies for building flexstack" is to use an interface on Switch 2 and another on Switch 4 for the etherchannel to Core Switch.
If we want to create an etherchannel of four links, is the recommanded deployment strategies also to use two interfaces on Switch 2 and two interfaces on Switch 4?

Which activities are taking a long time? The ejbc/appc step? or the boot of the
server and deployment of all the beans? Makes a difference, because splitting
up a large number of beans in to multiple JAR files might help with the time it
takes to create each JAR file but wouldn't help with deployment time.
I've seen applications with 300+ entity beans, and while it is a little painful
to run ejbc/appc and deploy the resulting ejb file, it wasn't bad enough to invalidate
the approach or require multiple files. How long are steps taking now? How many
beans, and what hardware are you using for the various steps in the process?
-Greg
http://www.amazon.com/exec/obidos/ASIN/047128128X/
"monica" <[email protected]> wrote:
>
I am working in a medium project that have in average 200 CMP entity
beans. Actually,
we have a mapping between each data base table with a CMP. Every time
that we
develop a new functionality the jar grows up and in fact, the deploying
time grows
up. This is a big problem if we think that only we had develop the 5%
of all project
and it spent much time making building of the jar. I would like to know
if exist
an extrategy to control the growth of the jar, for example do not map
every table
to an entity to make modules, and make build in independent form, one
module for
one group of functionality. The problem is that in this project exist
a group
of entities that are common for every functionality, Country, City, User,
etc..
This is the only strategy in which we could think but we do not have
a clear judgement
to decide which tables must to be mapped, only the ones that are not
catalogs?.
If you can guide me about the better form to organize my project or show
me a
knowledge base with similars problems I would thank you , very much.
Thanks in advance,
Monica A.

Version control and deployment strategies

Hi,
I was looking for input from the community on general
strategies for using version control and managing deployments to
test/stg/production.
Currently, I am using subversion to track my source code, and
using the standard flex builder build routine to produce my binary
output and test. My output is stored locally on a shared vmware
drive, so that it can be served up with a linux vm running apache
(this is not dissimilar to just local testing)
Now I'm getting ready to deploy to some remote testing server
though, so I'm trying to think of the best way to go about it. I
would like to tag my code in svn with a release tag, as is my
practice in other platforms. Should I also store the bin folder in
svn? Should I check in the resulting binary code independently in a
separate repository/directory and then tag it there? Should I
create a new build target to deploy directly to my testing server?
The issue with the tagging approach seems to be that if I
want to rebuild the code or redeploy it for any reason, I would
have to checkout the tagged code in a separate directory, import it
as a new project, rebuild and then redeploy.
If I checked in the tested binaries into a separate
repository/folder, I could always just do an svn export for
deployment, but I'm not sure if that would cause any weird issues,
and it seems a bit wasteful. I suppose I could build from the tag
and zip up the resulting release and just make it available via
normal download, but it seems that I would likely then have lots of
working directory checkouts as flex builder projects for each tag
or release, just so that I could rebuild from them....doesn't seem
very elegant.
I'm very interested in hearing any feedback on this. How do
you do it?
thanks,
Cliff

flex with ant is still not very very popular
combination,since FB does all for you anyways, but I have to say
ant is lot more flexible, especialy if you combine it with FB, ant
can do pretty much anything, ...
here is link about flex's ant tasks
http://livedocs.adobe.com/flex/3/html/help.html?content=anttasks_1.html
most of the projects I have done in Flex were with ant,
here is general approach:
for internal testing I let flex builder build and deploy
within integrated tomcat,this is also where I do debugging, FB is
pretty good about that.
then I have following targets :
build target - builds optimized version of flex app, only
using library classes that are needed by project, also using that
to feed my Modules building tasks so that they exclude all class
references (like Button, Tabnavigation etc... ) from their compiled
units,
something like this (this is my old fb2 example) i don't have
fb3 example handy right now :
quote:
<mxmlc file="${basedir}/main.mxml"
debug="false"
optimize="true"
output="${dir.web}/main.swf"
show-binding-warnings="false"
show-actionscript-warnings="false"
link-report="${basedir}/docs/my-links.xml"
use-network="true">
<load-config
filename="/configdir/modified/flex-config.xml"/>
<source-path path-element="${FLEX_HOME}/frameworks"/>
<compiler.library-path dir="." append="true">
<include name="lib" />
</compiler.library-path>
<compiler.source-path path-element=""/>
<compiler.source-path path-element="src"/>
<metadata description="some app">
<contributor name="John Doe" />
<contributor name="Apple Orangino" />
</metadata>
</mxmlc>

<mxmlc file="${basedir}/mymodule.mxml"
debug="false"
optimize="true"
output="${dir.web}/mymodule.swf"
show-binding-warnings="false"
show-actionscript-warnings="false"
load-externs="${basedir}/docs/my-links.xml"
use-network="true" >
<load-config
filename="/configdir/modified/flex-config.xml"/>
<source-path path-element="${FLEX_HOME}/frameworks"/>
<compiler.source-path path-element=""/>
<compiler.source-path path-element="src"/>
<metadata description="some app">
<contributor name="John Doe" />
<contributor name="Apple Orangino" />
</metadata>
</mxmlc>
tag -target tags release based on parameter of latest tag
plus number increment I configure in properties file.
Utility targets :
classpath target - builds classpath string for compc task.
commit target : commits source code, before building.
resources target - copies all resources files to build
directory,
deploy-local target- deploy to local Integration server
deploy-remote target deploy to remote uat server.
test -target - run test cases over classes and generate
report.
and of course all famous asDoc target :)
good thing is that you can create "ant builder" under project
properties and chain your targets with flexbuilder's build
commands,
you can also easily integrate with build servers ( I use
hudson)
here is example :
http://hudson.amostudio.com/
MR hudson checks out code for you, builds it using ant
targets you tell it to use, and reports to you, its pretty cool and
very handy to always have active build proccess over codebase, of
course in some cases its overkill, but most of the times, MR hudson
is good to have.
unfortunately all my ant files are for external clients I
cant disclose them, but I can write blog about some general (apples
and oranges) example, hhm that's actually good idea :) I can shake
off some stress as well :)
thanks for the idea :)
hth
regards
levan

Deployment in enterprise environment

Dear Team members,
I would like to post a question to you regarding deployment doubts that we are trying to address.
My company is working on the new version of our primary application previously built as a J2EE application with some reporting functions with Flex, and we want to use AIR in order to leverage its possibilities:
Seamless integration with existing application functionalities (implemented as standard JEE web application pages) thanks to the integrated HTML capabilities
Improved integration of the user interface with the desktop
Native processes to provide additional functionalities
Our application is targeted to pharmaceutical industry, subject to FDA regulations, and it affects more than 5000 users for each customer, so we have some specific requirements affecting the deployment and distribution of the software:
Allow to run multiple versions of the software on the same client machine (to support test and acceptance activities in addition to the production environment)
Minimize the effort of the initial setup on each client
Manage the version upgrades without manual activities on each client
Keep the test/acceptance and production environments strictly aligned to improve effectiveness of formal validation (ideally, an application once validated should be transported in production without any source code modification, recompilation or repackaging)
The current browser-based strategy is perfectly fit to these requirements, and in the shift towards a desktop-based strategy we need to continue satisfying them as much as possible. We evaluated the standard distribution strategy of Adobe AIR applications, and noticed several attention points in this scenario.
The first issue we encountered is the back-end services endpoint discovery problem. Simply hardcoding a server URL in the packaged application could be a viable solution for public internet-accessible applications, but we need to support multiple customers in their intranet, and each one typically requires multiple environments for the application (acceptance, production, etc.). Maintaining dozens of different packages of the AIR application to support all these customer environments clearly is not the solution. Neither we want to force thousands of different users to enter and maintain the correct server location in their local preferences.
So, we thought to use a badge hosted in the back-end application to run the local AIR application: using the underlying API, we could activate the application specifying also the network location of the back-end services. We could also rely on the badge to install the application (and the AIR runtime if necessary)… however, application packaged as native installers cannot be installed, upgraded, or launched by the badge API (and we need to package ours as native to use native processes).
We also noticed that multiple versions of an AIR application cannot be installed side-by-side in a client machine, and that the installation and upgrade of the application can be performed only when the local user has administrative rights on the machine (using standard or native packages), forcing us to rely on external software distribution systems in some customer scenarios (introducing additional complexities in the release cycle)
At this point, in our opinion the standard deployment strategies of Adobe AIR applications are unfit for enterprise environments. In the enterprise world, many of the applications have migrated to a completely browser-based solution, while others enhanced their client layer to comply with the requirements, for example installing only a thin portion of the client code and allowing to connect to multiple server versions/environments with it (e.g. the SAP GUI universal client). Without smarter deployment and distribution tools, AIR applications currently are a step back compared to web applications in terms of manageability.
So, we are trying to develop a solution to address these problems, with some concepts similar to JStart: install on the client machine a launcher application capable of being activated from a web page, dynamically locate, download and run the actual client bytecode, transparently enforce client software updates, and supporting multiple applications (and multiple versions of the same application). However, we are facing many technical problems due to internal architecture of AIR and we already spent a considerable amount of effort trying to find a solution. We are now thinking to return on the choice of AIR, going back to Flex.
What is the position of Adobe on this argument? Is Adobe aware of these issues and are there any plans on this topic? Any advice?
Thank you in advance

For those following along, Oliver Goldman will be answering this post in future articles on his blog.
Many great comments and questions here. I’m working on some follow-up posts to address these; nothing I could cram into this comment field would really do your query justice. - Oliver Goldman
Pursuit of Simplicity
Chris

Deployment of an Adobe AIR application in an enterprise environment

Dear Team members,
first of all my apologies for posting this thread in more than one forum (see Installations Issues) but the argument is very important to us and I don't know where discuss it.
I would like to post a question to you regarding deployment doubts that we are trying to address.
My company is working on the new version of our primary application previously built as a J2EE application with some reporting functions with Flex, and we want to use AIR in order to leverage its possibilities:
Seamless integration with existing application functionalities (implemented as standard JEE web application pages) thanks to the integrated HTML capabilities
Improved integration of the user interface with the desktop
Native processes to provide additional functionalities
Our application is targeted to pharmaceutical industry, subject to FDA regulations, and it affects more than 5000 users for each customer, so we have some specific requirements affecting the deployment and distribution of the software:
Allow to run multiple versions of the software on the same client machine (to support test and acceptance activities in addition to the production environment)
Minimize the effort of the initial setup on each client
Manage the version upgrades without manual activities on each client
Keep the test/acceptance and production environments strictly aligned to improve effectiveness of formal validation (ideally, an application once validated should be transported in production without any source code modification, recompilation or repackaging)
The current browser-based strategy is perfectly fit to these requirements, and in the shift towards a desktop-based strategy we need to continue satisfying them as much as possible. We evaluated the standard distribution strategy of Adobe AIR applications, and noticed several attention points in this scenario.
The first issue we encountered is the back-end services endpoint discovery problem. Simply hardcoding a server URL in the packaged application could be a viable solution for public internet-accessible applications, but we need to support multiple customers in their intranet, and each one typically requires multiple environments for the application (acceptance, production, etc.). Maintaining dozens of different packages of the AIR application to support all these customer environments clearly is not the solution. Neither we want to force thousands of different users to enter and maintain the correct server location in their local preferences.
So, we thought to use a badge hosted in the back-end application to run the local AIR application: using the underlying API, we could activate the application specifying also the network location of the back-end services. We could also rely on the badge to install the application (and the AIR runtime if necessary)… however, application packaged as native installers cannot be installed, upgraded, or launched by the badge API (and we need to package ours as native to use native processes).
We also noticed that multiple versions of an AIR application cannot be installed side-by-side in a client machine, and that the installation and upgrade of the application can be performed only when the local user has administrative rights on the machine (using standard or native packages), forcing us to rely on external software distribution systems in some customer scenarios (introducing additional complexities in the release cycle).
At this point, in our opinion the standard deployment strategies of Adobe AIR applications are unfit for enterprise environments. In the enterprise world, many of the applications have migrated to a completely browser-based solution, while others enhanced their client layer to comply with the requirements, for example installing only a thin portion of the client code and allowing to connect to multiple server versions/environments with it (e.g. the SAP GUI universal client). Without smarter deployment and distribution tools, AIR applications currently are a step back compared to web applications in terms of manageability.
So, we are trying to develop a solution to address these problems, with some concepts similar to JStart: install on the client machine a launcher application capable of being activated from a web page, dynamically locate, download and run the actual client bytecode, transparently enforce client software updates, and supporting multiple applications (and multiple versions of the same application). However, we are facing many technical problems due to internal architecture of AIR and we already spent a considerable amount of effort trying to find a solution. We are now thinking to return on the choice of AIR, going back to Flex.
What is the position of Adobe on this argument? Is Adobe aware of these issues and are there any plans on this topic? Any advice?
Thank you in advance

For those following along, Oliver Goldman will be answering this post in future articles on his blog.
Many great comments and questions here. I’m working on some follow-up posts to address these; nothing I could cram into this comment field would really do your query justice. - Oliver Goldman
Pursuit of Simplicity
Chris

How to deploy with Oracle 8i, Forms 6i and Reports 6i

We are developing a number of application systems. We have 2 servers. Oracle 8i is installed on one server and other werver is used for network authentication.
We have to now start deploying newly developed applications. We have around 200 users located in various buildings over our campus spread over one kilometer.
What can be different deployment strategies.
Pl. help.
M. Tariq

Mr. Robin
I also need information on the subject. Kindly send me a copy of the presentation when it is ready. Here is my email address: [email protected] Your act will highly be appreciated.
Thanks
Farhan
Muhammad,
A whitepaper on this topic will be produced over the coming months, but isn't available yet.
There will be a presentation on this topic at ODTUG in Las Vegas in June, if you happen to be going. :)
If not, I can send you a copy of the presentation once it is done. You'll need to reply and give your email address.
Regards,
Robin Zimmermann
Forms Product Management

Deployment - best practices

There is a lot of questions/answers about deployment strategies in this forums .
i solved a lot of problems an get answer to my questions
but there are some remaining problems..
My problem :
I developed a project.
There are several mappings, source/target tables, process flows and one main flow combined with a scheduler.
What is the best method/way to deploy the whole project without the OWB client.
With OMB scripts , i can deploy the mappings and process flows...
But how can i define new connections(for example the production connections) ,
how can i deploy the target tables...
how can i configure the new connection to the tables,mappings etc.
how can i deploy the scheduling part en let start it( without the OWB client software).
Thanks a lot..

OMB encompasses pretty much every UI interaction, so you can also deploy tables, create new locations, connectors and schedules can be created.
You can create locations and connectors via OMB
OMBCREATE LOCATION 'X' SET PROPERTIES (TYPE,VERSION,CONNECTION_TYPE) VALUES ('ORACLE_DATABASE','11.2','DATABASE_LINK')
OMBCREATE LOCATION 'Y' SET PROPERTIES (TYPE,VERSION) VALUES ('ORACLE_DATABASE','11.2')
# 1.a. To create a connector and let OWB generate a database link....
OMBCREATE CONNECTOR 'Y/X' SET PROPERTIES (DATABASE_LINK_NAME) VALUES ('LINKNAMEHERE') SET REF LOCATION 'X'
# 1.b. To create a connector that uses an existing database link of yours ....
OMBCREATE CONNECTOR 'Y/X' SET PROPERTIES (DATABASE_LINK_NAME) VALUES ('LINKNAMEHERE') SET REF LOCATION 'X'
# To add the location to a module and configure the module to use the location
OMBALTER ORACLE_MODULE '<modulename>' ADD REFERENCE LOCATION '<locationname>' SET AS DEFAULT
OMBALTER ORACLE_MODULE '<modulename>' SET PROPERTIES (DB_LOCATION) VALUES ('<locationname>')
Schedules can be created as in the link Re: how to properly create a calendar using OMB*Plus, to schedule a workflow ? and then to set the calendar on a flow for example see Problems setting the calendar on a process flow using OMB
Cheers
David

XSQL/XSL deployment on Tomcat question

I have been running my XSQL pages within the default Oracle/Apache/JServ environment. This is where I 'install' my source xsql/xsl files in the htdocs directory of Apache.
I have now recently upgraded my environment so that it now consists of Tomcat 4.x and Apache.
My question is, what deployment strategies are available to me? For example, do I have package my xsql/xsl files into a .war package or can I simply move my xsql/xsl source files into a certain directory very similar to how I use to do before.
Any help greatly appreciated.

I deployed both on Apache (JSP,XSQL) and I have another PC with Apache as Proxy.
It works fine. I dont know the performance when many users try to connect.

Web Services Deployment

Not sure if this is the best forum, but I am looking for guidance on deploying a simple Web Service in eBS r12i.
So basically, we want to have the Web Service available on the Web Server used by the application.
Any help much appreciated

Hi Anil,
Yes, this is a common setup in the field. One of the WebLogic Server Proxy Plug-ins
(i.e. NSAPI plug-in, Apache plug-in, IISAPI plug-in), is typically setup to "proxy"
the web service requests by either path (i.e. using all or a portion of the target
endpoint URL), MIME type (i.e. text/xml for SOAP 1.1 and application/soap+xml
for SOAP 1.2), or a combination of both.
Proxy "by path" and the Apache proxy plug-in are the most commonly chosen configuration
for this.
Refer to the information at the following link for specifics on how to setup the
WebLogic Server Proxy plug-in for Apache:
http://e-docs.bea.com/wls/docs70/plugins/apache.html#123030
Regards,
Mike Wooten
"Anil Kumar" <[email protected]> wrote:
>
What is the deployment strategy for the web services that are running
on WebLogic
7.x that is behind a firewall fronted by a web server in the DMZ? In
other words,
can a web services client (in our case, the client is another WebLogic
Server)
call the web service through the web server? If not, what are the typical
deployment
strategies for web services in a production environment?

Deploy Consumer Grade Windows Laptops On Domain?

We are considering purchasing some low end laptops that will be used for the main purpose of users accessing their primary workstation remotely from home.
HP Stream 14 looks like a candidate.
It comes with 8.1 "home" edition OEM. So, we would need to upgrade to Pro for domain join (so they can use their normal domain user id and password to log in and so we can manage the accounts) either by purchasing Pro Packs for each
laptop or via Volume licensing upgrades. Can VL be used to upgrade 8.1 OEM to 8.1 Pro VL?
Does anyone have experience with managing these types of devices. I'm not sure we would need to bother with creating a corporate image for these laptops. We could just add the Pro Pack, join the domain and then manage settings and install required
software (VPN, disk encryption and managed antivirus) using Group Policy.
PC Reset or factory restore could be used as needed when reassigning to new users or if there is a major software issue.
I assume the Windows keys are embedded so we can reinstall Windows 8.1 without having to keep track of and manually type in software keys after a restore.
Anyone have experience with this type of use case?

Hi,
Regarding the license related issue, we'd better make a contact with the Microsoft local license team for support.
http://support.microsoft.com/contactus/
If we purchased the "Home" edition, then the embedded key should be this edition, if we want to reinstall with Windows 8 professional edition, we need to enter the professional edition license key again.
For Windows 8.1 deployment, here is some information for reference:
Windows 8 Deployment Strategies
Step-by-Step: Windows 8 Deployment for IT Professionals
Best regards
Michael Shao
TechNet Community Support

Web Services Deployment in Oracle9i

I have read several articles on Web Services on TechNet. It is still
not clear to me:
1. If I use Oracle9i EE on HP UNIX 11, do I have everything to deploy
web services. Many articles on web services mention about Oracle9i AS
OC4J containers. Does that mean I need Oracle9i AS (do I need to get a
license for it) or OC4J containers can be downloaded (if not already
available) with Oracle9i EE.
2. Same question for Oracle 10G, do I need Oracle10gAS for deployment.
I know using Oracle Jdeveloper, it is easy to develop web services, but
do I need anything from Developer to deploy a web service,
Thanks a lot.

Hi Anil,
Yes, this is a common setup in the field. One of the WebLogic Server Proxy Plug-ins
(i.e. NSAPI plug-in, Apache plug-in, IISAPI plug-in), is typically setup to "proxy"
the web service requests by either path (i.e. using all or a portion of the target
endpoint URL), MIME type (i.e. text/xml for SOAP 1.1 and application/soap+xml
for SOAP 1.2), or a combination of both.
Proxy "by path" and the Apache proxy plug-in are the most commonly chosen configuration
for this.
Refer to the information at the following link for specifics on how to setup the
WebLogic Server Proxy plug-in for Apache:
http://e-docs.bea.com/wls/docs70/plugins/apache.html#123030
Regards,
Mike Wooten
"Anil Kumar" <[email protected]> wrote:
>
What is the deployment strategy for the web services that are running
on WebLogic
7.x that is behind a firewall fronted by a web server in the DMZ? In
other words,
can a web services client (in our case, the client is another WebLogic
Server)
call the web service through the web server? If not, what are the typical
deployment
strategies for web services in a production environment?

Hot deployment in 8.1 beta

Hi,
If i want my modified ejb/servlet classes to be automatically detected by the
server while it is still running, what is the method to do it?..
I have tried touching the REDEPLOY file and also undeploy/deploy strategies...but
doing so is causing the server to throw exceptions and also the changes are not
being reflected.
I am using weblogic 8.1 beta version on windows2000 and in the development mode.
please help,
seshu

Seshu:
I would suggest upgrading to 8.1 GA.
I would also suggest you check out split-dir and ant for deploy and
redeploy, vs. the applications directory.
http://edocs.bea.com/wls/docs81/programming/packaging.html#1097040
Servlet classes are auto detected and reloaded without requiring a redpeloy
as their hierachy is flat. EJB's require a redeploy.
Cheers
mbg
"Seshu" <[email protected]> wrote in message
news:3efc9056$[email protected]..
>
Hi,
If i want my modified ejb/servlet classes to be automatically detected bythe
server while it is still running, what is the method to do it?..
I have tried touching the REDEPLOY file and also undeploy/deploystrategies...but
doing so is causing the server to throw exceptions and also the changesare not
being reflected.
I am using weblogic 8.1 beta version on windows2000 and in the developmentmode.
>
please help,
seshu

Package PIP Deployment to manage license costs

What deployment strategies have people applied to mitigate the cost of PIPs (core based licensing) e.g. has anyone established a cluster just for the licensed PIP so that they're not paying for more CPU allocation than is necessary; then any custom PIPs go into a separate cluster?
thanks

This particular forum is about general Cloud issues, try the links below
Team license links that may help
-https://helpx.adobe.com/contact/creative-cloud-teams.html for Team help
-http://www.adobe.com/creativecloud/buy/business.html
-team plans https://creative.adobe.com/plans?plan=team
-manage your team account http://forums.adobe.com/thread/1460939?tstart=0
-Team Installer http://forums.adobe.com/thread/1363686?tstart=0

What is the average duration of 1 full SAP life cycle or 1 end-to-end implementation. How long does it take to prepare DEV, QAS and PRD?

What is the average duration of 1 full SAP life cycle or 1 end-to-end implementation. How long does it take to prepare DEV, QAS and PRD in any company?

Anand,
let me start with saying that the question you ask may not help you to determine the duration of your project. As Ryan and others stated the duration of the project is highly dependent on the scope of the solution you are implementing, geographical scope, amount of modifications/enhancements, number of languages, number of users that need to be trained, amount of standard processes customer is able to re-use in the implementation and many other factors (like quality of implementation contractor you will chose and availability of customer and implementors resources). I can probably go on for another couple lines, but I guess you get the idea.
With that out of the way let's talk about some example implementations that will give you an idea - Ryan did great job outlining what I would call traditional approach above. I have couple examples where customers leveraged innovative deployment strategies that are available today. In particular the project teams leveraged pre-packaged services like RDS, World Template or Best Practices as their baseline solution and they built from there. Second acceleration technique customers now leverage is the deployment in the SAP HANA Enterprise Cloud to accelerate the time to initial setup of the system and thus move from traditional blueprinting to scope validation exercise that further shortens the time. There are other acceleration techniques we see applied in some cases like use of iterative implementation of the delta requirements on top of the baseline solution.
Let me offer few examples to illustrate what I explained above:
ERP implementation at Schaidt Innovations with 3 months long deployment of ERP solution using ERP RDS as a baseline (you can view their testimonial here - Schaidt Innovations: SAP ERP on HANA in the cloud - YouTube)
Customer in Asia with global template deployment that leveraged SAP ERP for Manufacturing with deployment to cloud and 9 countries rollout (Japan, Korea, China, Taiwan, Hong Kong, UK, Germany and US). The initial deployment took 4 months for first country and 2 months for rollout into the additional 8 countries - so total of 6 months. The original plan using traditional approach with full blueprint and heavy configuration was estimated to be more than double of the actual deployment time.
There are many other examples where customers follow the assemble-to-order delivery model for their project and gain significant benefits doing so. I suggest you to review some of the recordings we did in 2013 about this approach and if you are member of ASUG review the Agile ASAP sessions we did for ASUG PM SIG.
Link to webinars: SAP A2O Webinar Series Schedule
Let me know if you have any questions.
Jan

Deployment Strategies

Similar Messages

Maybe you are looking for