I think its good to post this. My application does an SSO via Credential Vault. However, after migrating my application via XMLAccess, the applicaiton suddenly refused to work. Here's the answer and the solution. (Source : http://www-1.ibm.com/support/docview.wss?uid=swg21259823)
You might run into a situation where a portlet that works correctly in a development environment that uses the credential vault for storing user data no longer works correctly in the higher (for example, QA or production) environments.The error is:AbstractCrede E com.ibm.wps.command.credentialvault.AbstractCredentialVaultCommand execute EJPSK0042E: Operation could not be performed successfully. Missing parameter: Segment ID.
This problem usually happens when the defaultUserSegment is missing from the higher environments. This omission can happen if you use release builder to promote the release to an empty portal, as the slot data is seen as being private data so is not exported as part of the release.
To correct this problem, you can create and import a file to supply the missing data.
Create a file based on http://www-1.ibm.com/support/docview.wss?uid=swg21259823
Then, import this file to the higher environments using XMLAcces.If your environment is missing a different segment, you can alter the file contents above. To determine the missing segment, look at an export from the higher environment compared to the lower, or development, environment. Change the segment tags in the XML file sample given above to the correct lines from the lower environment's XML. Then import the file to resolve the issue.
So we have an EC2 instance on AWS. But we need to terminate it as the project has to give way to something urgent and therefore not on for...
My current work nowadays involves a lot of multi-threading application. And also a lot of simultaneous users. We need to serve them fast (as...