How I will log in in pentaho data integration after installation on windows - pdi

I have installed pentaho data integration. I don't know from where I will take start, I mean where I should click to run the application in the installed folder.

In the installation folder you can run the spoon.bat file which will launch the application. It will then ask you to select a repository, which you can then select by browsing to the folder you wish to use as your repository, or press cancel to skip that step and not use a repository.

Related

How to install extension on server in yii2

I have an website running on server.
I want to use graph extension to show some reports.
How do install extension on server?
Locally I can use cmd for that, do I need to download project install extension and upload it again?
You have to enable SSH access on your server.
DigitalOcean SSH tutorial - here you can find some helpful informations about SSH connection.
If you connect by SSH, navigate to project directory and use composer install or composer update.
If you don't have a command line access to your server and so cannot use composer directly, I would recommend to do prepare the code locally in a 'deploy' folder and then copy the whole folder content, including the vendor directory, to the server. I assume that you can use composer locally, so that you can install the extension regularely . And I assume that the local machine and the server does differ to much (PHP version, other settings).
Installing the yii2-extension does mean: if you install it with composer install Yii gets prepared so that you can use the code like any other code in your application. Installing the extension creates an entry in `vendor/yiisoft/extension.php which gets evaluated each time the application gets loaded.

Creating installer with multiple support files

I currently have a program that uses Qt, MySql, and MS Visual Studio 2010 compiler. I want to create an installer that can be put on a fresh computer, and when opened, it will install my program plus all the needed files from the others.
I don't know if it matters but I followed this blog to install the files in the first place: http://eraden.blogspot.com/2013/05/my-fight-with-qt-5-and-mysql-drivers.html
Is there any way for my installer file to first run through the steps to install the support files, then have it install my program in such a way that the program has all the files it needs?
Thanks in advance,
-Duncan
You need to add the resources as prerequisites to the main package, this will make them install before your application, so the system is ready to launch the application when the installation is done.

How to Integrate MYSql in C# Setup Project?

I want to install MySql and Database File while installing the Setup File,
which is developed in C#.
simply, while installing the setup file only everything needs to be installed
(MYSql,Database File)
So, please guide me on this.
You can set Custom Launch Options to the Setup file. Add the necessary executibles in the Commit node of the setup file and those will get executed when your installation finishes.
As for installing entire MySQL, you would need to add the installation files of MySQL to the Setup project. Executing the Database Script would be simple, just call the script after MySQL installs.

How to setup a box and 3 machines as a web development environment for a small team

Extended title: How to setup a box with (Windows7 + Apache + VisualSVN + MySQL + PHP) and 3 machines with (MacOs/Windows7) and Dreamweaver CS5 as a web development environment for a small team
These are my thoughts. Please forgive my ignorance, I still don´t have completly clear all the concepts.
1. I need to setup a web development environment for a small team of 3 web developers. The staging and live environments will be in a remote server under an external hosting company (probably Amazon).
2. Our first project is a blog with Wordpress
3. I've installed XAMPP in the box and can be accessed like this (http://dev.company.com/xampp)
4. I've installed Wordpress and can be accessed like this (http://dev.company.com/blog)
5. I've installed VisualSVN in the box and can be accessed like this (http://dev.company.com:8080/svn)
6. I don´t know how to import files for the first time to my repositories in the box (c:/repositories/blog)
7. VisualSVN includes Apache. I don´t know if I should turn off the Apache of XAMPP or if should install another version of VisualSVN without Apache
8. I don't know if I should keep my repositories at C:\repositories or c:\xampp\htdocs.
9. I've read something about hooks? to copy the files from the repositories to the htdocs? Can anybody explain this process?
10. Would it be a good option to keep all the files always in the box? or it is a better option to check out the files to the machines?
11. When setting up Dreamweaver to connect to the SVN Server, do I have to point to the trunk, branch or the name of the repository? Do I have to setup a different connection for each branch?
12. How can we include images and PSD's in the repositories?
When we start a new project we usually just checkout files on clients and commit the changes to the server when finished editing. This way people can just edit files on their own machine (without other users slowing stuff down).
Can't you just do a Linux install for the webserver (CentOS or something like that?). Windows 7 seems so heavy / unfitted for webdevelopment server.
We usually keep the repo out of the webroot.
XAMPP really???
Just my two cents...
It's strongly not recommended to use Apache HTTP server bundled to VisualSVN Server for anything else than Subversion server. So you have to install VisualSVN Server and XAMPP.
Just keep repositories in C:\Repositories. If you move them to htdocs all repository will be accessed for everyone who have access to XAMPP.
Common practice is to checkout working copy to htdocs folder, configure permissions to deny access to .svn and then run svn update in post-commit hook in VisualSVN Server.

Microsoft Access 2002 Package Deployment Problem

I've created a split Access database application and used the packaging wizard to create a deployment package. All the files are installed by the deployment package into C:\Documemts and Settings\All Users\Application Data\Provision Manager, this is too avoid Windows Vista not allowing write access to the Program Files directory.
The application installs OK on both Vista and XP and creates a Provision Manager entry in the Program Group in the user account that installed the application, however when I login using another account (both Admin and non-admin ones) the there is no Provision Manager item listed in the Program Group.
Can anyone enlighten me as to what is going on here and more importantly how I can ensure that the deployment package creates a Program Group item for each user account.
Thanks
Marc
To ENSURE that the package has created the right Program Group, look in All Users/Start Menu/Programs because these programs are automatically placed in every user's Start Menu when they log in. Similar for Desktop shortcuts, place them in All Users/Desktop
The fundamental problem (and it's not really a problem but a feature) is that MS tightened up security in Windows Vista. Users are no longer allowed to update the All Users Start Menu/Programs or Application Data folder. Only administrators can update such as using instllers. Now that's mostly fine for the shortcuts to Access FEs. The real problem arises with the FE MDB/MDEs as users pretty much have to have read/write/create/delete (although strictly speaking create/delete privilieges are only required for LDB files.) So those can't be installed into the All Users folders.
The solution is to split the runtime install into two components. The administrator types install the actual Access runtime into Program Files along with msaccess.exe , etc, etc.
Then you have a second install with the users can run which puts the Access FE MDB/MDE, and other files in the Current Users Applications Data folder along with shortcuts on the desktop.
If the users are on your local LAN you could use the free Auto FE Updater utility to handle the FE installation for users.
If the users are remote then you can use the Sample inno script which checks to see if a version of Access is installed. If not it tells you to install a runtime version of Access. If installed then it continues to install your FE MDE and other assorted files.
http://groups.google.com/group/microsoft.public.access/msg/10e3fc9234660872?hl=en
Sample inno script which "wraps" the package wizard install into a single .exe
Deploying updates to your software in a Runtime environment for Access 2007