When installing SAP Netweaver there was a step to specify the SAP installation export. I want to know what these files contain and what they are used for.
the installation export contains the actual application that is supposed to run on the netweaver platform. This could be SAP ERP, SAP Solution Manager or something else. It is probably called "Export" because technically it is an export of a functioning application environment. If you for instance move your Netweaver installation to another server, you export your application on the old server and import that Installation Export when installing your new netweaver server. For new installations, this installation export is downloaded from the SAP Support website.
Related
I have developed an application in qt and connected a database to it by SSMS Express. How can I deploy this program so that this data is available to the program when installed on another computer?
You should Export your DB
then you should put db file near Exe File that you want to deploy.
watch this youtube video :
https://www.youtube.com/watch?v=hCXAgB6y8eA
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'm getting the message "Logging: Couldn't initialize from PropertyFile; activating fallback ..." on a fresh install of Domino 9.0.1 FP8 with the latest OpenNTF Domino API 4.0.0. There's another question with the same issue, but the solution was a fresh install.
After the Domino install we created the updatesite.nsf, imported the OpenNTF Domino API 4.0.0. Clicked, Action, Sign All Content, then added the OSGI_HTTP_DYNAMIC_BUNDLES=updateSite.nsf to the notes.ini and rebooted the server.
With a little more digging it seems the IBM_TECHNICAL_SUPPORT/org.openntf.domino.logging.logconfig.properties file is missing from the OpenNTF install or not being created.
There are no applications running on this server, other than the basic Domino default applications you would have from a fresh install.
Also, this isn't a fresh re-install. This is a brand new Win 2008 R2 server with a new Domino 9.0.1 FP8 install.
I'm working on a project where the client Company has one Enterprise SQL Server license and its box is highly exclusive. I need the Enterprise version because the package uses fuzzy lookups.
So I want to trigger the launch of the package remotely from some VB.Net code. I can't use the DTS Runtime library because they require the calling box to be running the Enterprise version too; besides Enterpise is version 2012 while everywhere else is SQL 2008 R2. I can't install either a web service or a Windows Service on the Enterprise machine to call an SSIS package because the client won't let me. I could create a job but I don't know how to trigger it on-demand.
I've read that Powershell is the answer but the script I've written generates an invoke command that runs DTExec which doesn't work as again I don't have the Enterprise version installed locally. Can anybody point me to the solution? I've looked and looked and all I find is variations on what I've already tried and know won't work.
Cheers
I have a VB.NET application that uses a .accdb access file (2010 version) as a backend. The application only reads from this DB file, no writing ever. The application and database file need to be deployed together on the user's PC.
I understand that users will need either:
1) Full version of Access installed already or
2) The runtime installed
in order for the application to run.
That's fine and dandy but my problem is that the AccessRuntime.exe is HUGE (175 MB) and I would rather not deploy it with my app if I don't have to. Is there a way to just deploy the needed Runtime DLLs/files with my VB app and DB file? If so, what/where are these files located?
If your .NET application will just be reading the Access database file via System.Data.OleDb or System.Data.Odbc then you don't need the Microsoft Access Runtime. You just need to have an Access database engine installed, either
the older "Jet" database engine, if you only need to access .mdb files from 32-bit applications, or
the newer "ACE" database engine if you need to access .accdb files (or .mdb files from a 64-bit application).
Since your database apparently does not need any specific Access 2010 features you can just convert your .accdb file to an .mdb file and use the "Jet" database engine that is already installed on all Windows machines. However, Jet is only available to 32-bit applications so you need to go into your VB.NET project and target it to the x86 platform so it will always run as a 32-bit application (even on 64-bit machines).
Edit
If you want to manipulate an .accdb database file then you need to ensure that the Access Database Engine ("ACE") is installed on each machine. The installer is available for download here:
Microsoft Access Database Engine 2010 Redistributable
Notes:
There are both 32- and 64-bit versions of the ACE database engine. The installed version must match the "bitness" of your application (32-bit or 64-bit). This can be tricky, because Microsoft has designed the ACE installers so that you can have either the 32-bit or the 64-bit version installed. (There is a workaround that can force-install both, but it is not recommended because it can break Microsoft Office.)
Further to point #1, so even if you target your .NET app to the x86 platform and require the 32-bit version of ACE you can still have difficulties dealing with target machines that already have the 64-bit version of Office installed. They cannot install the 32-bit version of ACE because the 64-bit version is already installed. So, to use your app they would have to uninstall the 64-bit version of Office and install the 32-bit version.
As far as I know there is no practical way to include the ACE installer in the setup program for your application. Your users would need to download and install the appropriate version (from the link above) for themselves.