Best practice - Production deployment

what is the best practice to deploy custom built application in production?
Where to deploy in Admnistration server or in manged server?
Thanks,
Shankar

Hi Shankar ,
It is always better to deploy your application in the Managed Server. You do not need to restart your admin server while you need to restart your managed server for changing your environment related to your application. Admin Server is meant for administering all the managed server instances. You can have many different managed servers for different specific applications. So it is a best practise to deploy your application in the managed server.
Regards,
Ilaya

Similar Messages

Best practices for deployment from Dev /Staging /Production in SharePoint ?

Hi All,
What is a best practices to deploy SharePoint Portal to dev / staging / Production.
I have custom solution deployed using WSP file. But I have done some changes using sharepoint designer.
Like as Designer workflow, master pages etc.
How can I deploy my document libraries and list to dev to prod using best practices?
Thanks
Balaji More

Hi,
According to your post, my understanding is that you wanted to know the best practices to deploy SharePoint Portal in different SharePoint environment.
If the site is not existing in the production server, we can save the site from the development server, and then import it to the production server.
But if the site is already existing in the production server, we should follow these steps to just add the taxonomy and content types to the production server:
Save the site from Dev as a template
Import the template as solution in Visual Studio
Remove unnecessary items from the solution(Please pay more attention on it. If a content type/list... in the solution is existing in the production site too, it will replace the
same object existing in the production after deployment)
Package the solution
Deploy the solution in the production
For more detailed, please see:
http://ahmedmadany.wordpress.com/2012/12/30/importing-sharepoint-solution-package-wsp-into-visual-studio-2010/
There is a similar thread for your reference.
http://social.technet.microsoft.com/Forums/en-US/7dcf61a8-1af2-4f83-a04c-ff6c439e8268/best-practices-guide-for-deploying-sharepoint-2010-from-dev-to-test-to-production?forum=sharepointgeneralprevious
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

Best Practice for Deploying ADF application

I am tasked with developing a best or prefered practice of feploying a large ADF application. Background: we are in the process of redeveloping a UI for a large system. We have broken the system down into susbsytems. Each of these susbsystems UI will be a ADF aaplicaion(?). This is a move from a MS .Net front end. The backend (Batch processes etc) is being dveloped in Java. So my question is if I have several ADF projects for each subsystem and common components that they all will use - what is the best practice to compile package and deploy? The deployment will be to weblogic server or servers(Cluster).
We have a team of at least 40 -50 developers worldwide so we are looking for an automated build and deploy and would like to follow Oracle best practice. So far I have read Deploying ADF Applications (http://download.oracle.com/docs/cd/E15523_01/web.1111/e15470/deploy.htm#BGBJHGFH) and have followed the links. I have also look at the ADF evangalist blogs - lots of chatter about ojdeploy. My concern about ojdeploy is that dependent files are also being compiled at the same time. I expected that we want shared dependent files compiled only once (Is that a valid concern)?
So then when we build the source out of subversion (ojdeploy ? Ant? ) then what is best practice to deploy to a weblogic server (wslt admin console) - again we want it to be automated.
Thank you in advance for replies.
RK

Rule 1: Never use the "Automatically Expose UI Componentes in a New Managed Bean" option, create your bindings manually;
Rule 2: Rule 1 is always right;
Rule 3: In doubts, refer to rule 2.
You may also want to check out :
http://groups.google.com/group/adf-methodology
And :
http://www.oracle.com/technology/products/jdev/collateral/4gl/papers/Introduction_Best_Practices.pdf

Best practices for deploying EMGrid Control

Can i use one db for OEM & RMAN repository? Looking for Best practices for deploying EMGrid Control in our environment, I have experience working with EMGrid control it was very slow , how to make it fast ? Like i enjoy the speed of EMDBControl....

DBA2008 wrote:
Is this good idea to put RPM recovery catalog & OID schema in OEM Repository DB? I am thinking just to consolidate all these schema's in one db.Unless you are really starved for resources, I would not recommend storing the OID and OEM repositories in the same database. Both of these repositories support different products, and you risk creating unnecessary dependencies when patching or upgrading. As a completely fictitious example, what if your OID installation has a critical issue that requires a repository database upgrade to version 10.2.0.6, and the Grid Control repository database is only certified for version 10.2.0.5?
Regards,
John P.
http://only4left.jpiwowar.com

Best practice to Deployment Oracle WebCenter Suite for enterpsie

I have a lead with enterprise client; and we need to proposed to this client best practice to deploy high availability on cluster environment contains the following components:
- oracle web center content: it will used for WebCenter portal (spaces) repository for x-trantent portal as well as it will used to build internet website using WCM
- oracle WebCenter portal; to build x-intranet portal
- oracle access manager for single sign on authentication
- oracle web tier for HTTP server and web cache.
i reviewed the enterprise deployment "http://docs.oracle.com/cd/E23943_01/core.1111/e12037/intro.htm" and contains rich information on the configuration.
However; my question is could you provide us a best practice to deploy above components on a high availability cluster environment "on a Linux environment prefared" to support and tested around 20k users? By the way client already had oracle exadata 11g server and it will used for this deployment.

AW,
One way is creating EJBs.Please refer to the threads below for that
https://forums.sdn.sap.com/click.jspa?searchID=2936002&messageID=1082087
You can create a javabean and you can import that as a model .
Check the following project which will generate javabean (MaX DB)
https://www.sdn.sap.com/irj/sdn/softwaredownload?download=/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/business_packages/a1-8-4/simple_javabean_generator_project.zip
This project will generate a javaben out of the tables in MAXDB.
You can follow any one of the above.
Regards,Anilkumar

What is best practice for deploying agent(10204) on RAC 9i

Hello,
What would be best practice for deploying agent(10204) on RAC 9i? Should the agent be deployed on each node or should the agent be deployed on the cluster file system? What are the advantages/disavantages deploy on individual nodes vs. on cluster file system? Please advice. Thank you in advance.

Please use agent push application to deploy agent on all the nodes at one shot
Please refer the obe
http://www.oracle.com/technology/obe/obe10gemgc_10203/agentpush/agentpush.htm

What is the best practice to deploy the SharePoint site from test to production environment?

We are beginning to start a new SharePoint 2010 and 2013 development projects, soon developing new features, lists, workflows, customizations to the SharePoint site, customization to list forms and would like to put good practice (that will help in deployment)
in place before going ahead with development.
What is the best way to go about deploying my site from Development to Production?
I am using Visual Studio 2012 and also have Designer 2013...
I have already read that this can be done through powershell, also through visual studio and also via designer. But at this point I am confused as to which are best practices specifically for lists, configurations; workflows; site customizations; Visual studio
development features; customization to list forms etc. You can also provide me reference to links/ebook covering this topic.
Thanks in advance for any help.

Hi Nachiket,
You can follow below approach where the environments has been built in similar fashion
http://thesharepointfarm.com/sharepoint-test-environments/
if you have less data then you can use http://spdeploymentwizard.codeplex.com/
http://social.technet.microsoft.com/Forums/sharepoint/en-US/b0bdb2ec-4005-441a-a233-7194e4fef7f7/best-way-to-replicate-production-sitecolletion-to-test-environment?forum=sharepointadminprevious
For custom solutions like workflows etc you can always build the WSP packages and deploy across the environments using powershell scripts.
Hope this helps.
My Blog- http://www.sharepoint-journey.com|
If a post answers your question, please click Mark As Answer on that post and Vote as Helpful
Hi, can you answer me specifically with regards to the foll:-
lists
configurations
workflows
site customizations like changes to css/masterpage
Visual studio webparts
customization to list forms
Thanks.

Best practice for deploying the license server

Was wondering if there is a best practice guideline or a rule of thumb out there for deploying the license server. For instance, is it better to have one license server and all your products connect to that, dev, QA, prod. Or is it better to have a license server for each deployment, i.e. one for dev one for QA.. etc.

Was wondering if there is a best practice guideline or a rule of thumb out there for deploying the license server. For instance, is it better to have one license server and all your products connect to that, dev, QA, prod. Or is it better to have a license server for each deployment, i.e. one for dev one for QA.. etc.

Best practice to deploy some secret credentials in AIR app

Hi,
Can someone suggest the best practice way to deploy some
secret credentials in an AIR app please?
For example, network connection settings or passwords ?
In my particular case (and since this is only for testing)
I'd like to deploy a password in an AIR app. So is there any way to
effectively deploy an encrypted store with the app ? (hope that
makes sense!)
Tks,
Alex

I think the best practice is not to do it. You can't deploy
an encrypted local
store file to another computer. You could encrypt the
information some other
way, but that just moves the problem. If you have a server,
you could have the
app connect to the server to get the sensitive information
and put it into the
ELS (ideally through HTTPS).

Best practices for deploying forms in a 'cluster'?

Anyone know of any public docs that discuss typical best practices for
- forms deployment;
- forms apps management and version control; and/or
- deploying (and keeping) the .frm/frx in sync when using multiple forms servers in a HA or load balancing envrionment?

Hi adil,
Based on your description, you want to know the best practices for search service in a SharePoint farm.
Different farms have different search topologies, for the best search performance, I recommend that you follow the guidance for small, medium, and large farms.
The article is about the guidance for different farms.
Search service can run with other services in the same server, if condition permits and you want to have better performance for search service and other services including BI performance, you can deploy search service in dedicated server.
If condition permits, I recommend combining a query component with a front-end Web server to avoid putting crawl components and query components on the same serve.
In your SharePoint farm, you can deploy the query components in a WFE server and the crawl components in an application server.
The articles below describe the best practices for enterprise search.
https://technet.microsoft.com/en-us/library/cc850696(v=office.14).aspx
https://technet.microsoft.com/en-us/library/cc560988(v=office.14).aspx
Best regards
Sara Fan
TechNet Community Support

What is best practice to deploy webpart into 1. Solutions Galary, 2. GAC, 3. BIN?

I am trying various ways to deploy webpart. Can you please provide me best practice methods to deploy webpart into:-
Case 1. Solutions Galary: ?
Case 2. GAC: ?
Case 3. BIN: ?

That is going to depend on what is in the web part...
There are "apps", "sandboxed solutions" (becoming deprecated in 2013), "Farm Solutions" if you have dlls that need to be deployed to the gac.
Apps - More for javascript (or if you have server side code that you want to run on a server that is not in sharepoint
sandboxed solutions - run in the context of a site, but cannot add dll to gac (or consume certain dlls such as system.web, etc...) so anything that you want to do outside the context of the current site collection is not allowed
Farm Solution - allows you to deploy .Net code to the GAC. Would package as a wsp and give it to an admin to install (requires app pool resets and/or iis resets).

Best Practices for deployment of Oracle 10g database.

Hello ,
Is anyone aware of a whitepaper/ document that talks about best pratices in deploying a database on Oracle 10g and configuration of the database to utilize all the features available in 10g ( eg. ADDM , reports setup etc )
Thanking you in Advance.
Cheers..rCube

Appreciate the input Jaffer. Thanks.
However I was referring to a Best Practices whitepaper like the one existing for Data Guard & MAA available at the follwogng url : - http://www.oracle.com/technology/deploy/availability/htdocs/maa.htm
Is there something available along the same lines ?
Cheers..rCube

Best Practice for deploying in Production Cluster

          I have the following.
          2 Physical machines each running 2 jvm's, thus I have 4 jvm's in my cluster.
          We access the jvm's via an IIS plug-in.
          When it comes time to do a new .war file migration, do you need to stop the jvm's
          first ?
          I have tried deploying with the jvm's live, it technically worked but we then
          noticed several 404 errors during the day on a servlet that was there. (Called
          successfully around the 404)
          Anyway, I'm just looking for recomendations on how others deploy to production.
          Tim


          Tim wrote:
          > I have the following.
          >
          > 2 Physical machines each running 2 jvm's, thus I have 4 jvm's in my cluster.
          >
          > We access the jvm's via an IIS plug-in.
          >
          > When it comes time to do a new .war file migration, do you need to stop the jvm's
          > first ?
          You should be able to redeploy a web application without any
          problems? When you get this 404 errors, do you see any stacktrace
          on the server window
          Kumar
          >
          >
          > I have tried deploying with the jvm's live, it technically worked but we then
          > noticed several 404 errors during the day on a servlet that was there. (Called
          > successfully around the 404)
          >
          > Anyway, I'm just looking for recomendations on how others deploy to production.
          >
          > Tim

Best Practice when deploying a single mdb into a cluster

At a high level, we are converting all of our components to Weblogic processes that use Stateless Session Beans and Message Driven Beans. All of the weblogic processes will be clustered, and all of the topic queues will be distributed (Uniform Distributed Topics / Queues).
          We have one component that is a single MDB reading from a single queue on 1 machine. It is a requirement that the JMS messages on that queue be processed in order, and the processing of messages frequently requires that the same row in the DB be updated. Does anyone have any thoughts on the best design for that in our clustered environment?
          One possible solution we have come up with (not working):
          Possible Solution 1: Use a distributed topic and enforce a single client via client-id on the connection factory, causing a single consumer.
          1.Deploy a uniform-distributed Topic to the cluster.
          2.Create a connection factory with a client-id.
          3.Deploy a single FooMDB to the cluster.
          Problem with Solution 1: WL allows multiple consumers on Topic with same client-id
          1.Start (2) servers in cluster
          2.FooMDB running on Server_A connects to Topic
          3.FooMDB running on Server_B fails with unique id exception (yeah).
          4.Send messages - Messages are processed only once by FooMDB on Server_A (yeah).
          5.Stop Server_A.
          6.FooMDB running on Server_B connects automatically to Topic.
          7.Send messages - Messages are processed by FooMDB on Server_B (yeah).
          8.Start Server_A
          9.FooMDB successfully connects to Topic, even though FooMDB on Server_B is already connected (bad). Is this a WL bug or our config bug??
          10.Send messages - Messages are processed by both FooMDB on Server_A and Server_B (bad). Is this a WL bug or our config bug??
          Conclusion: Does anyone have any thoughts on the best design for that in our clustered environment? and if the above solution is doable, what mistake might we have made?
          Thank you in advance for your help!
          kb

Thanks for the helpful info Tom.
          Kevin - It seems that for both the MDB, and the JMS provider, there are (manual or scripted) actions to be taken during any failure event + failure probes possibly required to launch these actions...?
          In the case of the JMS provider, the JMS destination needs to be migrated in the event of managed-server or host failure; if this host is the one that also runs the Admin server then the Admin server also needs to be restarted on a new host too, in order that it can become available to receive the migration instructions and thus update the config of the managed server which is to be newly targetted to serve the JMS destination.
          In the case of the MDB, a deployment action of some sort would need to take place on another managed-server, in the event of a failure of the managed server or the host, where the original MDB had been initally deployed.
          The JMS Destination migration actions can be totally avoided by the use of another JMS implementation which has a design philosophy of "failover" built into it (for example, Tibco EMS has totally automatic JMS failover features) and could be accessed gracefully by using Weblogic foreign JMS. The sinlge MDB deployed on one of the Weblogic managed servers in the cluster would still need some kind of (possibly scripted) redeployment action, and on top of this, there would need to be some kind of health check process to establish if this re-deployment action was actually required to be launched. It is possible that the logic and actions required just to establish the true functional health of this MDB could themsevles be as difficult as the original design requirement :-)
          All of this suggests that for the given requirement; the BEA environment is not well suited; and if no other environment or JMS provider is available at your site, then a manipulation of process itself may be required to enable it to be handled in a highly-available way which can be gracefully administered in a Weblogic cluster.
          We have not discussed the message payload design and the reasons that message order must be respected - by changing the message payload design and possibly adding additional data, this requirement "can", "in certain circumstances", be avoided.
          If you can't do that, I suggest you buy a 2 node Sun Cluster with shared HA storage and use this to monitor a simple JMS client java program that periodically checks for items on the Queue. The Tibco EMS servers could also be configured on this platform and give totally automatic failover protection for both process and host failure scenarios. With the spare money we can go to the pub.
          P.S. I don't work for Tibco or Sun and am a BIG Weblogic fan :-)

Best practices for deploying common object services

Hi,
Our team has broken out from our main application around 10 services that largely are used to return objects from 10 common tables in the database. We are thinking that these services should be reusable amongst the 5 or so applications that we are going to have in the near future. We're now trying to decide what the best way to make these common services available to the applications is and after considering several ideas, these are the options we've come up with:
1. Putting jars for all of the services in each application and adding entries to the sessions.xml for any Toplink project mappings that are in the jar files. Also are considering having just one many services jar.
2. Exposing the services through web services and only giving the client apps the client side code to invoke the web service. Realize this may mean a performance hit, but would mean less code on the client.
3. Stateless session EJB's.
4. parent-application tag or some other way to make these jar's be available to all applications on the app server through classloading
5. Some sort of messaging service
Would appreciate some input on this, as this seems like it would be a fairly common problem.
Thanks,
Mark

DBA2008 wrote:
Is this good idea to put RPM recovery catalog & OID schema in OEM Repository DB? I am thinking just to consolidate all these schema's in one db.Unless you are really starved for resources, I would not recommend storing the OID and OEM repositories in the same database. Both of these repositories support different products, and you risk creating unnecessary dependencies when patching or upgrading. As a completely fictitious example, what if your OID installation has a critical issue that requires a repository database upgrade to version 10.2.0.6, and the Grid Control repository database is only certified for version 10.2.0.5?
Regards,
John P.
http://only4left.jpiwowar.com

Best practice - Production deployment

Similar Messages

Maybe you are looking for