Environments deploy

Hello,
I developed a system with JDeveloper that uses Oracle Database and Application Server which are installed on the developing network. I created Entities from tables and a Session Bean and everything is working great.
Now I would like to deploy the projects on a different environments such as Testing and Production.
I have created the same tables on the testing environment but when I used JDeveloper to deploy the projects the Application Server has collapse.
Please help and thanks in advance
Ronny

Finally had time to address this issue... used a stored procedure/TSQL-script to generate stored procedure calls that inserts the environment, variables and the project reference. You can copy those, adjust the values and execute them on the new server.
http://microsoft-ssis.blogspot.com/2014/02/deploying-ssis-2012-environments.html
Please mark the post as answered if it answers your question | My SSIS Blog:
http://microsoft-ssis.blogspot.com |
Twitter

Similar Messages

Deploying iTunes in lab environments campuswide

We are creating an iTunes U page for our institution (small college), but my question involves the deployment of iTunes across our campus. What is the best, most streamlined method for deploying and using iTunes over a campus network that has migrating user profiles?
We have several lab environments in which students would access iTunes, and we want to minimize the issues involving storage limits with migrating profiles, when any particular user will login to access iTunes from any particular workstation. Specifically, what would be the profile ramifications from accessing the user agreement to syncing their devices? Furthermore, we are mostly a Windows-based campus, so we're looking for any additional caveats that might occur.
Any thoughts, suggestions or references would be greatly appreciated.

We are creating an iTunes U page for our institution (small college), but my question involves the deployment of iTunes across our campus. What is the best, most streamlined method for deploying and using iTunes over a campus network that has migrating user profiles?
We have several lab environments in which students would access iTunes, and we want to minimize the issues involving storage limits with migrating profiles, when any particular user will login to access iTunes from any particular workstation. Specifically, what would be the profile ramifications from accessing the user agreement to syncing their devices? Furthermore, we are mostly a Windows-based campus, so we're looking for any additional caveats that might occur.
Any thoughts, suggestions or references would be greatly appreciated.

How to achieve Incremental deployment of Code Files to different environments of windows azure using TFS and Visual Studio ?

Hi
We are new to Windows azure and are developing a web application. In the beginning of the project , we have deployed complete code using Sitefinity Thunder to different environments which actually publish complete code. But now as we are in the middle of development
, we are just required to upload any new files created which can be quite less in numbers (1 or 2 or maybe few). Now if we deploy with thunder , it publishes all files and then deploys complete code which takes good amount of time. Hence we are thinking to
attach each Azure Cloud Service which is actually a different environment like staging, UAT to a TFS branch and then just check in code from local development machine to TFS and then deploy only checked in files to azure environment linked to TFS.
I hope this possible but if you can help send some links where I can see how to achieve this , that will be helpful.
Also I would like to know whether a single cloud service can be linked to a single TFS branch or multiple cloud service can be linked to a single TFS repository? Why I am asking is – because we want to deploy a checked in files revision number to a staging
cloud service and then will test there and then if everything works well then will be required to deploy these revision files to the next cloud UAT cloud service and then production cloud service. Please help.

Hi,
We can use TFS to manage our azure cloud service application code, refer to the following to get more information about how to deploy sitefinity to azure.
#http://www.sitefinity.com/documentation/documentationarticles/manually-deploying-your-project-to-windows-azure
#http://www.youtube.com/watch?v=E2aZ7lE1JUA
#http://www.sitefinity.com/documentation/documentationarticles/sitefinity-azure-configuration
If any question about sitefinity, please redirect to sitefinity forum:
http://www.sitefinity.com/developer-network/forums if the issue was related with azure, welcome to post again.
Best Regards
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

B2B configuration deployment to higher environments

Hi ,
I am new to B2B.My question may sound ridiculous but anyone please provide me some light on this.
How B2B configuration done in dev environment is deployed to higher environments(test,UAT).
Does this configuration get stored in a file that can be deployed to higher environments through ant scripts?
please help me gurus.

While creating agreement I see that we need to select channels for Host TP and Remote TP as well.Remote TP channel is used to send outbound messages to remote TP and Host TP channel is used to pass incoming message to middleware(internal applications).
In case of Outbound agreement, you need to select only Remote TP channel.
In case of Inbound agreement, Remote TP channel is required to send acknowledgement back for exchange protocols like ebMS, RosettaNet, AS2 etc. It also plays a role in message security (signing and encryption). Host TP channel should be selected if you want to pass incoming message to middleware (internal applications) through non-default B2B internal channel (IP_IN_QUEUE or B2B_IN_QUEUE). If you are using default B2B internal channels (IP_IN_QUEUE or B2B_IN_QUEUE) to pass incoming message to middleware, then you should not select any channel in Host TP drop-down.
You may refer -
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10229/bb_agree_flow.htm#CEGDGCAH
Regards,
Anuj

Is SCOM security compliant (ISO and HIPAA ) to deploy in health care environments

Hi All,
We have a requirement to deploy SCOM 2012 and a questioned arise.
is SCOM security compliant (ISO and HIPAA ) to deploy in health care environments.
I would appreciate if you can clarify me on this regards.
Thanks in advance.
Raj
raj

Hi Raj,
As we know, SCOM is used to monitor objects healthy based on monitors or rules created within management packs. After searching the internet, it seems like that few article take ISO and HIPAA together with SCOM.
What do you want to achieve with SCOM?
Regards,
Yan Li
Regards, Yan Li

Questions regarding deploying Biztalk WCF service to higher environments.

Here is my situation:
I have published BizTalk schema as WCF service in my local.
I need to move this to higher environments, is there any way I can move this to upper environments without again using WCF service publishing wizard in respective environments.

Hi,
These are the more common options that I have used for this task:
Use the IIS Web Deploy: with this tool, you can export the WCF Service as a ZIP package that can be imported in the target environment manually or using the command line.
http://www.iis.net/downloads/microsoft/web-deploy
http://jpsmit.bloggingabout.net/2012/06/04/deploying-wcf-services-using-web-deploy/
Include the WCF service inside the BizTalk deployment package: I don't recommend this approach because it doesn't allow almost any customization when deployed in the target environment.
Generate a Web Setup Project: other option can be creating a web setup Project in visual studio that will deploy the WCF service.It allows some customization when deploying in the target enviorment.
http://jpsmit.bloggingabout.net/2010/03/29/deploying-a-wcf-service-using-a-web-setup-project/
Using a custom tool: as Rachid Sikrosia said in the previous post, you can use BizTalk Deployment Framework o BizTalk powershell addin to do this task.
https://psbiztalk.codeplex.com/
In my last Project, I have used a combination of both Web Setup Project and some powershell scripts to configure correctly the web site, application pool, enabled bindings, etc...
Best regards.

How to deploy site collection has sub sites to other environments

Hello everybody,
I have a site collection SharePoint online.
In the site, haven 3 sub sites.
Now, i want to deploy this site to other environment,
How can i do that?
I am trying save site as template but that is not support sub site.
Thanks and best Regards,
QuyenPV

Hi,
According to your post, my understanding is that you want to backup SharePoint online site to another environment.
For SharePoint server, we can use the PowerShell to backup the site collection with all the subsites.
However, per the technet article below, there is no backup and restore cmdlets for SharePoint online to backup and restore.
http://technet.microsoft.com/en-us/library/fp161374.aspx
You can use the third-party tool to achieve this scenario.
http://blogs.technet.com/b/akieft/archive/2012/01/09/restore-options-in-sharepoint-online.aspx
As this is the forum for SharePoint server on-premise, I’m not familiar with the SharePoint online, for this issue, I recommend you can post a new question in the forum for Office 365/SharePoint online.
http://community.office365.com/en-us/forums/154.aspx
More experts will assist you, then you will get more information relation to SharePoint Online.
Thank you for your understanding and support.
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

Deploy InfoPath Forms across Ms SharePoint environments

Hi,
I have created workflows in MS SharePoint 2010 and added MS InfoPath forms in it. However, when migrating the workflow from DEV to TEST environment, the InfoPath is not included. I would like to export the MS InfoPath form DEV and import it into TEST environment.
I am looking for help regarding the migration. Any help in this regard will be appreciated.

Hi Abhijit,
For migrating workflow with InfoPath Forms in SharePoint 2010,you can refer to the steps as below:
1. Export source files of the form. Open form in InfoPath designer. And because we can't republish it to the different place using wizard (its type is a Workflow form), we should Export source files (from the menu File\Publish) to some folder.
After this step we received a set of files, one of which is "manifest.xsf".
2. Close InfoPath designer.
3. Correct URLs in manifest.xsf Open "manifest.xsf" in a text editor. Find all URL related to the first site collection and replace it with new URLs linked to new site collection. Save the file.
Hint: If you don't know the URL to publish in new site collection, you can open autogenerated form from it in the same manner (look at URLs in its manifest.xsf).
4. Publish changed form. Open InfoPath designer, open corrected manifest.xsf in it and publish it (by pressing the publish button for example).
5. Hurray! The form is deployed to the new place!
You should repeat this steps for all custom InfoPath task forms in your workflow.
Reference:
http://sharepoint.stackexchange.com/questions/41542/how-to-reconnect-infopath-task-form-to-spd-workflow-after-moving-it-to-the-new-s
http://sharepoint.stackexchange.com/questions/36462/copying-a-globally-reusable-workflow-in-sp-designer-loses-form-task-fields-and-i/41556#41556
Thanks,
Eric
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Eric Tao
TechNet Community Support

JCAPS deployment to multiple external system environments.

While creating deployment profile, we need to map the resources (such as jdbc, webservice connector) to external systems.
External systems are predefined with the target server ip, port, db name, credentials etc(in case of jdbc).
So the problem is an EAR built for test environment can not be deployed to production environment without a re-build. This introduces concerns of manual errors and inconsistencies.
In simpler applications we could store database/credentials etc on to property files and hence EAR built for UAT could be deployed to Production with out any change.
Or we could edit database resources per environment and all the resources would be using JNDI names.
Is there a similar strategy available for JCAPS by which EARs built against an environment can be promoted to another seamlessly?

Take a look at: http://eai.ittoolbox.com/groups/technical-functional/seebeyond-l/changing-properties-of-an-interface-after-deployment-logging-interface-2105662
A brief Summary:
- Many adapters can be dynamically configured - that is config info can reside in a database.
- Java Caps Allows for connection to an LDAP server for dynamic lookup. There is some caveats described in the link above. It also seems to have been preserved for compatibility reasons in CAPS 6 (see below). I do not know if the basic problem (how to find the correct LDAP environment for your needs) have been officially solved in the CAPS 6 implementation
- Tools like iDeploy (for ICAN 5.0.5 J2EE) and iConfigure (distributed by Support) allows for updates of a specific EAR-file with config parameters stored in files. I doubt sincerely that these are (or have ever been) supported (despite of Sun Support distribution) or maintained.
- It is possible to perform jndi-lookups from collabs or external code. The transactionality aspect is however unpredictable.
- I believe what would work for you is the new CAPS6 dynamic configuration functionality. For an overview, please note: http://wikis.sun.com/download/attachments/38767325/JavaCAPS6+Application+Configuration.pdf?version=1&modificationDate=1225463856000 and http://wikis.sun.com/display/JavaCAPS/Application+Configuration and http://wikis.sun.com/display/JavaCAPS/Application+Configuration+Lab.

Instructions to deploy human task forms into production environments

What is the easiest way to deploy BPEL human task forms into a production environment? Can we use ant? Where can I find the document?

What do you mean by "a while"? I gave it quite a bit of time, at least 10 minutes. I'm not quite sure how to reference the different views, so we are talking about the same thing. So let me try to explain what I did.
From the Console home I click on the project I am interested in which gets me to the
project home with components listed (BPELProcess and Humantask) and instance IDs below. I click on the instance I want to see and get the
Flow Trace page. I then click on the BPELProcess to get the
Instance Detail page.
The first time I went thru this sequence BPELProcess and Humantask where both "running" on the Flow Trace page and on the Instance Detail page I get what I expect "waiting for 'onTaskCompleted'
After responding to the task:
I get "Completed Successfully" for the BPELProcess on the Flow Trace page. Even after several minutes and starting up the console from the start again, when I went to the Instance Detail page it still showed "waiting for 'onTaskCompleted' both on the Audit tab and the Flow-Debug tab. The Instance Detail for the Humantask showed Intitated, Outcome Updated and Completed.
Hope this is clearer.
Interestingly enough, I just went back to be sure I was naming everything correctly for this reply and found that the BPELProcess detail for that same instance now shows detail to completion. Now this is a few hours later and the server has gone down and restarted 2 or 3 times with errors. I'll start another thread with the errors so any response doesn't get lost within human task.

Automatically deploy outlines between environments

Hello everybody:
I would like to know your opinion about this question: How could I pass outline changes between environments (Dev, Prod, etc.) automatically?
Essbase is version 11.1.1.3 and I know several ways to pass changes:
1) Using migration wizard (manually)
2) Overwriting physical otl files (automatically but with problems if data exists)
3) Using 'Save as' menu in EAS (manually)
4) Using rules to upload incremental files which define, for example, father-child relationships in a dimension (automatically)
Right now, 4) is my best shoot but I do not know if there are other ways to pass outline changes between environments.
What is your opinion? Which option do you use?
Thank you
Regards
Javier

2) Overwriting physical otl files (automatically but with problems if data exists)^^^You could use MaxL to delete existing apps/dbs, create new ones, stop the database(s), shell out to do file copies across environments, start the new ones. This sounds complicated writing it out, but would actually be pretty easy to script.
If you drove security through MaxL scripts (filters, access, etc.) you could just repurpose those scripts using MaxL variables to the target database.
There's also always EPMA. Brrrrr, was that a chill wind that just blew by?
Regards,
Cameron Lackpour

Deployment of dashboards to different folders in different environments

Dear All,
I need to publish dashboard, Xcelsius components and crystal reports from one environment to another. The problem is that folder structure on source and target is different. We are using VersionManager for deployment of webi and deski reports. This tool allows seamless deployment to different folder structures, but doesnu2019t support dashboards, Xcelsius and Crystal. Is there any method to do it with standard tools or scripting with SDK?
Regards,
D.

Hi Dmytro,
Which version of BOE are u using? If it is XI 3.1 you could use LCM. If not try Import Wizard for the dashboards (build using dashboard builder?) Xcelsius and Crystal. You could save the Xcelsius and Crystal Reports directly from the client to the target environment by using a local copy but that will created different CUIDs in the landscape and a conflict with your dashboards (if Xcelsius and/or Crystal components are included).
Hope this helps...
Martijn van Foeken
Focuzz BI Services
http://www.focuzz.nl
http://nl.linkedin.com/in/martijnvanfoeken
http://twitter.com/mfoeken

Best practice to move things between various environments in SharePoint 2013

Hi All SharePoint Gurus!! - I was using SP deployment wizard to move Sites/lists/libraries/items etc. using SP Deployment Wizard (spdeploymentwizard.codeplex.com) in SP 2010. We just upgraded to SP 2013. I have few Lists and Libraries that I need to push
into the Staging 2013 and Production 2013 environment from Development 2013 environment. SP Deployment Wizard is throwing error right from the startup. I checked SP 2013 provides granular backups but is restricted to Lists/Library level. Could anybody
let me know if SP Deployment Wizard works for 2013? I love that tool. Also, Whats the best practice to move things between various environments?
Regards,
Khushi
Khushi

Hi Khushi,
I want to let you know that we built
SharePoint Migration tool
MetaVis Migrator that can copy and migrate to and from on-premise or hosted SharePoint sites. The tool can copy entire
sites with sub-site hierarchies, content types, fields, lists, list views, documents, items with attachments, look and feel elements, permissions, groups and other objects - all together on at any level of granularity (for
example, just lists or just list views or selected items). The tool preserves created / modified properties, all metadata and versions. It looks like Windows Explorer with copy/paste and drag-n-drop functions so it is easy to learn. It does not require any
server side installations so you can do everything using your computer or any other server. The tool can copy the complete sites or just individual lists or even selected items. The tool also supports incremental or delta copy based on the previous migrations.
The tool also includes Pre-Migration Analysis that helps to identify customizations.
Free trial is available:
http://www.metavistech.com . Feel free to contact us.
Good luck with your migration project,
Mark

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

Environments deploy

Similar Messages

Maybe you are looking for