is it possible to change the cuba configuration to start tomcat server in a windows power shell window and not in a dos window?
regards
Karl
You can create a shell script that will be invoked instead of cmd.exe /c ... when Studio starts the application server. The path to the script should be specified in the CUBA_TOMCAT_START_SCRIPT environment variable.
See the CUBA Gradle plugin code for details.
Related
I have download the .iso file to install the SQL Server . I want to automate the process of installation on windows server using powershell script so that i can run those scripts in multiples machines.
I have searched online but didn't find any good material to do so from scratch.
I am a beginner in powershell.Can anyone provide a sample script to do so?
Tried this answer on Stackoverflow but didnt get it>
Install SQL Server using PowerShell
AFTER you have mounted the ISO file you can install SQL Server:
From cmd passing parameters. Installing a new instance of SQL Server at the command prompt specifying the features to install and how they should be configured.
From configuration file. SQL Server Setup provides the ability to generate a configuration file based upon the system default and run-time inputs. You can use the configuration file to deploy SQL Server throughout the enterprise with the same configuration. You can also standardize manual installations throughout the enterprise, by creating a batch file that launches Setup.exe.
I am setting up a process to build remotely a suite of COBOL programs. A virtual machine has Visual Studio 2017 installed along with a Micro Focus COBOL Enterprise Developer 4.0 Visual Studio 2017 plugin. The programs use CICS as their UI and work with a Microsoft SQL Server backend. Opening a developer command prompt in Visual Studio and issuing a MSBuild command with the solution as the parameter successfully builds the programs. A remote build does not - the error is
MSBUILD : error MSB4025: The project file could not be loaded. Root element is missing.
any ideas?
You need to install the "Micro Focus Enterprise Developer Build tools" on the CI machine.
I am wondering the correct way to navigate to a dtsx package deployed on my SQL Server. While creating the action, so far I ave the Program/script to open SQL.
"CD\C\Program Files (x86)Microsoft SQL Server\140\Tools\Binn|ManagementStudio\DTExecUI.exe"
My issue is finding the path to the package that is deployed. What arguments can I add to continue navigating through the packages in the ssis catalog?
First of all, i think that it is better to work with SQL server agent to schedule a ssis package job
To run a package from a server using Task scheduler, you can use DTExec utility.
example
dtexec /ISServer "\SSISDB\Project1Folder\Integration Services Project1\Package.dtsx" /Server "localhost"
References
Run an SSIS package from the command prompt with DTExec.exe
Scheduling SQL Server Integration Services Packages.
dtexec utility
Usin dtexec with package on IS Server
I have a deployment script & I have to give it to operations team to deploy ADLA & add Azure Storage data source to ADLA.
This command works well on my local machine as well as our development vm.
Operations team facing issues with this command. The command Add-AdlAnalyticsDataSource not found. They are using plain windows server virtual machine for deployment having Powershell version 3.4.0
Are we missing anything?
#Rohi_Dev_1.0 What is the Windows Management framework installed on your machine?
This can be checked using $PSVersionTable command.
If the PSVersion is below 5.0, then Install-Module command won’t be available in showcommand window
Maybe we should upgrade your Azure PowerShell version to 4.3.0, here is my PowerShell output, it works for me:
If you want to upgrade your PowerShell version, we can download PowerShell installation package from this link.
So if I made a VB.NET normal windows.form application and then booted into ms dos mode, i am able to run notepad and taskmgr but any normal exe file will just give me an error saying it can't be run in MS DOS mode. Is there a way I can make it compatible with MS DOS environment?
If by "MS-DOS " you mean "command Line" then you can mark your Project as a "Console Application" when you create it in visual studio. This should enable it to run in the command line.
If by "MS-DOS" you mean the 20 year old operating system by Microsoft, it cant be done.