When upgrading Talend server components such as TAC, Command Line, Job Server etc... Is it possible to use the talend installer instead of upgrading each application individually?
Yes you can use the Talend Installer instead of installing each piece individually but here is the catch
Talend does not support in place upgrades, so for example even going from Talend 6.2.1 to Talend 6.3.1 requires a fresh new install- and they recommend doing it on brand new servers as you don't want to install multiple versions on same box.
If your deployment strategy utilizes multiple servers you will still be running the installer multiple times (e.g. TAC on separate server than your job server).
Related
I have a VSTF build server which we use to build and deploy our applications mostly C#. I have now been challenged with deploying SSIS packages. From a manual perspective on my laptop we can get things accomplished, but on the build server we are having issues. This has been our guide, but it was written in 2017. https://www.red-gate.com/simple-talk/sql/ssis/deployment-automation-for-sql-server-integration-services-ssis/
We are on VSTF2019, VS2019. On the build server we use only the MSBuild tools, but it seems like SSIS on the build server wants the full UI for VS2019 and SQL Server Management Studio and SSIS.
Our issue is our C-Drive has insufficient space to support these UI's and they don't fully allow us to deploy them to the D-Drive where we have more then enough space.
I am looking for a document or how-to add SSIS (2019) to our build server so that it can be built and deployed using the least amount of space on the c-drive, like build tools. or does SSIS need a build server of its own?
You can use SSDT standalone installer to install Integration Services without a SQL server. See document here for more information.
does SSIS need a build server of its own?
Building SSIS package needs the required tools(VS2019+SSIS) to be installed in the build server. If this is achievable. You can just install the tools in your existing build server.
Or you can just create on-premise build agent on a new build server which has the tools installed.
If you are able to have a build server with Visual Studio and SSIS designer installed. Deploying SSIS packages would be much easier. You can use the SSIS Build/Deploy task directly in your pipeline. See document here.
Thanks in advance. I am working on to upgrade JBOSS As7 to Wildfly 10. Manually I am able to do it. But I am looking for scripted solution that works without manual intervention as I need to upgrade 1000s of client. Please suggest some tools or scripts to do this.
Thanks,
Naga
I prefer to use CLI scripts to configure a server.
You are able to use variables and use the sript on different installations.
Also you are able to configure a new instance the same way as before.
If you use a newer version the CLI run check whether all is applicable.
I don't think that there is a general tool to migrate the config.
For minor versions you are able to copy the configuration folder, but you might loose new enhancements or features.
When trying to install Talend MDM, the documentation said something rather interesting:
"JBoss Application Server comes prepackaged with Talend MDM."
That would make my life a lot easier, but I can't tell if they are trying to say that Talend's downloadable version of JBoss comes with Talend MDM, or if the open source JBoss AS actually comes with Talend?
If so, what other neat software tools come prepackaged with JBoss, and if so, how can I view a listing?
There's a misunderstanding here. What the documentation means is that as part of the Talend MDM product, the JBoss Application Server is shipped. So JBoss is a component (actually the core component) of Talend MDM. Not the other way round.
Talend MDM actually depends on the precise version of JBoss that is shipped with the product (it may even be modified here or there), so it is not possible to install Talend MDM into a different JBoss instance.
I want to use SqlLocalDB for my application. The application is deployed with WiX. Now, I am searching a way to install SqlLocalDB when my application is installed for the first time. How can I do that? Would it be enough to deploy some binaries with my application or do I have to install the whole SqlLocalDB.msi? - When installing of the whole msi is needed - how can I do this with WiX? - The goal is, that the result is a single msi-file which holds all what is needed for installing my application.
I'm not aware of a private deployment model for LocalDB. If WiX is your tool of choice, you'll need to use it's Burn bootstrapper feature to install LocalDB as a prerequisite. The result will be a single EXE that installs 2 MSI's.
I am running a VB6 with ActiveReports Standard v2 sp3. All of the sudden on one installation when creating a report the application shuts down. Eventually the system wants to report the error to Microsoft on actrpt2.dll Version 2.0.0.1252. If I copy the the clients database down on my machine it runs just fine. We have tried it on several machines. I have reinstalled the application. Reregistered the DLL. The client is using a terminal server running Server 2003. It is simply a columnar report.
I would have suspected a dependency issue for actrpt2.dll.
Check the dependency on your machine and do the same on the clients machine that this is failing.
For details on checking dependency
May be it is best to contact Grape City folks their forum is pretty active.
Update: if you are using win32 version of AR (not the dot net version of active reports).
Try dependency walker to check dependancy