Appboard/old/windows installation: Difference between revisions
imported>Mike.berman (created page) |
imported>Mike.berman (update language to reflect dual use for AppBoard and enPortal applications) |
||
Line 1: | Line 1: | ||
This section provides instructions for installing AppBoard on a Windows Server. It also details how to create a service that will automatically start AppBoard when the server is booted. | This section provides instructions for installing AppBoard/enPortal on a Windows Server. It also details how to create a service that will automatically start AppBoard/enPortal when the server is booted. | ||
== Install AppBoard == | == Install AppBoard/enPortal == | ||
To install AppBoard, perform the following steps on the | To install AppBoard/enPortal, perform the following steps on the server: | ||
Line 16: | Line 16: | ||
## Note: Make sure JAVA_HOME does not end with "\" and is not surrounded by quotes. It is also recommended that JAVA_HOME not contain spaces. | ## Note: Make sure JAVA_HOME does not end with "\" and is not surrounded by quotes. It is also recommended that JAVA_HOME not contain spaces. | ||
# Extract the turnkey installation file to any desired location on the server | # Extract the turnkey installation file to any desired location on the server | ||
# Save the license file into [ | # Save the license file into [INSTALL_HOME]/webapps/enportal/WEB-INF/config/license.properties | ||
# If you are running a 32-bit version of Windows, perform the following additional steps: | # If you are running a 32-bit version of Windows, perform the following additional steps: | ||
## Navigate to [ | ## Navigate to [INSTALL_HOME]/server/bin/windows-x86 and copy the 32-bit Tomcat files from the /windows-x86 folder up one level to replace the default 64-bit versions in the /bin folder: | ||
### tcnative-1.dll | ### tcnative-1.dll | ||
### tomcat7.exe | ### tomcat7.exe | ||
## Navigate to [ | ## Navigate to [INSTALL_HOME]/server/bin/setenv.bat and change the JAVA_MEMORY_MAX setting from 1536 to 1024 | ||
# [optional] Confirm that the server does not have anything running on the port to be used by AppBoard | # [optional] Confirm that the server does not have anything running on the port to be used by AppBoard/enPortal | ||
## The port number is shown as HTTP_PORT in the file: [ | ## The port number is shown as HTTP_PORT in the file: [INSTALL_HOME]/bin/setenv.bat (Windows) or setenv.sh (Unix) | ||
# Run the Tomcat startup executable in [ | # Run the Tomcat startup executable in [INSTALL_HOME]/bin/ | ||
## Windows: startup.bat | ## Windows: startup.bat | ||
## Unix: startup.sh | ## Unix: startup.sh | ||
# Validate the installation | # Validate the installation | ||
## Go to the following URL in a supported web browser on any workstation that has network access to the AppBoard server: http://localhost:8080 | ## Go to the following URL in a supported web browser on any workstation that has network access to the AppBoard/enPortal server: http://localhost:8080 | ||
## When prompted, log in with the following default credeintials: | ## When prompted, log in with the following default credeintials: | ||
### User ID: administrator | ### User ID: administrator | ||
Line 35: | Line 35: | ||
== Create an AppBoard Service == | == Create an AppBoard/enPortal Service == | ||
After installing AppBoard, you can configure the application for automated startup. For example, on a production server, you may want the application to start up automatically any time the server is re-started. This can be implemented using a Windows service. This section details how to configure automated startup. | After installing AppBoard/enPortal, you can configure the application for automated startup. For example, on a production server, you may want the application to start up automatically any time the server is re-started. This can be implemented using a Windows service. This section details how to configure automated startup. | ||
Line 45: | Line 45: | ||
{{Note|A 64-bit JVM must be used when running as a service on 64-bit Windows. }} | {{Note|A 64-bit JVM must be used when running as a service on 64-bit Windows. }} | ||
# Locate the subfolder under [ | # Locate the subfolder under [INSTALL_HOME]\server\bin that matches your operating system. | ||
#: Example: If you are running a 32-bit Windows OS, this would be the "windows-x86" folder. | #: Example: If you are running a 32-bit Windows OS, this would be the "windows-x86" folder. | ||
# Copy the two files from this folder over the same files in [APPBOARD_HOME]\server\bin | # Copy the two files from this folder over the same files in [APPBOARD_HOME]\server\bin | ||
# Open the DOS command window | # Open the DOS command window | ||
# Navigate to [ | # Navigate to [INSTALL_HOME]\server\bin | ||
# Enter the following command to install the Windows service: | # Enter the following command to install the Windows service: | ||
#: > service install | #: > service install |
Revision as of 16:31, 27 March 2012
This section provides instructions for installing AppBoard/enPortal on a Windows Server. It also details how to create a service that will automatically start AppBoard/enPortal when the server is booted.
Install AppBoard/enPortal
To install AppBoard/enPortal, perform the following steps on the server:
- Install the Java Development Kit (JDK)
- Make sure the Java home environment variable is set on the server:
- Start | Right-click on Computer and "Properties" | Advanced System Settings | Environment Variables
- Under "System Variables", if there is no "JAVA_HOME" variable set, click "New"
- Set "Variable Name" to JAVA_HOME
- Set "Variable Path" to the path to the JDK
- Example (Windows): JAVA_HOME = C:\Program Files\Java\jdk1.6.0_10
- Note: Make sure JAVA_HOME does not end with "\" and is not surrounded by quotes. It is also recommended that JAVA_HOME not contain spaces.
- Extract the turnkey installation file to any desired location on the server
- Save the license file into [INSTALL_HOME]/webapps/enportal/WEB-INF/config/license.properties
- If you are running a 32-bit version of Windows, perform the following additional steps:
- Navigate to [INSTALL_HOME]/server/bin/windows-x86 and copy the 32-bit Tomcat files from the /windows-x86 folder up one level to replace the default 64-bit versions in the /bin folder:
- tcnative-1.dll
- tomcat7.exe
- Navigate to [INSTALL_HOME]/server/bin/setenv.bat and change the JAVA_MEMORY_MAX setting from 1536 to 1024
- Navigate to [INSTALL_HOME]/server/bin/windows-x86 and copy the 32-bit Tomcat files from the /windows-x86 folder up one level to replace the default 64-bit versions in the /bin folder:
- [optional] Confirm that the server does not have anything running on the port to be used by AppBoard/enPortal
- The port number is shown as HTTP_PORT in the file: [INSTALL_HOME]/bin/setenv.bat (Windows) or setenv.sh (Unix)
- Run the Tomcat startup executable in [INSTALL_HOME]/bin/
- Windows: startup.bat
- Unix: startup.sh
- Validate the installation
- Go to the following URL in a supported web browser on any workstation that has network access to the AppBoard/enPortal server: http://localhost:8080
- When prompted, log in with the following default credeintials:
- User ID: administrator
- Password: administrator
- Domain: System
Create an AppBoard/enPortal Service
After installing AppBoard/enPortal, you can configure the application for automated startup. For example, on a production server, you may want the application to start up automatically any time the server is re-started. This can be implemented using a Windows service. This section details how to configure automated startup.
The following steps detail how to create a Windows service for automated startup:
- Locate the subfolder under [INSTALL_HOME]\server\bin that matches your operating system.
- Example: If you are running a 32-bit Windows OS, this would be the "windows-x86" folder.
- Copy the two files from this folder over the same files in [APPBOARD_HOME]\server\bin
- Open the DOS command window
- Navigate to [INSTALL_HOME]\server\bin
- Enter the following command to install the Windows service:
- > service install
- If successful, the message should be displayed: "The service 'EdgeWebServer' has been installed."
- Enter the following command later if you need to remove the Windows service:
- > service remove
- If successful, the message should be displayed: "The service 'EdgeWebServer' has been removed."
The service is installed with manual startup configured. The Startup type is changed by running "services.msc" from Windows, selecting properties for "Edge Web Server", then choosing the desired startup type, such as "Automatic".
The setenv.bat script can be used to override the system JAVA_HOME and memory allocated to the Java process.