Websphere Application Server 5.1 woes
When attempting to install a new application using an EAR file created by Websphere Studio 5.1 I get the following security warning. When I finish the installation of the new application I am unable to start the application from the enterprise application panel. I am at a loss for what I must do.


The contents of the was.policy file -
//
// Template policy file for enterprise application.
// Extra permissions can be added if required by the enterprise application.
//
// NOTE: Syntax errors in the policy files will cause the enterprise application FAIL to start.
// Extreme care should be taken when editing these policy files. It is advised to use
// the policytool provided by the JDK for editing the policy files
// (WAS_HOME/java/jre/bin/policytool).
//

grant codeBase "file:${application}" {
};

grant codeBase "file:${jars}" {
};

grant codeBase "file:${connectorComponent}" {
};

grant codeBase "file:${webComponent}" {
};

grant codeBase "file:${ejbComponent}" {
};


ADMA0080W: A template policy file without any permission set is included in the 1.2.x enterprise application. You can modify the Java 2 Security policy for the enterprise application by editing the was.policy file located in the ${user.install.root}/config/cells/(yourCellName)/applications/(yourAppName).ear/deployments/(yourAppName)/META-INF directory after the application is installed. For syntax of was.policy, please refer to the Dynamic Policy section of documentation in Info Center.

Solution:
Well, after some time playing with the Webphere Application Server 5.1 install I realized that when I was exporting the application from Webphere Studio 5.1 I was not exporting from the EAR project name but the Sub-Project name in my tree menu. I also realized that I was attemting to add a project to the Application Server that had the same name as an application currently running on the application server. This is a big no-no and the reason for my Webphere Application Server 5.1 woes. I renamed the project in Webphere Studio 5.1 and also created a new Enterprise Application Project for good measure called DFS and DFSEAR respectively. Then I exported by right clicking the DFSEAR project and choosing (surprise) "export". Then I went to install the application on the Websphere Application Server 5.1 and everything fired up correctly.

What is left to do?
I need to be able to invoke my new application without including the port number 9080 in my url line. I am running IBM HTTP SERVER 2.1.4 and I need to be able to invoke the files running on IBM WAS 5.1 without the 9080 port number.


- posted by ThinkEddy @ 3:41 PM