- Error Setting Java_home Variable For P6 Suite Installer Software
- Error Setting Java_home Variable For P6 Suite Installer Free
- Error Setting Java_home Variable For P6 Suite Installer Windows 10
- Error Setting Java_home Variable For P6 Suite Installer Download
This tutorial shows you how to set a JAVAHOME system variable on Windows 10. Tested with: Windows 10; JDK 1.8; 1. Advanced System Settings. Type advanced system settings in the search box (beside the Windows start button), clicks View advanced system settings.
- Apr 27, 2019.
- After installing the JDK, you must set the following environment variables to ensure the P6 EPPM installation scripts can locate your Java libraries:. JAVAHOME. PATH Setting the Environment Variables in Microsoft Windows To set the JAVAHOME and PATH environment variables in Microsoft Windows:. Click Start, Control Panel, System,.
Prepare the Development Environment
This section provides a step-by-step guide to set up your development environment for AndroMDA. We assume that you are working on a Windows platform. Throughout this section you will install various programs. The recommended installation paths for these programs and other required directories are listed below. Please feel free to change the installation paths depending on your configuration and personal preferences. For example, you may choose to install programs on the D: drive instead of the C: drive. However, note that some programs don't work well if there are spaces in their pathname. So, try to stick to the suggestions below as much as possible.
![Windows Windows](https://i.stack.imgur.com/LvSGe.png)
Error Setting Java_home Variable For P6 Suite Installer Software
Recommended Path | Purpose |
---|---|
C:Programsm2repo | Maven local repository M2_REPO |
C:Programsmaven3 | Maven3 program M2_HOME |
C:ProgramsJavajdk6 | Java Development Kit JAVA_HOME |
C:ProgramsJavajdk6jre6 | Java Runtime Engine |
C:ProgramsMySQL | MySQL database server 5.6 |
C:ProgramsJetBrainsIntelliJ IDEA 9.0.2 | IntelliJ IDEA IDE (optional) |
C:ProgramsEclipse | Eclipse IDE (optional) |
C:ProgramsJBoss7 | JBoss v7 Application Server JBOSS_HOME |
You will also be asked to set up several environment variables. Please set these as SYSTEM variables using the Control Panel (Control Panel > System > Advanced > Environment Variables, or Computer > Properties > Advanced > Environment Variables). Note that if you change the installation path of any program then you must make sure that the associated environment variable is changed accordingly.
Install Java
Install J2SE Development Kit 6 (JDK 6) or newer from http://www.oracle.com/technetwork/java/javase/downloads/index.html. Libstdc mac. how to install boost libraries on xcode for mac. This is the preferred version of the JDK for AndroMDA. We also support JDK version 1.5. Support for version 1.4 requires a specific code generation configuration overriding the default settings, and changing to an earlier maven version and changing compiler settings.
Make sure that the JAVA_HOME environment variable is pointing to the directory where you installed the JDK. It is possible you have this variable set already, but just to make sure here's how to check.
- From a command prompt type echo %JAVA_HOME%. - OR -
- Go to the control panel and double-click on System. If you are a Windows XP user it's possible you have to open Performance and Maintenance before you will see the System icon.
- Go to the Advanced tab and click on Environment Variables
- Make sure you have set the JAVA_HOME variable and it is pointing to the directory where you installed the JDK. If not, add/edit the variable and set it to the correct value, e.g. C:ProgramsJava6. You may add the variable to the list of user variables or system variables.
Install Maven
Maven3 is our preferred tool for building and deploying applications generated by AndroMDA. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting, and documentation from a central piece of information. If you are familiar with Ant, Maven is very similar except that it contains additional functionality:
- A hierarchical build environment, where properties configured in a POM file (pom.xml) flow down to POM files of all child projects.
- Standardized build tasks (clean, build, install, deploy, etc.)
- Dependency specifications for build and deploy tasks - for all internal and external libraries; tied to a specific released versions of dependent libraries
- A repository containing all versioned dependencies. This repository is used during the build and deploy processes for all referencing projects.
Install Maven 3.0.3 by following the steps below.
- Click http://maven.apache.org/download.html and download Maven 3.0.3 or newer.
- Unzip this file at C:Programs. A directory called apache-maven-3.0.3 will be created which contains the Maven program. Rename to 'maven3'.
Note: If you are behind a proxy server, you will have to configure Maven to use the proxy. The details can be found below. Maven 2.2.1 or later will also work with AndroMDA.
Install JBoss Application Server
JBoss Application Server is a widely used open source Java application server. Install JBoss 7 by following the steps below.
- Download the desired version from http://www.jboss.org/jbossas/downloads.html. The TimeTracker sample works with the latest current version 7.0.2.
- Timetracker is also compatibile with JBoss 6.1, 5.1, Tomcat7, and GlassFish, with minor changes to be described later.
- Click on the download link for '7.0.2.Final' Everything Profile to download this file.
- Unzip this file at C:Programs. A directory called jboss-as-7.0.2.Final will be created which contains the JBoss application server. Rename this directory to JBoss7 (just to make the name a little shorter and to allow for multiple versions).
- If you are planning to install the Oracle database on your machine, then you must change the JBoss HTTP port, which defaults to 8080. The reason is that Oracle also defaults to this port and it is not easy to change Oracle's configuration. In order to change JBoss' HTTP port, edit the files called standaloneconfigurationstandalone.xml (on JBoss 6.1 or earlier defaultconfbindingservice.beansMETA-INFbindings-jboss-beans.xml and serverdefaultdeployjbossweb.sarserver.xml) and change all occurrences of the number '8080' to something else, say '9090'. This will resolve the conflict between JBoss and Oracle. If you have followed this step then you must use port 9090 whenever you are instructed to use port 8080 in this tutorial. If you are using JBoss5.1, use a utility such as WinGrep to search and replace all instances of 8080 with the new port, under serverdefault, for *.xml and *.properties (about 4 places).
- Test start the JBoss application server: cd %JBOSS_HOME%bin and standalone.bat. If using JBoss 6.1 or earlier, use run.bat. Make sure the default server starts without errors. JDK6 is required for JBoss7. If you see the error java.lang.NoSuchMethodError: javax.annotation.Resource.lookup()Ljava/lang/String; there is a JDK version conflict in the JSR250 jar, add the following to the JBoss command line: -Djava.endorsed.dirs=$JBOSS_HOME/lib/endorsed as explained in http://community.jboss.org/wiki/EJB31Embeddable
- Verify the JBoss Administration Console after starting JBoss: Open http://localhost:8080. Select the 'Administrative Console' link. Login with 'admin/admin'. The console will be used for adding/configuring databases other than the default H2 DB ExampleDS.
Setup environment variables
We have seen earlier how to set environment variables such as JAVA_HOME, it is strongly recommended to set the following variables before continuing. We repeat JAVA_HOME here just for completeness.
Property | Value | Required? |
---|---|---|
JAVA_HOME | Java installation directory, e.g. C:ProgramsJavajdk6 | Yes |
M2_HOME | Maven installation directory, e.g. C:Programsmaven3 (this may have already been set by the Maven installer) | Yes |
M2_REPO | Maven local repository, e.g. C:Programsm2repo | Yes |
MAVEN_OPTS | Parameters to pass to the Java VM when running Maven. Set this value to: -XX:MaxPermSize=128m -Xmx512m (required to build large maven projects such as AndroMDA itself) | No |
JBOSS_HOME | JBoss installation directory, if running jboss server e.g. C:ProgramsJBoss7 | No |
ANT_HOME | Ant installation directory, if running ant scripts from maven e.g. C:ProgramsAnt. Can set to eclipsepluginsorg.apache.ant directory. | No |
PATH | This makes sure the system will search for console commands in the directories listed here. If this property already exists you should simply add %JAVA_HOME%bin;%M2_HOME%bin;%ANT_HOME%bin | Yes |
Configure and Test Maven and create a local repository
Maven is based on the concept of a single local repository located on your machine, where it automatically downloads artifacts such as 3rd party libraries as well as components created by you. When you create a new project, you must specify a Project Object Model (POM) in a file named pom.xml. In this file, you can tell Maven about the various 3rd party libraries and components your application depends on. When Maven starts to build the application, it will first fetch these dependencies from one or more remote repositories (generally located on the Internet) and store them in your local repository. This allows future builds to happen entirely locally. By default, the local repository is located at C:Documents and Settingsyour user name.m2repository. Note that so far we have installed only the Maven application, we have not created a local repository. Follow the steps below to test your Maven installation and force the creation of a local repository. We will use a standard Maven plugin to create a temporary project which we will delete later. Maven3 and Maven2 share the same M2 environment variables.
- Edit %M2_HOME%confsettings.xml to use the Sonatype and JBoss repositories, and to download the andromda plugins. Include proxy settings if behind a firewall. This is described at Configuring Maven and Maven Settings
- Open a Command Prompt and change the current directory to any temporary directory, such as C:andromda-temp.
- Execute the following command to make sure you can run Maven: mvn -v
- Maven should display the following output:
- Now execute the following command to create a temporary project:Make sure that you get a BUILD SUCCESSFUL message at the end.Sometimes due to bad Internet connectivity, Maven may not be able to download all dependencies.If your build fails due to this reason, try to issue the command again until you get a successful build.
- Verify that Maven created a temporary project called testapp in the current directory and also a local repository at the %M2_REPO% location mentioned above.
Install AndroMDA Application plugin
Next we will download and install the AndroMDA Application plugin. This plugin allows creation of Java starter applications that use AndroMDA. All artifacts, such as AndroMDA cartridges, will be automatically downloaded by the Maven scripts generated by the plugin.
- Change to the temporary directory, e.g. C:andromda-temp.
- Edit pom.xml in this directory to add the following content:
- Open a Command Prompt in the directory where you edited this pom.xml and run the command mvn without any arguments. Make sure the command completes successfully by displaying the BUILD SUCCESSFUL message.
- You can now delete the temporary directory you created in step 1.
Install a UML tool
Install a tool that will allow you to model your applications in UML and export these models into a format that AndroMDA can understand. AndroMDA currently supports UML 1.4/XMI 1.2 as well as UML2 3.x/EMF/XMI2. Please follow one of the links below to install the UML tool of your choice. (We invite UML tool vendors and open-source projects to test their tools with AndroMDA and supply installation instructions for inclusion in this section.)
ArgoUML (UML 1.4/XMI 1.2)
MagicDraw 9.5 (UML 1.4/XMI 1.2)
MagicDraw 11.5 through 17 (EMF-UML2 3.x)
RSM 7, 7.5, 8 (Rational Software Modeler/Architect) (EMF-UML2 3.x)
Eclipse Papyrus (EMF-UML2 3.x)
MagicDraw 9.5 (UML 1.4/XMI 1.2)
MagicDraw 11.5 through 17 (EMF-UML2 3.x)
RSM 7, 7.5, 8 (Rational Software Modeler/Architect) (EMF-UML2 3.x)
Eclipse Papyrus (EMF-UML2 3.x)
Install a database
Install or download a database that is supported by Hibernate. Click http://www.hibernate.org/260.html to see the list of supported databases. For the purpose of this tutorial we assume that the H2 database will be downloaded automatically and configured by maven as part of the build process. If you have installed another database then you will have to change the AndroMDA Hibernate configuration accordingly in the completed application pom.xml.
- H2: H2 is an open source in-memory java database, the successor version of HSQL. You can download it from http://www.h2database.com or automatically through maven. This database ships with JBoss 7 and is often used for unit testing. It features compatibility modes with most major DBMSs such as mySQL, Oracle, DB2, SqlServer.
- Hypersonic SQL 2.0: HSQL is an open source java database. You can download it from http://hsqldb.org. This database ships with JBoss 6.1 and earlier.
- MySQL 5.6: MySQL is an open source database, owned and supported by Oracle. You can download it from http://dev.mysql.com/downloads/mysql. We recommend downloading the full Windows installation - not just the 'Essentials'. In addition, download and install MySQL Workbench, a GUI based tool that will make your development much easier. Finally, download and unzip MySQL Connector/J (the MySQL JDBC driver) in a convenient directory. For the purpose of this tutorial we will assume that you have installed the driver at C:ProgramsMySQLmysql-connector-java-5.1.18. Or - you can wait until running mvn after creating the timetracker project, which has a dependency on mysql connector. Copy the MySQL driver from C:Programsm2repomysqlmysql-connector-java5.1.18mysql-connector-java-5.1.18.jar to the JBoss lib directory located at C:Programsjboss7serverdefaultlib. This allows JBoss to access your database.
- PostgreSQL 8.1: PostgreSQL is an open source database. You can download it from http://www.enterprisedb.com/products/pgbindownload.do. The Postgres installation contains a GUI based administrative tool called pgAdmin III. JDBC drivers are also included as part of the installation.
- Oracle: Oracle 11g is an commercial database sold by Oracle. We assume that you have the necessary distribution media to install it. Oracle 11g includes a GUI based administrative tool called Enterprise Manager. JDBC drivers are also included as part of the installation, or as a separate download. The Express edition is free to use.
Install Eclipse (Optional)
Eclipse is a popular open source IDE that is useful in developing Java applications. AndroMDA does not require the use of Eclipse. However we do recommend using it for development as it helps increase your productivity. Eclipse users will glad to know that AndroMDA generates fully usable .project and .classpath files, or you can use the Sonatype M2E Eclipse plugin to manage your maven projects. You can download Eclipse from http://www.eclipse.org/downloads. We recommend downloading the Eclipse Indigo (v3.7) Package called 'Eclipse IDE for Java EE Developers'. Follow the steps below to install and configure Eclipse:
- Unzip the downloaded archive to a suitable location on your hard drive. The recommended location is C:Programseclipse.
- Edit the file eclipse.ini under C:Programseclipse to increase the memory available for Eclipse. Here are the suggested contents for this file:
- Start Eclipse by double-clicking on eclipse.exe.
- Eclipse asks for a folder where it can store your projects. This folder is called the Eclipse workspace. Set the workspace to a location where you generally creates projects, such as C:Workspaces.
- Choose Preferences from the Window Menu.
- In the left pane, select Java > Installed JREs
- Add the JDK6 from the JAVA_HOME directory, and make it the Workspace default.
- In the left pane, select Java > Build Path > Classpath Variables.
- Click New.
- Add M2_REPO in the Name field and the path of your M2 repository in the Path field (for example, C:Programsm2repo). This value is needed in order to import Maven generated project configurations.
- In the left pane, select Server > Runtime Environments > Add > Jboss v7
- Click OK twice to close the dialog boxes.
- Create a new JBoss server instance (Window > Show View > Other > Servers > Server) and start the instance from Eclipse.
- We recommend the following plugins also be installed:
Plugin | Repository or Download Location (* = Manual install) | Notes |
---|---|---|
Sonatype M2E | http://download.eclipse.org/technology/m2e/releases | Import maven projects, run maven from Eclipse. See http://wiki.eclipse.org/M2E_FAQ |
SpringSource Tool Suite | http://dist.springsource.com/release/TOOLS/update/e3.7 | Install instructions at http://download.springsource.com/release/STS/doc/STS-installation_instructions.pdf |
JBoss Tools | http://download.jboss.org/jbosstools/updates/development/ | If using JBoss server or Hibernate ORM. Only Dev releases are available for Eclipse 3.7. Install instructions at https://www.jboss.org/tools/download/dev.html |
PMD | http://pmd.sourceforge.net/eclipse | Code quality checker |
CheckStyle | http://eclipse-cs.sourceforge.net/update | Code quality checker |
FindBugs | http://findbugs.cs.umd.edu/eclipse-candidate | Code quality checker |
Cobertura | http://ecobertura.johoop.de/update | Code unit test coverage |
SVN | http://eclipse.svnkit.com/1.3.x | If using SVN repositories, integrate with Eclipse Subversive |
Velocity | http://veloedit.sourceforge.net/updates | If editing Velocity templates |
This topic guides you through installing the Discovery Module on a single computer under the Windows operating systems. It's intended for system administrators and application developers.
- About Discovery Module Installation
About Discovery Module Installation
Advanced features discussed here work with Logi Info v12.5. Earlier and later Info versions may not support them; consult the Release Notes for specific details. How to set up toshiba canvio connect ii for mac.
The Logi Discovery Module (DM) provides an embedded data discovery experience that works directly with relational data sources using Logi data services. It does this by making several special elements available in Logi Studio. These include the Thinkspace element, which provides a highly-interactive analysis experience. In its interface, best-fit visualization suggestions are automatically referred to the user by a built-in 'recommendation engine' and data is organized using intelligent technology that clusters data to make it more easily consumable by users.
The DM is installed separately, after Logi Info and, if using it, the SSRM are installed. Please note these important restrictions:
- Logi Info: v12.5 or later, 64-bit version (there is no 32-bit version available).
Databases supported include:
- AWS Redshift
- Infobright
- JDBC database providers
- MS SQL Server
- MySQL
- Oracle
- PostgreSQL
- Snowflake
- Vertica
Logi Info applications on IIS that utilize DM v3.1+ must run using an Application Pool configured for Integrated pipeline mode. Classic pipeline mode Application Pools will not work.
If you're using Internet Explorer 11, the Internet OptionsSecurity setting for applications using this technology must be set to Medium High or lower.
Important Java Information
Starting in January 2019, Oracle discontinued its free, long-term support of the Oracle Java Development Kit (JDK) for enterprises. The impact of this on Logi products is discussed in detail in Java Usage Policy .
As a result, Logi no longer distributes the Oracle JRE as part of the Discovery installation. Prior to installing Discovery 3.2, you must have OpenJDK 12 installed; Oracle JRE is not supported.
When you install OpenJDK, you must configure your Windows System Variables properly. See this section for more information.
What Gets Installed
The following components will be installed on the web server:
- An embedded, runtime environment for server-side web applications (node.js)
- An embedded, Java-based relational database (H2)
Error Setting Java_home Variable For P6 Suite Installer Free
Node.js and H2 are extremely compact, have a small installation footprint, and do not install a lot of extra tools or management utilities. They're provided as transparent services that require little or no management.
Two Windows services are created during the installation: Logi Application Service and Logi Data Service.
Important Upgrade Information
If you're upgrading from earlier versions of Discovery, please uninstall the earlier version first, using Control Panel, and at the end of the process be sure to respond 'Yes' when prompted to remove logs and the database. Then run the Discovery 3.1+ installer to create a fresh installation.
Release Pairings
Information about which Logi Info and DM versions should be used together is available inIntroduction to Add-on Modules . For more information, see the Release Notes for each Logi Info version.
Product License
Unlike previous versions, DM v3.1+ requires its own license. The installer will provide a built-in 15-day trial license. You don't need to do anything but install the product and you can begin using it immediately. After the trial period expires, you will not be able to use certain DM functions, such as authoring Dataviews and saving Thinkspace visualizations.
Licenses are keyed to you or your organization; they take the physical form of license files, which are assigned to a specific computer. DevNet includes a License Management page where you can manage your licences, including reviewing them, assigning and un-assigning them to machines, and generating license files, at any time, without any interaction with our staff. For more detailed information about licenses, seeProduct Licensing .
You may not use our products for redistribution with, or embed them in, other products without an OEM license; contact our Sales group for more information if you need OEM licenses.
Preparing to Install
Logi Info must be installed and licensed before the DM is installed. After the DM is installed, you'll also need to acquire its separate license file.
It's critical that installation and configuration occur while running as the built-in 'Administrator' account.
Even if your personal account has been added to the local Administrators Group, it may not have sufficient privileges, so don't rely on it.
As shown at left, on Windows the correct practice when running the Logi installer or using the Command Line to make configuration adjustments is to start the tool by right-clicking its icon and selecting 'Run as administrator' from the menu to start the program.
This ensures that appropriate permissions are provided for the installed components.
Don't see a 'Run as administrator' option? If the system is in a network domain, your network admin may have created security policies that don't allow you to see this option, in which case you need to consult your IT staff for assistance.
Installing the Software
As usual, you can click Back at any time before the physical installation begins to go back to the previous screen.
- To start the installation, right-click the Logi product installation file icon and select 'Run as administrator' to launch the installer. When the Welcome Screen appears, click Next.
If you see the dialog box shown above, click No and the installer will close. Uninstall the existing DM version and then re-run the DM v3.1+ installer.
- License Agreement: Select the 'I accept the agreement' radio button after reading the license agreement and click Next to continue.
- Java Acknowledgement: Next, if you have OpenJDK installed, you'll see the screen shown above. If you don't, an error message is displayed, along with a link to download OpenJDK. If you have it installed but haven't set the related Windows System Variables, an error message is displayed. You must install it before proceeding.
If the link in the window does not resolve correctly, you can go here to get OpenJDK12: JDK12 Download from Archive.
Click Next. - Dataview Authoring Credentials: (Not shown for upgrades) Provide the required information for the default Dataview Authoring 'admin' user, as shown above. Click Next to continue.
Error Setting Java_home Variable For P6 Suite Installer Windows 10
- Installation Directory: Click Next to accept the default installation location and continue. Optional - click the Folder icon to specify an alternative installation location if you don't like the default location.
You may not install directly to the root folder of a drive, i.e. C: and if you specify a custom installation directory, the folder names in the path must not contain spaces. For example, this path is not valid: C:Program FilesDiscovery.
In addition, the length of the path must not exceed 260 characters.
- Ready to Install: Click Next.
- The physical installation will begin and you'll see a progress indicator for different tasks.
- Installation is complete: Click Finish to exit the installer.
Customizing Service Settings
You may wish to customize Logi services settings which, assuming a default installation location, can be found in these files:
<installationFolder>platformsettingslogiApplicationService.json
<installationFolder>platformsettingslogiDataService.json
<installationFolder>platformsettingslogiDataService.json
The beginning of the logiApplicationService.json file looks like this:
{
'disableSchemaValidation': false,
'logiApplicationService': {
'description': 'Platform logiApplicationService Configuration',
'logLevel': 'error',
'corsOriginWhiteList': '*',
'accessTokenGracePeriod': 120,
'system': {
'pollingIntervalSeconds': 15,
'pollingTimeoutMinutes': -1
},
'disableSchemaValidation': false,
'logiApplicationService': {
'description': 'Platform logiApplicationService Configuration',
'logLevel': 'error',
'corsOriginWhiteList': '*',
'accessTokenGracePeriod': 120,
'system': {
'pollingIntervalSeconds': 15,
'pollingTimeoutMinutes': -1
},
For example, the required corsOriginWhiteList attribute, highlighted above, specifies which servers the service will respond to, allowing you to restrict access to the service, if desired. The default value, '*', tells the service to respond to all servers; to restrict access enter a single IP address or server name (as a string) or a JSON array of them, such as:
['http://server1','http://server2','http://192.168.1.1']
Caution: Changes to some settings may cause applications to fail. For example,
changing the platformBaseUrl setting, shown above, may cause integrations with Logi Info applications to fail.
You'll need to stop and restart both services to have any changes to the settings file take effect.
Setting Windows System Variables for OpenJDK
There is no installer for OpenJDK. You download and unzip its files and place them on your machine, then configure System Variables to point to them, as follows.
These examples assume you've place the unzipped OpenJDK folder in C:tools.
Error Setting Java_home Variable For P6 Suite Installer Download
Navigate to the Environment Variable manager in your OS and add the path for the OpenJDK bin folder to the Path system variable, as shown above. Be sure to add the reference to the OpenJDK folders at the top (front) of the Path string, as shown.
Next, create/set the JAVA_HOME system variable to the path for the OpenJDK bin folder, as shown above. The Path variable from the previous step has been highlighted for reference.
Click OK to close any related open windows.
Test your variables by opening a Command window and entering:
echo %Path%
echo %JAVA_HOME%
echo %JAVA_HOME%
Removing the Installation
You can remove the DM completely by selecting it in Windows' Control Panel applet, Programs and Features, and clicking Uninstall/Change:
Click 'Yes', as shown above, when prompted to uninstall the product, and 'Yes' again if prompted to remove logs and database files. If JRE 8 was installed as part of the DM installation, it will be uninstalled, but if you had JRE 8 installed prior to installing the DM, it will not be uninstalled as part of this process.