Azure package deployment automation

Hi All,
I am looking for Azure package deployment automation. Let me know if any article or any other stuffs will be great help..
Thanks,
Bhupi..

There are several good resources about
Continuous Delivery for Azure by using TFS , works both for TFS Services and similarly for TFS on premise. I think this is a good starting point also if you look to develop something custom.

Similar Messages

How can I use UC4 instead of SSIS Master Package deployed using project deployment model?

Hi Folks,
My team is planning to opt UC4 for scheduling the SQL Jobs and I have to come up with a plan to integrate it.
As of now, I do not have software licence in place to do some research.
If you have worked on it, can you tell me that how can I schedule SSIS packages using UC4.
Also, we are using SSIS project parameters (Project deployment Model). What kind of changes I have to make in SSIS packages to support UC4. Is it possible to pass parameters to SSIS package through UC4? If not, is there any alternativ?
Appreciate your help!
Gaurav Gupta

If you have access to Automic Community, there are details there on how to execute SSIS 2012 packages deployed in SSISDB catalog (project deployment model). Here is the link:
https://community.automic.com/discussion/4878/how-to-execute-sql-server-data-tools-ssdt-2012-package-synchronously-using-sql-job
Leonard

Best report to check application and package deployment compliancy?

I am looking for the best report to check application and package deployment compliancy.
Preferably targeting a collection.
tconners

I'm recommending this one:
Software Distribution - Application Monitoring folder -
All application deployments (advanced)
It allows you to select Collections and applications
Kent Agerlund | My blogs: blog.coretech.dk/kea and
SCUG.dk/ | Twitter:
@Agerlund | Linkedin: Kent Agerlund |
Mastering ConfigMgr 2012 The Fundamentals

App for SharePoint online : Resource files can not with the app install package deployment

I come from China, my English is not very good, bring you the confusion, I apologize;In the development of the APP to the store, I met a problem, hope someone can help me to solve, thank you very much, specific as follows:
The development tools: vs2012
Platform: office 365 development version
Host:Auto
Problem presentation:
Press "F5" debugging running normally,Generate app install package, deploy to test environment, the app page error, tip can't find the resource file"
error:
Server Error in '/' Application.
Object reference not set to an instance of an object.
Description: An
unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
Line 107: <div id="FoundareADUserIndex_PageHead">
Line 108: <span><img alt="" src="../images/head.png" height= "45px" width="45px" /> </span>
Line 109: <span style="color: #000000; font-size: 28px; font-weight: bold"><%=HttpContext.GetGlobalResourceObject("FoundareADUserResource", "foundare_index_head").ToString()%></span> 
Line 110:
Line 111:
Source File: c:\DWASFiles\sites\fzym9dfaguchcdqnvjrwcr2pqasevj5hpvhmcaydkdg1.0.0.0\VirtualDirectory0\site\wwwroot\Pages\Default.aspx
Line: 109
Stack Trace:

Hi,
According to your post, my understanding is that you want to use resource files in your SharePoint app project.
Here is an article for your reference:
http://msdn.microsoft.com/en-us/library/office/fp179919.aspx
Code sample: SharePoint 2013: Localize the app web, host web, and remote components of an app
http://code.msdn.microsoft.com/office/SharePoint-2013-Bookstore-328060fc/sourcecode?fileId=60464&pathId=1536365664
Best Regards
Dennis Guo
TechNet Community Support

SCCM: Application deployment vs Package deployment with requirements and prerequisits.

Hey,
My organization is in the process of implementing a new remote networking solution for all employees, however some employees require additional software vs others. What I am trying to find out is if there is a way to have one package with supersedes and
requirements that we can use to do a massive deployement.
Here are the different scenarios with order of installation:
Financial group Desktop:
1.Install New solution
2.Install Configuration
3.Install Token Authentication
(nothing crazy)
Financial Group Laptops
1.Install Token Authentication
2.Install New Solution
3.Install COnfiguration
4.Un-uninstall Old Solution
5.Un-install Tunnel Guard application (requires a reboot, that's why it's last). (this is the application that would be deployed with requirements to go back up the chain of supersedes (meaning, deploy 5, but do 4, when 4 is triggered, it does 3 first, etc...)
All other laptops
1.Install New Solution
2.Install COnfiguration
3.Un-uninstall Old Solution
4.Un-install Tunnel Guard application (requires a reboot, that's why it's last).(this is the application that would be deployed with requirements to go back up the chain of supersedes (meaning, deploy 4, but do 3, when 3 is triggered, it does 2 first, etc...)
Because of the different requirements, is there a way to have one deployment with multiple deployment types to say based off:
1. Computer types (we have a naming convention that identifies laptops and desktops.
2. Only install certain pieces of software (Token validator in this case if financial application is detected on the machine).
Or should I create different applications for each case with different collections or go with 3 different packages and collections with install this package first set in the package deployment
Thanks for your help.

The problem is the last uninstall, because it's not applicable to all machines. That means that if you would deploy that with all it's dependencies, it wouldn't do anything on the desktops as it's not applicable to them.
In this case, if you want to use one deployment, the easiest solution is a task sequence. That way you can target everything in one time and still build some logic to prevent some (un-)installs.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

BPEL deployment automation

Hi all.
I've been reading about the efforts regarding esb deployment automation:
Dealing with changing service wsdl locations in the ESB
Now, I'd like to know about the latest best practices regarding BPEL deployment automation for different environments.
I was wondering if there's some already tested ant configuration for deploying multiple BPEL projects at the same time using a specific bpel.xml
Thanks
Denis

I created an article on this issue:
http://orasoa.blogspot.com/2006/08/using-ant-in-bpel-environment.html

ESB Deployment Automation Fault

I'm using the ant ESB Deployment Automation tasks authored by Doug Gschwind and referenced in other threads. I get a build failed error when trying to extract an ESB deployment plan. The error states that the output file already exists but the directory where it resides cannot be written or the filename does not have a .xml extension.
My set up is:
D:\temp - contains ESBMetadataMigrationTaskdefs.xml, ESBMetadataMigration.jar, my ant project file and the output file (PMSProto1Plan.xml). Both the directory and file are not read only.
I had to install commons-httpclient and also JAXB (from Sun Java Web Services Developer Kit). I did note that I had to find jsr173_1.0_api.jar under my JDeveloper home. I used your sample exampleBuild.xml as the basis of my ant file.
My extract file looks like:
<?xml version="1.0" encoding="UTF-8"?>
<project name="ESBMetadataDeployment" default="usage" basedir=".">
<property name="esbProjectToDeploy" value="D:\Oracle\JDeveloper\jdev\mywork\CVSTest\LR\PMSProto1"/>
<property name="deploymentPlanFilename" value="${basedir}/PMSProto1Plan.xml/"/>
<import file="${basedir}/ESBMetadataMigrationTaskdefs.xml"/>
<target name="test.ExtractESBDeploymentPlan">
<extractESBDeploymentPlan sourceDir="${esbProjectToDeploy}" deploymentPlanFile="${deploymentPlanFilename}"/>
</target>
<target name="usage">
<exec executable="ant" dir="${basedir}" vmlauncher="false">
<arg value="-projecthelp"/>
</exec>
</target>
</project>
My ESBMetadataMigrationTaskdefs.xml looks like:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<project name="ESBMetadataMigrationTaskdefs">

<property name="commons.httpclient.home" value="C:/Program Files/ApacheGroup/commons-httpclient-3.0.1"/>
<property name="jaxb.v2.0.2.home" value="C:/Sun/jwsdp-2.0"/>
<property name="soa.suite.home" value="D:/product/10.1.3.1/OracleAS_2"/>
<property name="JDev.home" value="D:/oracle/JDeveloper"/>

<dirname property="imported.basedir" file="${ant.file.ESBMetadataMigrationTaskdefs}"/>
<taskdef resource="oracle/tip/esb/client/anttasks/antlib.xml">
<classpath>
<pathelement location="${imported.basedir}/ESBMetadataMigration.jar"/>
<pathelement location="${commons.httpclient.home}/commons-httpclient-3.0.1.jar"/>
<pathelement location="${soa.suite.home}/lib/xmlparserv2.jar"/>
<pathelement location="${soa.suite.home}/integration/esb/lib/commons-logging.jar"/>
<pathelement location="${soa.suite.home}/integration/esb/lib/commons-codec-1.3.jar"/>
<pathelement location="${soa.suite.home}/integration/esb/lib/oraesb.jar"/>
<pathelement location="${jaxb.v2.0.2.home}/jwsdp-shared/lib/activation.jar"/>
<pathelement location="${jaxb.v2.0.2.home}/jaxb/lib/jaxb-api.jar"/>
<pathelement location="${JDev.home}/integration/lib/jsr173_1.0_api.jar"/>
<pathelement location="${jaxb.v2.0.2.home}/jaxb/lib/jaxb-impl.jar"/>
</classpath>
</taskdef>
</project>
I'm using JDev 10.1.3.3.0.4157 and SOA Suite 10.1.3.3
Has anybody hit this issue before and hopefully a solution ? Thanks.

For what it is worth I can confirm that what user531376 describes is the correct answer to the problem. Add this line:
<delete file="${deploymentPlanFilename}" verbose="true"/>
to the ExtractESBDeploymentPlan target and you should be fine.
Maybe this blog post (shameless self-promotion) adds to your knowledge: http://technology.amis.nl/blog/?p=2371.
Happy building, Sjoerd

Packaging/deploying a webapp client to already deployed EJBs

I have a webapp/ejb deployed on WLS 6.1. If it matters, the EJBs are
deployed in jar files but the webapp component is deployed in exploded
directory format.
Now I want to deploy another webapp that uses the same EJBs. At this
point in development, I am attempting to deploy this in exploded
directory format as well. I have run ejbc manually against the original
jars to create the EJB deployable units containing generated WL classes.
This also created a ejb-client.jar, but it does not contain any impl
classes for the home or remoted interfaces.
I tried placing the ejb-client.jar in my WEB-INF/lib but it doesn't seem
to be able to find the interface classes. Perhaps the exception I'm
getting does not mean what I think it does. It is included below.
I also tried adding the generated impl classes to the ejb-client.jar
manually, but this didn't work either. I have read the
packaging/deploying docs but don't seem to find this issue addressed
directly. From all I know, I have done this correctly, but obviously I
am missing something somewhere.
Thanks in advance for your consideration.
<May 10, 2002 1:53:57 PM CDT> <Error> <HTTP>
<[WebAppServletContext(9605583,adminApp,/adminApp)] Servlet failed with
Exception
java.lang.ExceptionInInitializerError
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:42)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:30)
at java.lang.reflect.Constructor.newInstance(Constructor.java:277)
at java.lang.Class.newInstance0(Class.java:301)
at java.lang.Class.newInstance(Class.java:254)
at javax.rmi.CORBA.Util.createDelegateIfSpecified(Util.java:342)
at javax.rmi.CORBA.Util.<clinit>(Util.java:54)
at
javax.rmi.PortableRemoteObject.createDelegateIfSpecified(PortableRemoteObject.java:182)
at
javax.rmi.PortableRemoteObject.<clinit>(PortableRemoteObject.java:61)
at
net.verizon.storm.util.DataBroker.initialize(DataBroker.java:102)
at
net.verizon.storm.util.DataBroker.getInstance(DataBroker.java:158)
at
net.verizon.storm.util.OrderDispatcher.<init>(OrderDispatcher.java:70)
at
net.verizon.storm.admin.OrderService.startOD(OrderService.java:159)
at
net.verizon.storm.admin.OrderService.processRequest(OrderService.java:104)
at
net.verizon.storm.admin.OrderService.doPost(OrderService.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Caused by: java.lang.RuntimeException: could not find or instantiate any
UtilDelegate class
at
weblogic.iiop.UtilDelegateImpl.<clinit>(UtilDelegateImpl.java:72)
... 24 more

Hi.
I tried placing the ejb-client.jar in my WEB-INF/lib but it >>doesn't seem to beable to
find the interface classes. Perhaps
the exception I'm getting does not mean what I think it does. >>It is includedbelow.
It seems fine since it is the way your webapp always to use its EJB client jar.
I also tried adding the generated impl classes to the ejb-
client.jar manually, but this didn't work either.Nope, you should never do this since Impl classes are used on Server Side ( webapp
treated as client of EJB in this case ) only.
It is so hard for us to analyze the problems without a test case, I would suggest
you to create a support case via http://support.bea.com/welcome.jsp to BEA support
for detailed work.
Thanks.
Ji Zhang
Developer Relations Engineer
BEA Support

Reading data file(txt) present in a file system from a package deployed in SSISDB

Hi,
I am trying to create and later read a data file from a package deployed in SSISDB, but it is not reading it while it is successfully creating the file. The same package when run from the file system package, runs successfully. Generating ispac and deploying
in SSISDB is running for infinite time. Any idea? Is it a permission issue?
Thanks
Ayush

Hi Ayush,
If I understand correctly, you directly execute a package from the file system source via Execute Package Utility, it works fine. When you right-click on a package under Integration Services Catalog \ SSISDB \ <Folder name> \ Projects \ <Project
name> \ Packages \ <Package name> and select Execute... to run a package in SQL Server Management Studio, it fails.
When we execute a package under Integration Services Catalog, the package will run under the credentials used to connect to SQL Server Management Studio. Please note that we need run the package using Windows Authentication.
As to your issue, please make sure the account connects to SQL Server Management Studio has required permissions to access the file folder and file outside the SSIS package.
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Article - LabVIEW-Based Utility to Package & Deploy MS SQL Server 2005 Express Edition Databases

Anthony Lukindo, the newest ExpressionFlow blog LabVIEW community author, has just published the first part of his two-part blog article
LabVIEW-Based Utility to Package & Deploy MS SQL Server 2005 Express Edition Databases - Part 1
Please check it out!
Tomi Maila

Anthony Lukindo, the newest ExpressionFlow blog LabVIEW community author, has just published the first part of his two-part blog article
LabVIEW-Based Utility to Package & Deploy MS SQL Server 2005 Express Edition Databases - Part 2
Please check it out!
Tomi Maila

How to build, package & deploy web services manually without ant on JWSDP

Hello,
How can I Build, Package & Deploy web services manually without using ant tool on JWSDP 1.3?.
Because I am having difficulties in using ant tool for my own webservices. ant is very tightly coupled with the directory hierarchy & configuration files (as I go throught the examples of JWSDP1.3). Also I need to learn the overall process going on behind the scene.
I have to teach the simplest required steps to build, package & deploy any webservice to any container independent of application server & OS without using ant tool. It would also help me to understand which items are required as specified in the Web Services Specifications & which one are implementation or platform specific.
Any help would be greatly appreciated.
Thanks,
Iftikhar.

Just follow the step of the JWSDP1.3 tutorial..

OIM 11g: Event Handler Packaging/Deployment

Need some advice/guidance on best practices for packaging/deploying Event Handlers in OIM 11g.
In our OIM 9.1 environment, we organized all of our custom code by "functional area" so we have JAR's named oim-common.jar, oim-ad.jar, oim-oid.jar, etc. Within each one of these JAR's we have all adapter code, scheduled tasks, and 10g event handlers related to that area. This approach was done to promote code reuse and make unit testing easier.
From what I've read on 11g Event Handlers, it sounds like each event handler needs to be packaged as a plugin along with it's own JAR so that we'd have one JAR per event handler. So, if we have 100 event handlers, we'd need 100 JAR's? Is this required or can our plugin ZIP files just contain the XML definitions as long as the referenced classes are on the classpath?

Gyanprakash Pandey wrote:
You should have a separate plugin package for each event handler. Practically we should have number of event-handlers as less as possible. If there are more event-handlers we must modify the design as event handler cause performance issues.
Regards,
GPHi Gyanprakash,
I'm going to use event handlers in my project, so I'm interested very much in hearing about the performance issues.
Besides, I do not see why I shall package every handler separately. Is this intended behavior or because of some bugs in OIM?
Regards,
Vladimir

SQL 2012 SSIS Single Package Deployment

I have the following scenario:
I have a 2012 SSIS project that contains two packages and on the release of the project, I deploy the entire project solution which has both packages. I then create a SQL Agent job that executes the packages from the SSIS catalog and all is well.
Down the road, a change is required for both packages and both packages are being developed. The first package change is ready to be deployed and the business wants the change to be implemented and does not want to wait for the second package development.
How do I deploy my project to get the first package deployed without overwriting the second package? I do not want to drop out the second package from the project because the agent job is depending on the package to be located in the catalog. However, I
cannot just create a new project deployment with the second package changes since the second package is not ready to be deployed yet.
Is this possible? In the deployment wizard, nothing is available to select only a specific package to update.
I want to take advantage of the SSIS catalog for configuring connections, parameters and the like but this ability to replace a single package needs to be available.
Can we do something in Powershell to add the updated package to the packages collection, which will overwrite the existing package or would that mess up the project deployment and the OOTB versioning that exists?
Or, is the workaround to create a new project with the Package One Updates and the original Package Two, walk through the deployment wizard to create the ISPAC file and then deploy that project to the catalog. (I guess answering my own question here but
really hoping for something more elegant)
Thanks in advance
Chuck

I agree completely with Mahesh.
Ever since the days of UNIX makefiles, only those parts of a project which have changed have been recompiled.
Indeed for instance, Visual Studio does this by default when building .NET projects, C++ etc - only what has changed is rebuilt, I mean it makes sense. Why waste time rebuilding something that hasn't changed at all.
I do not understand why an SSIS project requires the full redeployment of every single package when only one may have changed - it seems incredibly risky and exposes us to inadvertently deploying changes in other packages that we don't want to.
The workarounds described above that involve branching/merging etc in order to only be able to deploy a portion of a SSIS project may work to reduce that risk - but they can hardly be called 'best practice'. We risk end up making a mess of our version histories.
It would be good to get some direction from Microsoft on why it has been implemented the way it has, perhaps there is something we don't understand - in particular the decision to compile all packages into a single .ispac - after all, that's the source of
our problem here.
It would be handy to have a smaller target unit of compilation - again, forgive my possible lack of understanding here, but what is the reason for the granularity of deployment to be at the project level, and why wasn't the target of deployment simply kept
at the package level?
That was the massive change from 2008R2..
Thanks! Josh

Use Package Parameters in Package Deployment Model

Can you use Package Parameters when you use the Package
Deployment Model? The Parameter tab is visible in SSDT and in SSDT they seem to work, but can you use them outside SSDT? In a SQL Agent Job or on the command prompt?
And if not... why is the tab visible? ;-)

Hi HansAnderss,
Integration Services (SSIS) parameters allow us to assign values to properties within packages at the time of package execution. We can create project parameters at the project level and package parameters at the package level. But the use of parameters
are only supported in Project Deployment Model, we cannot use parameters in Package Deployment Model. This is by design.
Just as you said, we can also see the Parameters tab in Package Deployment Model. And I couldn’t find a way to hide the pane. If you have concern about this issue, I recommend you that submit the requirement at
https://connect.microsoft.com/SQLServer/. If the requirement mentioned by customers for many times, the product team may consider to add this feature in the next SQL Server version. Your feedback
is valuable for us to improve our products and increase the level of service provided.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

SSIS Parent package Deployment model

Hi,
I'm converting a SSIS 2008 R2 solution with multiple project to SSIS 2014, one of the projects stores only parent packages and these packages are calling packages in other projects. Using project deployment with project reference I guess this is not possible.
But can I have a parent package in package deployment model project and then call child-packages in project deployment model? Can I set values in an SQL Server Agent Job that sets project parameters?

Hi perwi,
I think in this scenario just convert, the legacy mode should be used and make sure the conversion is successful, only then try switching to Project Deployment.
Nothing can be set in the Agent, but in the Catalog (SSISDB).
Arthur My Blog

Azure package deployment automation

Similar Messages

Maybe you are looking for