Deploy in production environment

Hi,
I have to deploy a bpel client application in OracleAS 10.1.3 in production environment. In bpel_services.properties and wf_client_config.xml there are informations unknown to the developer. The deployer knows this information but he doesn't want to modify the ear file.
Is it possible to configure the informations in this files during deploy without modify the ear file ?
Thanks

Thanks a lot!
So it seems that .rpd file IS NOT portable between environments, but it is possible to change params via scripting.
It is surely better than changing via interface, though not ideal.
Any other idea around?
Edited by: user10676624 on 19-dic-2008 1.13

Similar Messages

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

Deploying jsp into testing/staging/developement/production environment

Hi,
I have a jsp, say header.jsp. It has,say 2links. All these links have different URL's based on the environment this jsp is deployed.
Snippet of JSP deployed for Test enviroment:
test_env=hostname:portnumber
contextroot=webappln
        <TD><A href="https://test_env/webappln/querystring">products</A></TD>
        <TD><A href="https://test_env/webappln/querystring">services</A></TD>
        prod_env=hostname:portnumber
contextroot=webappln
Snippet of JSP deployed for Production enviroment:
        <TD><A href="https://prod_env/webappln/querystring">products</A></TD>
        <TD><A href="https://prod_env/webappln/querystring">services</A></TD>
        Problem: For system testing, we need to deploy the code in test/staging and developement servers before it goes into production. Right now i have only one JSP. If i follow my lame procedure, i have to create 3 JSP's for each environement and deploy it in three diff env.Is there a better way?. How to eliminate the duplicate and redundant code in jsp. If the URL's change, need to change at 3 places.Its a big maintenece mess too.
Insted of making three different jsp's for each environment, i want to use single jsp and dynamically figure out the enviroment and generate the urls appropriately. That way we need to maintain only one JSP. No matter where its deployed(test/stage/dev) the URL's are dynamically generated.
Snippet of JSP which dynamically generate web resource URL's based on the Env
        //Determine the environment type
        //Generate URL's with proper hostname, port # and context root and set place holder
       <TD><A href="https://{place holder}/querystring">products</A></TD>
       <TD><A href="https://{place holder}/querystring">services</A></TD>
        Any pointers of how to implement the above case. Any help greatly appreciated.
Thanks,
DHM

Check the action part of the html form tag. On problem I see is in the dev environment you had file.jsp under /jsp but in the production you have it under /dir. This could just be a typo.

SOA OSB Deployment best practices in Production environment.

Hi All
I just wanted to know the best practices followed in production environment for deploying OSB and SOA Code. As you are aware that both require libraries from either (Jdev or SOA Suite) and (OEPE and OSB)? Should one rip the libraries and package them with the ANT scripts (I am not sure but SOA would require its internal ANT scripts and lot of libraries to be bundled, OSB requires only a few OEPE and OSB libraries) or we simply use the below:
1) Use the production run time (SOA Server and OSB Server) to build and deploy the code. OEPE would not be present here, so we would just have to deploy the already created sbconfig.jar (We would build this in a local environment where OEPE and OSB would be installed). The code is checked out from a repository and transferred to this linux machine.
2) Use a windows machine (which has access to prod environment) and have Jdeveloper, OEPE and OSB installed to build\deploy the code to production server. The code is checked out from a repository.
Please let us know your personal experiences with the deployment in PROD. Thanks a lot!

There are two approaches for deployment of OSB and SOA code.
1. Use a machine specifically for build and deployment which will have access to all production environments (where deployment needs to be done). Install all the required software (oepe, OSB etc..) and use remote deployment for deploying the code.
2. Bundle all the build and deployment related libraries and ship them as a deployment package on the target server and proceed with the deployment.
Most commonly followed approach is approach#1.
Regards
Vivek

Deploying AIA 11g composites in Production Environment

Hi all,
I am facing one trouble in deploying AIA11g composites in Production Environment. I know how to deploy codes on a usual server but in case of Production we require a single bundle containing say 100 composites for services developed.
Scenario:
Bundle all AIA composites developed into one single deliverable which can be deployed directly.
Things known or tried:
1. Deployment Plans will deploy codes to server manually which will mean that our codes have to be present on remote location so as to deploy them.
questions:
2. How can we archive MDS data (containing AIA design artifacts) and publish it in MDS.
3. Composites Such as EBS\Requester ABCS contains concrete urls so how can we make sure that they are overriden once we deploy it on Production Server with that server hostname:port.
Regards,
ankit

For publishing the changes to MDS, follow the steps -
1) Source the environment by running aiaenv.sh
2) Update UpdateMetaDataDP.xml at <AIA_INSTANCE_HOME>/config with the entries of the documents to be published.
Here is an example of entry for AIAConfigurationProperties.xml -
<fileset dir="AIA_HOME/aia_instances/INSTANCE_NAME/AIAMetaData">
<include name="config/AIAConfigurationProperties.xml" />
Make sure to create different fileset dir tag for each entry, else the documents will not be published to MDS.
3) Access the $AIA_HOME/Infrastructure/Install/config folder.
4) Execute the following command:
ant -f UpdateMetaData.xml
Hope it helps!

Deployment from DEV to Production environment

Hi,
What are the best possible ways to deploy the visual web parts and Pages from development environment to Production environment.
As I am very much new to Sharepoint, I would like to have the safest methods to do the deployment into production. Please also suggest the prerequisites.
I have a solution with number of visual web parts in the development environment which is working fine. Need to move the Visual web parts to production (Existing site). So please suggest the safest methods.
Thanks and Regards,
Satish
Sathiish Reddy

Hi Satish,
From your description, my understanding is that you want to deploy your solution from development environment to production environment with a safest method.
These links below about moving content from environment to another environment could be helpful to you:
SharePoint 2013 Dev/Test/Production environment - Moving content
http://sharepoint.stackexchange.com/questions/78483/sharepoint-2013-dev-test-production-environment-moving-content
How to deploy webpart on production (not debugging) server?
http://sharepoint.stackexchange.com/questions/17779/how-to-deploy-webpart-on-production-not-debugging-server
you could also have a look at this link below about SharePoint Content Deployment Wizard:
How do you deploy your SharePoint solutions?
http://stackoverflow.com/questions/9543/how-do-you-deploy-your-sharepoint-solutions
Best Regards,
Vincent Han
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

I want to deploy AIR application in production environment. Will the licence for AIR is free?

Please let me know the licence details. Shall i have to pay any thing if i want to use in production environment.

Just after the 2012 Macs were released there were a lot of crashes involving those machines that Chrome got the blame for. By the time I got my hands on a 2012 MBA Chrome had been updated at least twice (plus it was never clear which version of Chrome was implicated, assuming it was the cause to begin with). All I can say now is that I've not replicated the issue with the last two versions of Chrome.

Automatic Deploying of Portal Configuration from Staging to Production Environment

Hello,
I'm anlyzing the opportunituy to write an automatic procedure that synchronize
our WebLogic Portal production environment with the staging one. These two environments
are physically separated.
I have found the BEA Propagation Tool. However it seems that is not possible to
define a procedure that is really totally automatic.
Firts of all, it is necessary to hava an manual operator that selects the objects
that have to be propagated and after starts the propagation process.
Besides it is necessary to have database connections beetween the progation tool
and both the environments.
What I'm looking for is a solution that
1. analyze the staging environment
2. export some files that contain both code, configuration and data (code, LDAP
and DB data)
3. import these files into the second enviroment
has someone deal with this problem?
Thans in advance
Ciao

Manish,
to answer your questions -
1. You can find the exact date and time for these refreshes/maintenance schedule on your production pod. Just go to 'Training & Support' in your production. There will be a calendar in which you can see the maintenance schedule. The details are quite accurate. to be sure of the time I would suggest you get in touch with the Service/Support rep at Oracle.
2 & 3) Oracle CRM On Demand provides a Migration Tool that can be used to migrate configuration changes from on POD to another. This can be between Staging --> Production and vice versa. Although, I would recommend that you go through the migration tool bookshelf and understand in detail the use of this tool. There are limited configurations that can be migrated. So it would be wise to create a plan based on what changes you are looking to migrate.
Note: Reports are copied on the Staging after the refresh only from Prod to Staging. This does not happen from Staging to Production. Reports will have to be created in Production and will be copied on Staging on a Quarterly basis (Check your refresh schedule)
4) You can use the migration tool to migrate configuration changes from a live environment into another instance.
The migration tool can be downloaded from:
Admin --> Import and Export Tools -->Oracle Migration Tool On Demand
You can download the Migration Tool Bookshelf here:
http://docs.oracle.com/cd/E22393_01/books/OnDemMigrTool.pdf
Thanks,
Royston

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

Issue in production environment

Hi,
We got an issue in the production environment on last Friday and yet not able to find out the root cause of the issue.
Environment
GUI : .Net
Server : Java
Application Server: Jboss
Database: Sqlserver
The Java application is deployed into Jboss application server which connects to SQL server as back end. GUI makes the web service call to server for data communication
Issue
Friday at 2 PM users reported the slowness of the application (Not getting the response from server in GUI), all the request from GUI were getting timed out.
Restart of Jboss didn't help
Restarted the Jboss and sqlserver for the second time and than the environment became stable
Analysis
1. From the thread dump of Jboss log we see that there are many threads waiting on a socket for database connection(according to database team all the connections are open and available at that particular time).
2. The size of transaction log is almost doubled during this period (when the issue was reported).
We couldn't find a reason why this issue is happened. Is it a database issue or something else? Please suggest...
Thanks,
Manoj

Hi Manoj,
According to your description, when running the web application, many threads are waiting for the socket from database which cause requests from front GUI time out. Right?
In this scenario, user can access the front GUI, which means the application server is working. Since the connections are all open at that particular time, it should not be issue on your JDBC. It seems to be a deadlock issue which cause other threads
waiting and hang. I recommend check and optimize your code. On database side, I suggest you open the SQL profiler, select DeadLock Graph, it will record when deadlock occurs. Please refer to links below:
Detecting and Ending Deadlocks
Analyze Deadlocks with SQL Server Profiler
If you have any question, please feel free to ask.
Simon Hou
TechNet Community Support

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.

Application works in UAT but gives an error while deploying in Production m

Error occured while deploying MYApp.ear on production domain. but the same is working fine in UAT below error occured...
<Apr 12, 2010 3:55:50 PM IST> <Error> <Deployer> <BEA-149205> <Failed to initial
ize the application 'MYApp' due to error java.lang.NoClassDefFoundError: org/sax
path/SAXPathException.
java.lang.NoClassDefFoundError: org/saxpath/SAXPathException
at java.lang.Class.getDeclaredFields0(Native Method)
at java.lang.Class.privateGetDeclaredFields(Class.java:2259)
at java.lang.Class.getDeclaredFields(Class.java:1715)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAn
notationProcessor.java:867)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAn
notationProcessor.java:860)
Truncated. see log file for complete stacktrace
java.lang.NoClassDefFoundError: org/saxpath/SAXPathException
at java.lang.Class.getDeclaredFields0(Native Method)
at java.lang.Class.privateGetDeclaredFields(Class.java:2259)
at java.lang.Class.getDeclaredFields(Class.java:1715)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAn
notationProcessor.java:867)
<Apr 12, 2010 3:33:51 PM IST> <Warning> <Deployer> <BEA-149004> <Failures were d
etected while initiating start task for application 'MYApp'.>
<Apr 24, 2010 3:48:51 PM IST> <Warning> <Deployer> <BEA-149078> <Stack trace for
message 149004
java.lang.NoClassDefFoundError: org/saxpath/SAXPathException
at java.lang.Class.getDeclaredFields0(Native Method)
at java.lang.Class.privateGetDeclaredFields(Class.java:2259)
at java.lang.Class.getDeclaredFields(Class.java:1715)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAn
notationProcessor.java:867)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAn
notationProcessor.java:860)
Truncated. see log file for complete stacktrace
java.lang

Hi,
It looks like your Production Environment doesnt have ANY of the following Jars in Either the Server Classpath or in <DOMAIN_HOME>\lib directory.
dom4j.jar
Or
jaxen.jar
Or
saxpath.jar
Please add these Jars in the ServerClasspath ... or in <DOMAIN_HOME>\lib directory.
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)

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

Redeploy in cluster in production environment

There is a cluster consisting two node in a production environment. The purpose is to make it possible, to upgrade a deployed application to a new version, with the highest avaibility. Is it possible to do it faster than the standard Redeploy method? Couse it lasts an hour at least, and during that time the application cannot be accessed.
          Ideal would be that it could be done without service breakdown. /On one node the application keeps running, on the other at first it is redeployed, than the while the second is restarting the former stops and then that is redeployed too./
          Is it Possible? Or any other way to solve that?

Hello Mathers,
          Why does it take an hour to redoply your app, are you precompiling JSPs on startup or do you have a vast number of EJBs, lots of connection pools with connections that are all created on deployment etc?
          Can you explain your deployment process and are you using WLS staging?
          A redeployment of the application I am currently working on (three ear files approx 100 EJBs and 3 web apps) takes about 15 minutes on each managed server, so we have about 15 minutes of down time. But I think I can get this down to 5 minutes without too much trouble.
          cheers
          Hussein Badakhchani
          www.orbism.com

Deploy to production (best practices)

I am wondering if there are some best practices published somewhere in regard to deploying an app from your dev environment to a production environment?
I currently do the following.
1) export/inport application
2) generate a sync script (toad) to get the schema objects in sync. Maybe it's better to do an export/import (expdp) of the schema here.
3) import images/files needed by the application

Hi,
Have a look at:
Book: Pro Oracle Application Express
Author: John Edward Scott
Author: Scott Spendolini
Publisher: apress
Year: 2008
It has a good section on migrating between environments.
Hope this helps.
Cheers,
Patrick Cimolini

Deploy in production environment

Similar Messages

Maybe you are looking for