Move file from Linux to windows server - talend

I'm using Talend ETL tool.
What I'm trying to do is moving file from Linux machine to windows server and back to again to linux server after some work on that.
Is that possible we could achieve using Talend ?
Any suggestion or help would be appreciated.
Thanks !!

Assuming the Talend job is running on Linux and the remote file server is Windows and the remote file server is not running an SFTP or FTP server.
To copy from a Windows system to local system, you can use the built in component tFileFetch, which can copy files from a Samba share.
To copy files from Linux (Talend Job server) to the Windows file server, you'll likely need a third-party component. Look in the Talend Exchange site for the components "Samba copy", tSambaPut, tSambaFileCopy, tSambaGet, etc.
Alternatively, you could put an SFTP or FTP server on the Windows server. Then, it becomes very simple and you can just use the tFTP* series of components.

Related

Visual Studio Code remote access to a WSL2:ubuntu on my desktop from my macbook

've looked around and can't seem to find the answer to this - probably because the feature is pretty new.
I tried the remote WSL:ubuntu connection on my windows desktop machine to connect to my WSL2 Ubuntu running on the same machine. This is pretty much perfect as it allows access to my Nvidia GPU under linux
Is there anyway I can do the same trick from my macbook? I can connect to the windows side of the desktop using the new remote tunnel feature but I'm drawing a blank on how to do for the WSL buried in that machine. It looks like it's just using the same remote connection feature so I'm thinking it should be possible but WSL2 network is not exposed the same way you can with a VM or other machine.
The desktop has way more everything than my macbook including a nvidia GPU I want to use for some machine learning.
I can do it from the desktop itself - but it's nice to be able to use that machine from my macbook at certain times of day.
I have recently started using VSCode so I'm on the learning curve with it - it may well be that it's not possible using the new remote tunnels - or requires some messing with adding a new hyper-v bridged adapter to the WSL installation. I'm hoping against hope there's an easy solve that I've somehow missed.
I tried setting up the remote tunnel as per https://code.visualstudio.com/blogs/2022/12/07/remote-even-better but it seems to setup a server to access windows not the WSL2 service.
Thanks for any help!
I had a similar problem and found this github issue. While the developers are looking into including this feature, you currently will need to install the VSCode CLI directly in WSL. You can find the downloads here
Notes
I would recommend the x64 CLI download in the Linux section. It will download a tar.gz file which will have a file named code in it when extracted.
The tunnel will launch from wherever you place that code file, so I put mine in the ~/ (home) directory.
You can then open a tunnel using the command ./code tunnel from that location. You can replace the . with the path to the code file to open the tunnel while in a different directory, i.e. ~/code.
You can still launch a tunnel from Windows with code tunnel. (note that this command does not have ./)

How to upload files to LEMP stack on Microsoft Azure Virtual Machine?

I'm new to the whole cloud computing virtual machines thing, and I just started my free trial of Microsoft Azure. I'm interested in setting up a web server running Nginx to host some PHP pages that connect to a MySQL database. I just followed this official tutorial on how to install a LEMP stack on a Linux virtual machine in Azure, but it doesn't give a whole lot of instruction after that. How do I upload my files to this newly created web server?
There are many methods that you can upload files to your Azure Linux VM, Here are two options for you:
Move files to and from a Linux VM using SCP. In this way, you need an SCP client for your local computer. It is built on top of SSH and included in the default Bash shell of most Linux and Mac computers and some Windows shells.
Create An Azure File Share and mount to your Azure Linux VM. In this case, you will create a storage account, then mount the Azure file share on your Linux VM. It's better used for multiple clients to upload the files to Azure VMs.

Eclipse remote project stored also locally

I am working on a project, on a windows laptop, which is connected via RSE plugin to the linux server (can be run/tested only there).
So I have only a logical SSH link on my laptop, no actual files. Is it possible to somehow have project stored both on local and remote side? (so that both project are in sync)?
The problem is that the linux server is used for labs/experiments by other employees and its files can be removed any day. Now I'm making manual copy to my local machine at the end of each day, and it's really cumbersome.
Of course I don't have to use RSE if there is any other plugin that can satisfy my needs.
Thanks.

MSBuild deployment to machine outside of company network

Is it possible to deploy code (asp.net mvc application and Windows Service) to machine in public hosting (for example VM on Godaddy) using TFS MSBuild from internal network (company network)
All than I have is IP address of destination server, username and password. But I am not sure than TFS can deploy code at such machine.
When I doing it on local server, normally I specify path like this:
\machine-name\c$\deployment-folder\
But it is not working with remote machine.
Thanks.
Use a tool like InstallShield or Windows Installer XML to develop a Windows Installer database (.msi). Use TFS Team Build to build the MSI. Then use PsExec to copy the MSI to the remote machine and execute it.

Deploy files on a network share from a client machine using an installation package?

We have a large application that has been developed over 15 years and in installed in 200+ client locations. The application currently consists of an Access database and a bunch of executable and report files located on a network share. A Setup.EXE file is run on each client machine (dlls are installed on the client) and then the client machines run the executables directly from the network share. During our upgrade procedure the new executable and report files are copied to the network share and that way each client gets the update immediately.
Our current installation program is very old and, among other things, it doesn't handle x64 so we are in the process of moving to a new deployment tool. At the same time we are migrating client Access databases to SQL Server. I am having difficulty finding a deployment tool to do what we require. Specifically we need the install/upgrade file to do the following:
It must be able to be run from a client machine on a network and copy the new executable and report files to the network share. That share could be a Linux box or a dumb storage device.
Accept a password before running the installation
Allow the user to select the network share as the location to copy the executables
It must NOT add anything to the client machine from where the package is run (Add/Remove Programs, registry, etc.)
Connect to a SQL Server database and run a script
The install/upgrade must be contained in a single, standalone .msi or .exe file. (no dependencies on dlls or frameworks other than those that come with Windows XP)
The file must be able to be run in one simple step. It is the end user that runs the upgrade without our support and without involvement from IT.
It looks like the closest thing to what I need is WiX but the problem there is that whenever the .msi file is run from a client, the client machine thinks that a program is being installed so it allows the client machine to uninstall the product, which is not acceptable.
If the product were written today it would certainly be architected differently but it currently is what it is and we can’t change that. Any help here would be greatly appreciated!
WiX is just a toolset built on top of Windows Installer technology. It makes many things easier and simpler as well as hides lots of Windows Installer weird features... But, it is still limited by Windows Installer, its underlying technology.
Your list of requirements made me think that Windows Installer is not the right technology to choose. I would assume that you'll spend more time on workarounds, than on functional code... But I have no experience with other installation technologies, so I'll leave those recommendations to others.