For evaluation only
Below steps are meant for testing out PGX only. For any serious deployment, you should configure Tomcat to enforce proper authentication and authorization, store the credentials securely and only allow connections over HTTPS (see Weblogic's TLS/SSL howto)
This guide uses Weblogic version 220.127.116.11.
Unzip the downloaded file into a location of your choice, e.g.
unzip $HOME/Downloads/fmw_18.104.22.168.0_wls_Disk1_1of1.zip -d $HOME
Run the installer.
cd fmw_22.214.171.124.0_wls_Disk1_1of1 java -jar fmw_126.96.36.199.0_wls.jar
The script will start installation and prompt you to create a domain: choose Yes
Enter username and password for the admin console. The password must be at least 8 alphanumeric characters with at least one number or special character in it.
MW_HOME environment variable, e.g.
Start the server
cd $MW_HOME/user_projects/domains/base_domain ./bin/startWebLogic.sh
The server will then start up. You will know that it is running when something like the following is printed to the console:
<Nov 26, 2014 4:36:14 PM PST> <Notice> <WeblogicServer> <BEA-000360> <The server started in RUNNING mode> <Nov 26, 2014 4:36:14 PM PST> <Notice> <WeblogicServer> <BEA-000365> <Server state changed to RUNNING.>
Problems when starting Weblogic
We noticed that on some distributions the last step of the installation (starting Weblogic) fails, because Weblogic can not determine the IP address of the machine. Read more about this problem and the solution in the troubleshooting.
Open the Weblogic Admin Console by opening localhost:7001/console in your browser. Log in using the credentials you specified during the previous installation step.
To deploy PGX's WAR over HTTP, we need to enable tunneling first. In the Weblogic admin console, click on Environment (left panel) → Servers (left panel) → myserver(admin) (main panel) → Protocols (top tab bar) → Check the box Enable Tunneling → Click Save button.
Deploy PGX WAR via command line, passing your admin credentials and the PGX WAR file:
cd $MW_HOME/user_projects/domains/base_domain . bin/setDomainEnv.sh java weblogic.Deployer -adminurl http://localhost:7001 -username <username> -password <password> -deploy -upload $PGX_HOME/shared-memory/server/pgx-webapp-20.2.2.war
If everything was successful, the command will print something like
... Target state: deploy completed on Server myserver
Check whether you can connect to the server:
$PGX_HOME/bin/pgx-jshell -b http://localhost:7001/pgx