By default uploaded files are stored in the local disk of the machine where the tool is running. However, tool gives you the option to store uploaded files into S3 storage as well. Few customers might not want to store the uploaded files in the local disk, due to space limitation and availability concerns.
If you have the tool installed across multiple server instances behind a load balancer then it’s mandatory to store the uploaded files into s3 storage. Tool provides option to share the generated report between users. Say suppose a user uploads file into server instance#1. Seconds user tries to access the same generated report. Load balancer could route his request to server instance #2. In such circumstance seconds, user will experience HTTP 404 error if files are stored local disk.
Here are the two simple steps to store the uploaded files into S3 storage:
1. Create a file by name: ‘storage.xml’ and place in the root folder where the application is installed.
2. In ‘storage.xml’ insert the s3 bucket name, access key, secrete key as shown in the below format:
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd"> <properties> <comment>Storage Configurations</comment> <entry key="s3.bucketName">my-bucket</entry> <entry key="s3.accessKey">my-access-key</entry> <entry key="s3.secreteKey">my-secrete-key</entry> </properties>
Here are the steps to enable SAML authentication:
1. In the root folder, you will find ‘saml.xml’ configuration file. In this file set ‘auth.saml‘ property to ‘true’.
2. In the same saml.xml configure the Identify Provider properties.
Here are the steps to enable Dashboard:
1. Download and install Mysql 5.7
2. To activate Dashbaord you need special license key. This key should have been sent to you in the email. Place the license key file (license.lic) in the folder where tier1app tools are installed.
3. Now you need to create database tables required by GCeasy. Script (ddl_01.txt) to create database tables should be sent in email. Execute following statement from command prompt:
mysql -uroot -p < ddl_01.txt
You will be prompted to enter password. Enter the password for your database.
4. Now create a file called connector.xml, specifying database connectivity details. Below is the connector.xml template file:
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd"><properties> <entry key="JDBC_URL">jdbc:mysql://DB_HOST_NAME:DB_PORT/gceasy</entry> <entry key="JDBC_USER">DB_USER_NAME</entry> <entry key="JDBC_PASSWORD">DB_PASSWORD</entry> </properties>
Overriding domain name in Share Report URL
From the GCeasy, FastThread, HeapHero users can click on the ‘Share Report’ option. It will generate a report’s URL. This URL can be shared among team members. If you are running the tool in the ‘hostname1’ on ‘8080’, then generated URL will be of format: ‘http://hostname1:8080/my-gc-report.jsp?….’
However in some enterprises you might be running tool behind webserver, Load Balancer which might be mapped to a different domain name. Example: ‘gceasy.mycompany.com’. In this circumstance you would like the generated URL to look like: ‘https://gceasy.mycompany.com/my-gc-report.jsp?….’
This feature is supported by adding system property ‘appURLPrefix’ in the launch-*.sh script.
Say suppose your current ‘launch-gceasy.sh’ is looking like this:
java -Xmx2g -DuploadDir=. -jar webapp-runner-184.108.40.206.jar --port 8080 gceasy.war &
Change it to:
java -Xmx2g -DappURLPrefix=https://gceasy.mycompany.com -DuploadDir=. -jar webapp-runner-220.127.116.11.jar --port 8080 gceasy.war &
And then restart the tool. From this point, generated Share URL will look like https://gceasy.mycompany.com/my-gc-report.jsp?..
Thread dump analysis in HeapHero
Some Heap dumps tend to contain thread dumps with in it. In those circumstances, HeapHero can invoke FastThread (thread dump analysis tool) to do the thread dump analysis and publish detailed thread dump analysis report. Inorder to do it, you need to launch fastThread server. Say you are launching fastThread Server in http://localhost:8090. Now you need to specify this fastThread server URL in the launch script (i.e. launch-heaphero.sh ) in the -DfastThreadServer system property.
Say your launch-heaphero.sh is looking like this:
java -Xms2g -Xmx24g -Xss40m -DuploadDir=. -jar webapp-runner-18.104.22.168.jar -AconnectionTimeout=3600000 --port 9000 heaphero.war &
You need to add ‘-DfastThreadServer’, example:
java -Xms2g -Xmx24g -Xss40m -DfastThreadServer=http://localhost:8080 -DuploadDir=. -jar webapp-runner-22.214.171.124.jar -AconnectionTimeout=3600000 --port 9000 heaphero.war &