A few weeks ago, I discussed an issue where a profile could no longer be created on WebSphere Application Server 6.1.0.19. It boiled down to an issue with the Java security policy files and thier ‘restricted’ and ‘unrestricted’ flavours. At the time, I thought that WebSphere actually required the unrestricted versions.

To test my theory I created my own 6.1.0.19 server and created a profile. It worked just fine without installing the unrestricted policy files.  This means that my issue is that my environment is actually telling WebSphere (some-how) to use encryption algorithims used in the unrestricted jar. I’m still trying to figure out what part of my environment setup is doing this, but I thought it would be a service to the internet to document where I’m at currently.

IBM Documentation on the subject

Related Posts

• Profile Creation on WebSphere Application Server 6.1.0.19 Fails with Certificate Error
• IBM APAR PK49507: PROFILE RECREATION Required!
• WebSphere 6.1 and Jakarta Commons Logging (JCL) using Log4J in an EJB
• Still Springing Along
• Connecting to Oracle BPEL hosted on WebSphere Application Server 6.1 with JDeveloper

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.