Verified on WebLogic 10.0 MP1 on Windows
Verified on WebLogic 10.3.5.0 (11g) on Windows (with exploded EAR files)
Refer to the general notes for installing KonaKart on all Application Servers .
Use the deployment method of choice. If you want to be able to edit KonaKart configuration files (eg konakart.properties) without having to re-deploy the application you will have to install using exploded directories. If you don't need this functionality, you can simply deploy KonaKart as an EAR file.
When using the custom ANT command to produce the EAR for WebLogic add the -Dweblogic=true argument so that it creates a compatible birtviewer.war for WebLogic.
Deploying using WebLogic's Install Application Assistant in the Administration Console is particularly straightforward but WebLogic has a variety of deployment options you could also use (such as the autodeploy facility or their command-line driven deploy tool).
Follow these steps when using the Administration Console for deployment: (as applicable for your version of WebLogic)
"Lock and Edit" then choose "Install", then browse to your EAR file (for non-exploded deployments) or to the directory (a directory called konakart.ear under the custom directory of your KonaKart installation) where your exploded version of the EAR is located (for exploded deployments).
If you used the ant build file to create the EAR file and the exploded EAR file these will be located under your KonaKart installation directory at:
Ensure that your EAR is on a directory path that does not contain spaces (such as with "Program Files" on Windows).
Once selected, proceed through the wizard. For "Targeting style" choose "Install this deployment as an application". Accept all other defaults, click on "Finish", then finally click on "Activate Changes" when successful.
Eventually, you should see the message "All changes have been activated. No restarts are necessary." and there should be no errors in the WebLogic log.
Next, click on the checkbox next to konakart and start the application by choosing "Start Servicing All Requests" from the "Start" dropdown list. Confirm this action on the next screen and check theWebLogic log for any errors.
Set the port numbers (7001) for the reporting configuration variables as required (set these using the KonaKart Admin App under the Configuration > Reports section)
To set-up KonaKart to use SSL you need for set it up in the KonaKart Admin App and the BEA WebLogc Administration Console as follows:
Set the HTTP (7001) and HTTPS (7002) port numbers as required (set these using the KonaKart Admin App under the Configuration > HTTP/HTTPS section)
To enable SSL in WebLogic first click the 'Lock and Edit' button under the Change Center. Under the "Domain Structure" navigate through "Environment" then "Servers" then click on your server listed under the "Servers" table on the right hand side. (The default server will be called "AdminServer").
On the General Configurations panel, check the "SSL Listen Port Enabled" checkbox. Leave the port number for SSL as 7002 and ensure this matches the port number specified above in the KonaKart Admin Application.
Click on the "Save" button, then click on "Activate Changes" to save these changes in your WebLogic environment.
Set the memory parameters to suit your environment. Set your memory arguments inside the setDomainEnv.cmd (Windows) or setDomainEnv.sh (Unix/Linux) files.
Set a new USER_MEM_ARGS environment variable with your chosen memory flags, or modify the existing MEM_FLAGS environment variable assignment to suit your requirements. Take note of the code that follows the assignment to MEM_FLAGS - you might find that then your values are overridden.
Restart WebLogic for the changes to take effect and double-check the beginning of the WebLogic log to see what memory settings you actually achieved!