Subversion Production Environment Setup

Hi Everyone:
We are trying to set up our production environment. We are using Tortoise SVN for our repository. We have 2 servers "devl" and "prod". We have 2 runtime environments, one on each server. Currently we have only one copy of the applications on "devl" in Tortoise SVN.
There has been some discussion lately on whether or not we need to keep a copy of the application in its production state on "prod".
For those of you already in production environments using Tortoise SVN (Subversion), what have you found works best and your reasoning behind it.
Thanks very much in advance.
Mary
UofW

Hi Mary,
This isn't really a JDeveloper question, but relevant nonetheless. Let clarify some issues before answering though.
1. From what I understand you have two server for RUNNING your application, is that right? One is devl for development, integration and acceptation? While the other is prod for production? If so, then your question is not really valid. Normally you keep your repository on a single server (or a more complex topology if you have a really huge development team) that is NOT necessarily (and often not) the same as the runtime servers. This is quite useful for backup purpose, maintainability and scalability among other things.
2. What do you mean by "you already in production environments using Tortoise SVN (Subversion)"? If you mean having a system in production that used SVN as a versioning system, then yes, and it work just like I mentioned above using the branch and tag features of SVN to mark the code when it goes in production and when an experimental feature needs to be developed.
Regards,
~ Simon

Similar Messages

Problem on developing SSRS report in a production environment

Any problem could be caused if have to develop SSRS report in a production environment ?
If so, how it can be prevented?
Thanks!

Hi ,
As per my understanding, Normally our environment setup contains Development,testing,preproduction,production and its varies from company to company.
We develop SSRS report in development environment and after testing we deploy it to production report server.
Development environment use development database for creating report like your database IP and credential will use development environment
setup. and production environment use production database for creating report like your database IP and credential will use production environment setup.
Thanks
Neha Prajapati Please Mark This As Answer or vote for Helpful Post if this helps you to solve your question/problem.

Production Environment RFC's for EWA.... Please help!!

We have some of the production environment setup EWA. I will need to add else which are left. I have setup EWA in sandbox for testing. worked fine. but i have question about RFC's.
My all DEV systems has the following RFC's in solman;
SM_XXXCLNT100_LOGIN
SM_XXXCLNT100_READ
SM_XXXCLNT100_TMW
SM_XXXCLNT100_TRUSTED
But my all QAS and PRODUCTION system has the following RFC'c in solman.
SM_XXXCLNT100_LOGIN
SM_XXXCLNT100_READ
SM_XXXCLNT100_TMW
I thought when I generate auto RFC's from SMSY, it creates the following;
SM_XXXCLNT100_READ
SM_XXXCLNT100_TMW
SM_XXXCLNT100_TRUSTED
What should I do? if it creates _TRUSTED ONE in PRD, should I delete it? Please help!!
Question: If I am generating auto RFC's for PRD, it created _LOGIN one too? I am totaly confused??
Thanks,
I will definitely post points

The only reason I want to do that because I have to talk to security folks for that, they will go and look at the other production environments which dont have _TRUSTED rfc...
Like as I have mentioned, all production has the following rfc's
SM_XXXCLNT100_LOGIN
SM_XXXCLNT100_READ
SM_XXXCLNT100_TMW.
I dont understand only one thing. how can I get _LOGIN rfc?
The only reason I am asking, when I did EWA in sandbox, It did not generate _LOGIN rfc...
Do you have any idea?
Thanks,

How to move Oracle APPS 12 setup data to new APPS 12 production environment

Dear All
I need to know , how we can move Oracle APPS 12 setup data to new APPS 12 production environment?? What is the easy and secure way, we dont want to do the new installation of APPS 12 and re-setup the things....
cheers

Hi,
Can you please explain more regarding to move setup from DEV to PROD instance.The steps are documented in the iSetup manual, so have you gone through the documentation?
Also we would install PROD with multi tier nodes, and HA cluster. So in that case what would be the change to move the setups from DEV to PROD, as DEV is single node TEST APPS 12 installation.iSetup is helpful in moving the functional setup between the two instances. If you want to create an identical copy of your DEV instance to PROD instance (provided that both instances contain no data), then you can use "Rapid Clone" -- See (Note: 799735.1 - Rapid Clone Documentation Resources, Release 11i and 12).
Regards,
Hussein

Development and product environment

Dear all,
I want to setup two databases in seperated server. One for development purpose and another for product environment.
Which good method/tool in oracle can transfer data (like pl/sql,tables,fields) from
development to product environment?
Thanks you

I would strongly suggest cloning the database from Development to Production, using RMAN. You get a proper copy that way - and it isn't hard to do. Howard Rogers has all the answers here: http://www.dizwell.com/prod/node/9

Create a new portlet in Deployed Portal in production environment

are there any ways to import or create a new portlet in Deployed Portal in production environment?
Edited by: user8322798 on May 1, 2011 7:26 AM

This can done via WSRP proxy portlets and streaming desktops. First, you'll need to have a WSRP producer setup somewhere. This could be another WLP webapp with portlets, or another server altogether. Or, you can use the JSR 286 WSRP import tool from within the Portal Administration Console (I think it's under Services | WSRP | Import Tool) -- this will allow you upload .war(s) of JSR 168 or 286 portlets, which will be turned into WSRP producer(s).
Then, you can use the Portal Administration Console to register a WSRP Producer, and then add portlets from the producer to your desktop (http://download.oracle.com/docs/cd/E15919_01/wlp.1032/e14235/chap_fed_books_pages.htm#FPGWP690). Additionally, once the producer has been registered in Portal Adminstration Console, an adminstrator user can use the Dynamic Visitor Tools from within the streaming desktop itself to add wsrp proxy portlets to the desktop (http://download.oracle.com/docs/cd/E15919_01/wlp.1032/e14243/dvt.htm#PDGWP691).
It is not possible to add new local .portlet files to a deployed application in production mode. This requires adding the file artifacts to the .ear/.war and redeploy the application.
Greg

Best practice for a deplomyent (EAR containing WAR/EJB) in a productive environment

Hi there,
I'm looking for some hints regarding to the best practice deployment in a productive
environment (currently we are not using a WLS-cluster);
We are using ANT for buildung, packaging and (dynamic) deployment (via weblogic.Deployer)
on the development environment and this works fine (in the meantime);
For my point of view, I would like to prefere this kind of Deploment not only
for the development, also for the productive system.
But I found some hints in some books, and this guys prefere the static deployment
for the p-system.
My question now:
Could anybody provide me with some links to some whitepapers regarding best practice
for a deployment into a p-system ??
What is your experiance with the new two-phase-deploment coming up with WLS 7.0
Is it really a good idea to use the static deployment (what is the advantage of
this kind of deployment ???
THX in advanced
-Martin

Hi Siva,
What best practise are you looking for ? If you can be specific on your question we could provide appropriate response.
From my basis experience some of the best practices.
1) Productive landscape should have high availability to business. For this you may setup DR or HA or both.
2) It should have backup configured for which restore has been already tested
3) It should have all the monitoring setup viz application, OS and DB
4) Productive client should not be modifiable
5) Users in Production landscape should have appropriate authorization based on SOD. There should not be any SOD conflicts
6) Transport to Production should be highly controlled. Any transport to Production should be moved only with appropriate Change Board approvals.
7) Relevant Database and OS security parameters should be tested before golive and enabled
8) Pre-Golive , Post Golive should have been performed on Production system
9) EWA should be configured atleast for Production system
10) Production system availability using DR should have been tested
Hope this helps.
Regards,
Deepak Kori

Best Practice for Production environment

Hello everyone,
can someone share the best practice for a production environment? or is there a SAP standard best practice to follow in a Production landscape?
i understand there are Best practices available for Implementation , Migration and upgrade. But, i was unable to find one for productive landscape
thanks.

Hi Siva,
What best practise are you looking for ? If you can be specific on your question we could provide appropriate response.
From my basis experience some of the best practices.
1) Productive landscape should have high availability to business. For this you may setup DR or HA or both.
2) It should have backup configured for which restore has been already tested
3) It should have all the monitoring setup viz application, OS and DB
4) Productive client should not be modifiable
5) Users in Production landscape should have appropriate authorization based on SOD. There should not be any SOD conflicts
6) Transport to Production should be highly controlled. Any transport to Production should be moved only with appropriate Change Board approvals.
7) Relevant Database and OS security parameters should be tested before golive and enabled
8) Pre-Golive , Post Golive should have been performed on Production system
9) EWA should be configured atleast for Production system
10) Production system availability using DR should have been tested
Hope this helps.
Regards,
Deepak Kori

OBIEE Production Environment - Should it be made Private or Public?

I am interested to know whats the best practice for OBIEE Production environment's firewall setup? I feel it should be behind the firewall on private space, but i am having to convince my networking folks to make it private instead of public? But i dont know if this opens a different set of issues. In reality, OBI PRD should only be accessed by internal staff and not outsiders.
Could someone provide any supporting documentation related to this topic?
Thanks!

See this PDF:
http://www.peakindicators.com/media_pi/BI+EE+Architectures+and+Sizing.pdf
The safest deployment would be to have the BI Server in your intranet, your Presentation Services Plug-In in the DMZ and a firewall between the two.

RE: Production Environment Definition

Brad,
We use connected environments so that we do not have a single point of
failure.
We use multiple environments and connect them together in a star topology
for reliability of service. Our servers (23 in total) sit out at branches
in the back of beyond and the WAN connections between the servers are
unreliable. One needs a reliable connection to the Name Service which sits
on each Environment Manager. We have thus created 23 connected
environments with an Environment Manager on each LAN. Connected
environments are still a bit buggy but Tech Support is currently working on
fixing the last of the problems. We are still on ver 2H15 for this reason.
Disadvantages of this topology are that making distributions take a long
time because referenced partitioning cannot be scripted in fscript and
econsole only connects to one environment at a time.
There is a Forté consultant in Denver called Pieter Pretorius who has had a
lot of experience with our connected environments. It may be worth
chatting to him.
Regards,
Richard Stobart
Technical Consultant for Forté
E-mail [email protected]
Quick-mail: [email protected]
Voice: (+ 27 83) 269 1942
(+27 11) 456 2238
Fax: (+ 27 83) 8269 1942
-----Original Message-----
From: Brad Wells [SMTP:[email protected]]
Sent: Tuesday, February 10, 1998 11:52 PM
To: 'Forte Users - Sage'
Subject: Production Environment Definition
Hello again,
We are just starting to look at what it will take to setup a production
Forte environment. I have some general questions regarding
considerations that may affect the environment definition and thought
maybe some of the more experienced users could share some thoughts on the
following:
1) What factors lead to the creation of multiple production environments?
a. How many environments should you use in a production situation?
b. Do people create separate environments for separate business units?
c. Are there performance improvements to be had by restricting the
number of server and client nodes included in a single environment?
d. How do the performance benefits of multiple environments compare to
the additional complexity of managing and maintaining multiple connected
environments?
The initial need is for an environment that will service approximately 50
clients and contain a couple of server nodes (database and service
related). However, as the environment grows, it could easily grow to a
size of 600 clients encompassing approximately 15-20 server nodes.
At this point in time, there is no need for the failover support of
connected environments, but this is something we will need to add as the
environment absorbs applications with high reliability needs. Should the
environments be setup and connected right away or can this be easily
added on an "as needed" basis? What other recommendations would you
make?
Has anyone taken advantage of Forte consulting services in defining the
production environment? Where you satisfied with the results of the
service?
Thanks.
Bradley Wells
[email protected]
Strong Capital Management, Inc
http://www.strong-funds.com

On Tue, 10 Feb 98 13:52:00 PST Brad Wells <[email protected]>
writes:
At this point in time, there is no need for the failover support of
connected environments, but this is something we will need to add as
the
environment absorbs applications with high reliability needs. Should
the
environments be setup and connected right away or can this be easily
added on an "as needed" basis? What other recommendations would you
make?
From the Forte Systems Management point of view, you can add them "asneeded"
fairly easily.
Now from the application source code point of view, implementing
Fail/Over support
is a different story... You will need to check your SO's dialog
durations, handle
DistributedAccessExceptions, "warm-up" your distributed references for
F/O,
design a solution for restoring global transient data, do lots of
testings etc...
So implementing Fail/Over is not only related to systems-management
issues, it can
have some influence on your application(s) source code.
Hope this helps,
Vincent Figari
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com
Or call Juno at (800) 654-JUNO [654-5866]

Production Environment Definition

Hello again,
We are just starting to look at what it will take to setup a production
Forte environment. I have some general questions regarding
considerations that may affect the environment definition and thought
maybe some of the more experienced users could share some thoughts on the
following:
1) What factors lead to the creation of multiple production environments?
a. How many environments should you use in a production situation?
b. Do people create separate environments for separate business units?
c. Are there performance improvements to be had by restricting the
number of server and client nodes included in a single environment?
d. How do the performance benefits of multiple environments compare to
the additional complexity of managing and maintaining multiple connected
environments?
The initial need is for an environment that will service approximately 50
clients and contain a couple of server nodes (database and service
related). However, as the environment grows, it could easily grow to a
size of 600 clients encompassing approximately 15-20 server nodes.
At this point in time, there is no need for the failover support of
connected environments, but this is something we will need to add as the
environment absorbs applications with high reliability needs. Should the
environments be setup and connected right away or can this be easily
added on an "as needed" basis? What other recommendations would you
make?
Has anyone taken advantage of Forte consulting services in defining the
production environment? Where you satisfied with the results of the
service?
Thanks.
Bradley Wells
[email protected]
Strong Capital Management, Inc
http://www.strong-funds.com

On Tue, 10 Feb 98 13:52:00 PST Brad Wells <[email protected]>
writes:
At this point in time, there is no need for the failover support of
connected environments, but this is something we will need to add as
the
environment absorbs applications with high reliability needs. Should
the
environments be setup and connected right away or can this be easily
added on an "as needed" basis? What other recommendations would you
make?
From the Forte Systems Management point of view, you can add them "asneeded"
fairly easily.
Now from the application source code point of view, implementing
Fail/Over support
is a different story... You will need to check your SO's dialog
durations, handle
DistributedAccessExceptions, "warm-up" your distributed references for
F/O,
design a solution for restoring global transient data, do lots of
testings etc...
So implementing Fail/Over is not only related to systems-management
issues, it can
have some influence on your application(s) source code.
Hope this helps,
Vincent Figari
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com
Or call Juno at (800) 654-JUNO [654-5866]

ORACLE NOSQL INSTALLATION ON PRODUCTION ENVIRONMENT

Hi ,
I have already installed nosql in my test server using kvlite. My doubt is how to setup ORACLE NoSQL on production environment ?
Please suggest .
Thanks
Edited by: 861012 on Sep 3, 2012 12:54 PM

Hi Kamran,
I am using doc - http://docs.oracle.com/cd/NOSQL/html/AdminGuide/Oracle-NoSQLDB-Admin.pdf
Here on page-26 while "Create the Remainder of your Storage Nodes" i am getting following error -
kv-> plan -execute -name "Deploy n02" deploy-sn 1 node02 5000
Exception while executing command plan: Oracle NoSQL DB 11gR2.1.2.123 oracle.kv.impl.fault.OperationFaultException: Plan 9[Deploy n02] finished in state ERROR. Problem during plan execution: Exception creating connection to: node02; nested exception is:
java.net.NoRouteToHostException: No route to host
kv->
I have already configure iptables to allow network traffic to port 5000. Still i am getting this error java.net.NoRouteToHostException: No route to host
Please suggest how to resolve this.
Thanks
Edited by: 861012 on Sep 4, 2012 3:42 PM

Oracle Installation for Production Environment.

Hi All,
We need to install Oracle in our production environment.
But since there is no DBA in our project, we need to do it by ourself.
I was just wondering what all steps and cautions I need to take to install it.
I was told just double click on Setup.exe :-) and that would suffice.
I am pretty sure its not that easy, atleast for a production environment.
We might need to set some params, may be.
We are at present using Oracle 10g Rel 1.
Any help/suggestion would be highly appreciated.
Thanks in Advance,
Tanuja

Well, it does more complicate than a double click of setup.exe, especially for a production database.
It's not only about the installation, also think about how do you want to create your database, the storage configuration, database configuration, and backup/recover strategy etc.
For installation, make sure you follow Oracle installation guide,
http://download.oracle.com/docs/html/B10130_02/toc.htm
And there are many other document here
http://www.oracle.com/pls/db10g/portal.portal_demo3?selected=1

IPM 11 g production environment set up query.

Hi,
We need to install IPM 11g. For Production environment we want individual managed server wiz. soa_server1, UCM_server1 and IPM_server1 to be installed on different machines. However such an approach is not discussed in any of the documents of ecm. So my query here is whether such an approach is possible or not & if it's possible then which document mentions so. Do i need to to follow weblogic admin guide?

Hi Nico,
if you want a local test/development setup of Oracle why don't you just install Oracle 11gR2 XE (http://www.oracle.com/technetwork/products/express-edition/downloads/index.html) ?
If you install this you get a database, APEX (4.1), client etc all in one install, this includes a webserver (EPG) on port 8080 without having to configure anything. It's a simple next-next-next installation without much configuration.
If you would like to seperate database and software you can always do this later when you understand the concepts of database/control files etc.
If you would like to upgrade to APEX 4.2 you can download this afterwards and easily install this by running two scripts in SQL*Plus ( apexins.sql and apxldimg.sql ), just check the apex 4.2 installtion guid section EPG for this.
Regards
Bas
b.t.w. If you're running windows 7 - 64 bits just use the 32 bits XE for windows, might get some warnings but you should be able to install and run, good enough for test/dev

What authorizations to give to developers in the production environment

Hi,
We have setup our development PI 7.1 environment and are now ready to setup production. Can someone point me in the right direction for determining which authorizations need to be given to the PI developers in the production environment?
Do they have to be the same or is there some other set of roles/authorizations for a production environment?
Any help is greatly appreciated.
Best Regards,
Rick

Hi Rick,
Precisely for configuration XI have separate role: SAP_XI_CONFIGURATOR which is used to configure interfaces in ID. But again this is role provided to very selective people (usually Application Support team) because you need to share some sensitive user/password etc for different systems (SAP/Non-SAP).
We used following roles combinations:
- Dev system
Developers = SAP_XI_DEVELOPER, SAP_XI_CONFIGURATOR, SAP_XI_MONITOR, SAP_XI_BPE* ,
TechLead = Developer + SAP_XI_ADMINISTRATOR
- QA System
Developer = SAP_XI_CONFIGURATOR, SAP_XI_MONITOR, SAP_XI_BPE_MONITOR
TechLead = Developer (in special cases SAP_XI_ADMINISTRATOR)
- PROD System
Developer = SAP_XI_MONITOR, SAP_XI_BPE_MONITOR, (None for Configuration If I have separate team for configuration).
TechLead = Developer + SAP_XI_CONFIGURATOR
It is best practise to keep separate team for configuration on Prod system because of sensitivity of information. Even on PROD system you need to modify SAP_XI_MONITOR role to disallow monitoring of payload because of data sensitivity (HR, Finance data etc).
Regards,
Gourav

Subversion Production Environment Setup

Similar Messages

Maybe you are looking for