V11: EPMA App deploying error

Hi,
I'm using EPM11.1.1.3.
EPMA application has been migrated from V9.3.1 as classic app and then it has been migrated to EPMA app.
When I try to deploy it (w/out any changes) I get error
"Dimension 'FYear' failed validation 'YearMembersSequential' for the following reason(s): Year members must be sequential."
What does it mean?

Verify in the Application Library if your dimensions. The EPMA sometimes create new members how "No Year", for example.
You can excluded in the Application View.
M

Similar Messages

WD app Deployment Error - Where can we find J2ee log file for linux install

Hi,
I have a problem with deploying a web dynpro application. There are no errors before deployment but when I deploy the application, I get a deployment error with the following description.
I tried to view the trace or log file but we have SAP installed on a linux OS and I do not know where can we see the log or trace file. Please help.
Version:
SAP NW 2004s SP15
NWDS 7.0
xRPM 4.5
Error Description:
May 14, 2008 12:49:50 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager)
[Thread[Deploy Thread,5,main]] ERROR:
[008]Deployment aborted
Settings
SDM host : BS307
SDM port : 50718
URL to deploy : file:/C:/DOCUME1/SMULLA1/LOCALS~1/Temp/2/temp20045SempraDemo4.5.ear
Result
=> deployment aborted : file:/C:/DOCUME1/SMULLA1/LOCALS~1/Temp/2/temp20045SempraDemo4.5.ear
Aborted: development component 'SempraDemo4.5'/'local'/'LOKAL'/'0.2008.05.14.00.49.36'/'0':Caught exception during application deployment from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Cannot deploy application local/SempraDemo4.5.. Reason: Clusterwide exception: Failed to deploy application local/SempraDemo4.5. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application local/SempraDemo4.5. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine? (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
Edited by: Subramanya Srinivas Mullapudi on May 14, 2008 8:34 AM

Hi Reza,
Hope you are doing good.
You can set the trace level in the SAP/Java Gui dynamically :
Call transaction SMICM
Choose the menu Goto → Trace Level → Set
In the pop-up window, set the desired level (0,1,2,3)
To switch on an /nSMICM or ICM HTTP trace via command line you should go to
usr\sap\<SID>\<instance_number>\exe directory and run the icmon program with the following command:
icmon◦◦pf=\usr\sap\<SID>\SYS\profile\<SID>_<instance_name>_<HOST>
where you fill in the SID, instance name and host corresponding to your system.
The icmon program is interactive and to increase trace level you must write
"+" and pres enter.To quit you must write "q" and press enter.
The trace will be written◦to the following file: usr\sap\<SID>\<instance_number>\work\dev_icm
Thank you!
Kind Regards,
Hemanth
SAP AGS

EPMA Application Deployment Error (Essbase BSO cube)

Hi,
I am trying to deploy the EPMA application & I am getting the following error:
Success.
\\Record #8797 - Error adding Dynamic calc property to member %_to Sales (3320)
\\Record #8797 - No time dimension defined
Stat Accounts + S T Stat Reps + X T %_to Sales ~ X F E T "\"5500"->\"YearTotal\"/\"Sales\"->\"YearTotal\" ;" % to Sales % to Sales
\\Record #8799 - Error adding Dynamic calc property to member Margin_Inc% (3320)
\\Record #8799 - No time dimension defined
Stat Accounts + S T Stat Reps + X T Margin_Inc% + X A E T "\"Margin\"/ \"Sales\";"
I am trying to tag the account members %_to Sales & Margin_Inc% as TB Average, If I change that property to None, I don't get these errors & everything deploys without any error. Post deployment if I go in the outline & try to assign TB average directly in EAS I am able to do that without any errors.
I am on EPMA 11.1.2.1, this error is not occuring in Planning application but in BSO Essbase cube in EPMA
Any thoughts?
Thanks.

Sorry - reread your post and follow that it is an EPMA BSO app, not planning. Can you try placing the Period dimension before the Account dimension in order and seeing if it deploys? I know that's not ideal, but just as a test. You may want to read the very end of this possibly related post:
Re: Essbase Studio - Measures hierarchy
Thanks,
Jon

Provider-hosted app deployment error

Hi,
I am developing a provider-hosted app which programmatically adds the app part on Home page of the site. I wrote the code for adding the app part in App Installed event. It works fine when i debug it on my development site. Then i made a catalog site and
deployed it there following the instructions in this blog.
http://blogs.msdn.com/b/russmax/archive/2014/06/26/part-2-intro-to-provider-hosted-apps-develop-package-and-deploy.aspx
After deploying the app on app catalog, when i try to add the app, i get the following error.
Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Foundation
Date: 3/18/2015 5:44:17 PM
Event ID: 8311
Task Category: Topology
Level: Error
Keywords:
User: SP\Administrator
Computer: SP2013.SP2013.LOCAL
Description:
An operation failed because the following certificate has validation errors:
Subject Name: CN=SP2013.SP2013.LOCAL
Issuer Name: CN=SP2013.SP2013.LOCAL
Thumbprint: 9D3D48F8D7ED5AE4CB187BEB3319C3E65A36340C
Errors:
SSL policy errors have been encountered. Error code '0x2'..
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-SharePoint Products-SharePoint Foundation" Guid="{6FB7E0CD-52E7-47DD-997A-241563931FC2}" />
<EventID>8311</EventID>
<Version>15</Version>
<Level>2</Level>
<Task>13</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2015-03-18T12:44:17.912561500Z" />
<EventRecordID>24215803</EventRecordID>
<Correlation ActivityID="{3A58A90C-2A9C-4128-A4CF-D07A9FEB48E8}" />
<Execution ProcessID="980" ThreadID="688" />
<Channel>Application</Channel>
<Computer>SP2013.SP2013.LOCAL</Computer>
<Security UserID="S-1-5-21-2707663415-3900761612-1761970234-500" />
</System>
<EventData>
<Data Name="string0">CN=SP2013.SP2013.LOCAL</Data>
<Data Name="string1">CN=SP2013.SP2013.LOCAL</Data>
<Data Name="string2">9D3D48F8D7ED5AE4CB187BEB3319C3E65A36340C</Data>
<Data Name="string3">SSL policy errors have been encountered. Error code '0x2'.</Data>
</EventData>
</Event>
I am deploying the app with non-system user. Is there any any limitation of using app installed event in
app catalog or am i doing something wrong?

Hi,
The following blog for you to check:
SharePoint 2013 Domain Certificate for Provider-Host App Development Environment
http://rwcchen.blogspot.com/2013/12/sharepoint-2013-domain-certificate-for.html
Or try to add the following line within <system.net> tag
in your SharePoint site web.config:
<settings>
<servicePointManager
checkCertificateName="false"
checkCertificateRevocationList="false"/>
</settings>
Best Regards
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]
Thanks for the reply but I already tried the solution. My app works fine when i deploy it without app install event receiver but when i add the event receiver i face the error. Is there any limitation of using app install event receivers?

EPMA App Deployment

Hi,
Recently when we created a new EPMA application and deployed the same we are getting the following error message:
[Dec 27, 2012 11:21:20 AM]: Starting Cube Create/Refresh...[Dec 27, 2012 11:21:57 AM]: null
[Dec 27, 2012 11:21:57 AM]: An Exception occurred during Application deployment.: The Hyperion Essbase operation failed with an error code: 1019060.
But application got created in essbase. And other applications are getting deployed without any issues. Please do help us out.
thanks

The essbase related error is "1019060 Unable to Complete Reading From [%s]: Out Of Memory"
It might be worth having a read of the following doc in Oracle Support - "Error "1019060 Unable to complete reading from outline. Out of Memory" When Restructuring [ID 852783.1]"
Cheers
John
http://john-goodwin.blogspot.com/

HFM EPMA Application Deployment Error

While deploying application I'm finding the below error.
Any help would be highly appreciated
Error Reference Number: {7AF55A07-D29A-4D4F-8342-F5312BAA4153}
Num: 0x80040218;Type: 0;DTime: 7/5/2010 9:26:02 PM;Svr: AMIT-PC;File: CHsxServer.cpp;Line: 1115;Ver: 11.1.1.3.0.2413;
Num: 0x80040218;Type: 0;DTime: 7/5/2010 9:26:02 PM;Svr: AMIT-PC;File: CHsxServer.cpp;Line: 1010;Ver: 11.1.1.3.0.2413;
Num: 0x80040218;Type: 0;DTime: 7/5/2010 9:26:02 PM;Svr: AMIT-PC;File: AgentHelper.cpp;Line: 610;Ver: 11.1.1.3.0.2413;
Num: 0x80040218;Type: 0;DTime: 7/5/2010 9:26:02 PM;Svr: AMIT-PC;File: CHfmAwbAgent.cpp;Line: 546;Ver: 11.1.1.3.0.2413;
Rahul

This message is insufficient to determine the error. Please include the errors which precede this one.
--Chris

Deploying a web app with errors

Good day,
We are migrating an older application into a WebLogic Portal 10.2 environment. We have Ant scripts to do the deployment from the command line but we want to use the Workspace Studio capabilities to deploy JSP changes to the application. The problem is that the application was architected to dynamically include JSP fragments into other JSPs. These fragments have objects defined in other JSPs and therefore show up with errors in the problems tab in Eclipse.
Is there a way to force an application to deploy even in this case or do we have to keep deploying/redeploying from the command line? This takes much longer than pushing the single files so this is why we are trying to figure out how to do it within the tool.
Thanks,
Sean

I have created a web application and have a jsp host.
I have 2 questions:
1-How do I deploy to the host. please explain. is this host a 3rd party? if so, ask them.
if the host is tomcat running on a machine that you have control of, create a WAR file and put it in the /webapps directory.
>
2-I also want to add a tomcat realm and have been
told to edit the server.xml file and web.xml file you should not edit the server.xml. just put a WAR file in the /webapps directory. no need to edit server.xml.
web.xml is part of the standard web app deployment. your app should have one, and it needs to be in the WEB-INF directory.
are these found on the host??
please offer a confused guy some helpYou should read "My First Web App" on the Tomcat page.
%

HFM EPMA application deployment aborted with error Object reference not set

HFM EPMA application deployment aborted with error Object reference not set to an instance of an object when trying to validate/deploy any HFM application in EPMA. This has started happending after we have deleted a Dimension in one of HFM applications. The deleted dimension is a shared dimension.
We are facing this issue in a distributed environment with version 11.1.2.1. This applications are built here newly.
Following is the error log entry
16] ERROR Object reference not set to an instance of an object.
at Hyperion.DimensionServer.CompareCriteria.<>c__DisplayClass5.<GetMemberClassProperties>b__4(Dimension dim)
at Hyperion.DimensionServer.Library.IterateDimensions(Action`1 action)
at Hyperion.DimensionServer.CompareCriteria.GetMemberClassProperties(ApplicationClass appClass, DimensionClass dimClass, MemberClass mbrClass)
at Hyperion.DimensionServer.CompareCriteria.GetCommonMemberClassProperties(RelationshipMember fromMember, RelationshipMember toMember, ApplicationClass fromAppClass, ApplicationClass toAppClass)
at Hyperion.DimensionServer.CompareMemberEvaluator.CompareProperties(RelationshipMember fromMember, RelationshipMember toMember, ApplicationClass fromAppClass, ApplicationClass toAppClass, List`1 propertyDifferences)
at Hyperion.DimensionServer.CompareMemberEvaluator.Compare(RelationshipMember sourceMember, Application sourceApp, Application targetApp, Boolean firstPass, Int32 level, Boolean continueCheckingAfterDifferences)
at Hyperion.DimensionServer.CompareMemberEvaluator.Compare(List`1 sourceTopMembers, List`1 targetTopMembers, Application sourceApp, Application targetApp, Boolean firstPass, Boolean continueCheckingAfterDifferences)
at Hyperion.DimensionServer.CompareMemberEvaluator.Execute(List`1 fromTopMembers, List`1 toTopMembers, Dimension fromDimension, Dimension toDimension, Boolean continueCheckingAfterDifferences)
at Hyperion.DimensionServer.CompareDimensionEvaluator.Execute(Dimension fromDimension, Dimension toDimension, ApplicationClass fromAppClass, ApplicationClass toAppClass)
at Hyperion.DimensionServer.CompareEngine.CompareDimensions(Dimension fromDimension, Dimension toDimension)
at Hyperion.DimensionServer.CompareEngine.StartCompare()
at Hyperion.DimensionServer.Validations.HFMApplicationValidation.CheckStaticDimension(Library snapShot, Dimension dim, Application oldApp, String[] skipProperties)
at Hyperion.DimensionServer.Validations.HFMApplicationValidation.CheckStaticDimensions(Application baselineApp)
at Hyperion.DimensionServer.Validations.ApplicationValidation.ValidateAgainstBaseline()
at Hyperion.DimensionServer.Validations.HFMApplicationValidation.InternalValidate()
at Hyperion.DimensionServer.Validations.ApplicationValidation.Validate()
at Hyperion.DimensionServer.Validations.ApplicationValidation.<ValidateAsync>b__0()System.NullReferenceException: Object reference not set to an instance of an object.
at Hyperion.DimensionServer.CompareCriteria.<>c__DisplayClass5.<GetMemberClassProperties>b__4(Dimension dim)
at Hyperion.DimensionServer.Library.IterateDimensions(Action`1 action)
at Hyperion.DimensionServer.CompareCriteria.GetMemberClassProperties(ApplicationClass appClass, DimensionClass dimClass, MemberClass mbrClass)
at Hyperion.DimensionServer.CompareCriteria.GetCommonMemberClassProperties(RelationshipMember fromMember, RelationshipMember toMember, ApplicationClass fromAppClass, ApplicationClass toAppClass)
at Hyperion.DimensionServer.CompareMemberEvaluator.CompareProperties(RelationshipMember fromMember, RelationshipMember toMember, ApplicationClass fromAppClass, ApplicationClass toAppClass, List`1 propertyDifferences)
at Hyperion.DimensionServer.CompareMemberEvaluator.Compare(RelationshipMember sourceMember, Application sourceApp, Application targetApp, Boolean firstPass, Int32 level, Boolean continueCheckingAfterDifferences)
at Hyperion.DimensionServer.CompareMemberEvaluator.Compare(List`1 sourceTopMembers, List`1 targetTopMembers, Application sourceApp, Application targetApp, Boolean firstPass, Boolean continueCheckingAfterDifferences)
at Hyperion.DimensionServer.CompareMemberEvaluator.Execute(List`1 fromTopMembers, List`1 toTopMembers, Dimension fromDimension, Dimension toDimension, Boolean continueCheckingAfterDifferences)
at Hyperion.DimensionServer.CompareDimensionEvalua
There was a bug in earlier releases for deleting dimensions with children, making the children orphans.
Heard from release notes that it has been fixed, but we are seeing this issue in 11.1.2.1 again.
Please help us out in resolving this error.

Hi,
I always ask this first, have you installed all the planning and epma patches as there have been many issues addressed in 9.3.1
Cheers
John
http://john-goodwin.blogspot.com/

Deployment error with sun app server 8.2

hi,
i'm a newbieto java programming.
i'm following the j2ee tutorial.
but i'm stuck when deploying
could anyone help me on this?
thanks in advance.
Distributing /opt/CustomerBook/dist/customerbook.ear to [localhost:4848_server]
Unable to construct properties list for: getConnectionPoolProperties
deployment started : 0%
Deployment error: Deployment timed out after 120 seconds.. See the messages.log file for details.
/opt/CustomerBook/nbproject/build-impl.xml:219: Deployment error: Deployment timed out after 120 seconds.. See the messages.log file for details.
BUILD FAILED (total time: 2 minutes 54 seconds)
EXECUTION SECTION
=================
line 219:
** <nbdeploy clientModuleUri="${client.module.uri}" clientUrlPart="${client.urlPart}" forceRedeploy="${forceRedeploy}" debugmode="false"/>**

For future references:
this happens to me too and I found that the cause is that the AM server you are going to configure, is already registered into the directory server.
Try running this command (with the obvious parameters substituted)
ldapsearch -B -T -D 'cn=directory manager' -w YOUR_CREDENTIALS -b ou=1.0,ou=iPlanetAMPlatformService,ou=services,YOUR_BASEDN -s base objectclass=* | grep YOUR_SERVERNAMEIf you found that the server you are configuring is listed here try going to AMserver console (if you have another AMserver configured) and browse to Configuration->System Properties->Platforms. If the server is here, remove it, if not, just hit Save (very important).
If this is your first AM and is a first installation you can just get rid of the Directory Server suffix and recreate it with the Top Entry alone.
Edited by: flistello on Mar 27, 2008 4:30 PM

Deployment error in 9.0.3 for app with local interface

While attempting to port an EJB-application from jboss to oracle, I have encountered a deployment error in 9.0.3 9iASR2 which I cannot decipher. The same ear-file is successfully deployed on the 9.0.3. OC4J standalone version (both on a machine running winXP)
I get a "syntax error in source" when I attempt the deployment and all my local-interface class-files end up on the j2ee_home root, i.e. <oracle-home>/j2ee/home/.
Am I too early using local interface on version 9.0.3, is my packaging messed up or should I look for my bugs in some missed logfile?
BTW: where do I find deployment stack traces for this version of 9iAS?
Dag

Hi,
you can find deployment stack traces in the following location \ORACLE\806\opmn\logs. i think this might help u.
I am also facing a problem like com.evermind.compiler.CompilationException: Syntax error in source,did u know cause for this.
Thanks and Regards,
Bala

Helps for WLP9.2 in a cluster: deploy errors, propagation errors

I wrote a document for our portal project's production support that details how to fix several recuring problems with WLP9.2 (GA) in cluster. I'm sharing this with the community as a help.
Email me if you'd like updates or have additional scenarios / fixes or you'd like the word doc version.
Curt Smith, Atlanta WLP consultant, [email protected], put HELP WLP as a part of the subject please.
1     WLP 9.2 Environment
The cluster environment where these symptoms are frequently seen is described by the following:
1.     Solaris 9 on 4 cpu sparc boxes. 16Gb Ram. The VM is given ?Xmx1034m.
2.     Bea private patch: RSGT, fixed cluster deployments.
3.     Bea private patch: BG74, fixed session affinity, changed the session tracking cookie name back to the standard name: JSESSIONID.
4.     IBM UDB (DB2) using the Bea DB2 driver. FYI: the problems described below I don?t feel have any relationship to the DB used for a portal.
2     Common problems and their fixes
2.1     Failed deploy (Install) of a new portal application via the cluster console.
Problem symptoms:
After clicking Finish (or) Commit the console displays that there where errors. All errors require this procedure.
Fix steps:
1.     Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a.     Find the PID to kill: lsof ?C | grep <listen port number>
b.     kill <pid>
c.     Run kill again and if the pid is still running then do: kill -9 <pid>
2.     Admin server:
a.     Remove file: <domain>/config/config.lok
b.     Edit file: <domain>/config/config.xml
c.     Remove all elements of: <app-deployment> ? </app-deployment>
d.     Start the Admin server
e.     Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3.     Both Managed servers:
a.     cd <domain>/config
b.     rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c.     cd <domain>/servers/<managed_name>
d.     rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e.     Start each managed server.
f.     Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
You can now use the console to Install your applications.
2.2     The portal throws framework / container exceptions on one managed instance.
Problem symptoms:
If you see exceptions from the classloader re a framework class not found, serialization failure or error etc. In general the symptom is that the container is not stable, running correctly, not making sense or your application works on one managed instance but not on the other.
Fix steps:
1.     Shut down the problem managed instance. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a.     Find the PID to kill: lsof ?C | grep <listen port number>
b.     kill <pid>
c.     Run kill again and if the pid is still running then do: kill -9 <pid>
2.     Perform these clean up steps on one or both managed instances:
a.     cd <domain>/config
b.     rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c.     cd <domain>/servers/<managed_name>
d.     rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e.     Start each managed server.
f.     Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
3.     The libraries and applications should auto deploy as the managed instance comes up. Once the managed instance goes into the running state, or you Resume into the running state. Your application should be accessible. Sometimes it takes a few seconds after going into the running state for all applications to be instantiated.
2.3     Content propagation fails on the commit step.
Problem symptoms:
In the log of the managed instance you specified in the propagation ant script you?ll see exceptions regarding not being able to create or instantiate a dynamic delegated role.
There is an underlying bug / robustness issue with WLP9.2 (GA) where periodically you can?t create delegated roles either with the PortalAdmin or via the propagation utility.
Important issue:
This procedure was supplied by Bea which will remove from the internal LDAP and the portal DB your custom / created roles. This will leave your cluster in the new installation state with just the default users and roles: weblogic and portaladmin. The implications are that you?ll have to boot your cluster with console user: weblogic / weblogic. You can then add back your secure console user/password but you?ll have to do this over and over as propagations fail. The observed failure rate is once every 2-3 weeks if you do propagations daily.
Note:
The following assumes that you left the default console user weblogic password to be the default password of: weblogic. The following procedure deletes the local LDAP but leaves the rows in the DB.users table including the SHA-1 hashed passwords. The following procedure should still work if you changed the password for weblogic, but it probably won?t work if you try to substitute your secure console user/pw because there will be no delegated authorization roles mapping to your custom console user. You might experiment with this scenario.
Fix steps:
1.     Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a.     Find the PID to kill: lsof ?C | grep <listen port number>
b.     kill <pid>
c.     Run kill again and if the pid is still running then do: kill -9 <pid>
2.     Admin server:
a.     Remove directory: <domain>/servers/AdminServer/data/ldap
b.     Run this SQL script after you edit it for your schema:
delete from yourschema.P13N_DELEGATED_HIERARCHY;
delete from yourschema.P13N_ENTITLEMENT_POLICY;
delete from yourschema.P13N_ENTITLEMENT_RESOURCE;
delete from yourschema.P13N_ENTITLEMENT_ROLE;
delete from yourschema.P13N_ENTITLEMENT_APPLICATION;
commit;
c.     Start the Admin server
d.     Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3.     Both Managed servers:
a.     cd <domain>/servers/<managed_name>
b.     rm ?rf data
This forces the re-down load of the LDAP directory.
c.     Start each managed server.
d.     Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
2.4     The enterprise portal DB fails and needs to be restored OR switch DB instances
Restoring a portal DB or switching existing DBs are similar scenarios. The issues that you?ll face with WLP9.2 since it now uses a JDBCauthenticator to authenticate and authorize the console / boot user you need to first be able to connect to the DB before the admin and managed instances can boot. If you haven?t properly encrypted the DB user?s password in the <domain>/config/jdbc/*.xml files, then you?ll not be able to boot the admin server since you won?t be able to create a JDBC connection to the DB. The boot messages are not clear as to what the failure is.
You?ll need to know an Admin role user and password that?s in the DB you?re wanting to connect to, to put into boot.properties and on the managed instances in their boot.properties or startManaged scripts. Don?t forget that the managed instances have local credentials which is new for 9.2. They are in the startManaged script in clear text or a local boot.properties.
Note:
The passwords in the DB are SHA-1 hashed and there is no SHA-1 hash generator tool so you can?t change a password via SQL, but you can move the password from one DB to another. This is possible because the domain encryption salt is not used to generate the SHA-1 string. As it turns out, the SHA-1 string is compatible with all 9.2 cluster domains. IE the domain DES3 salt has nothing to do with password verification. The same password SHA-1 string taken from different domains or even same domain but different users will be different, this is just a randomization put into the algorithm yet every domain will be able to validate the given password against the DB?s SHA-1 string. Because of this, I?ve not had any problem moving DB instances between clusters, especially if I?ve given up on security and use weblogic/weblogic as the console user and this user / pw is in every DB.
Steps:
The assumption for restoring a DB is that the DB has been restored but it?s an older version and doesn?t have the console user/pw that is in boot.properties. At this point swaping a DB is the same as restoring an old version of the portal DB.
1.     Edit the console user and password as clear text into: <domain>/servers/AdminServers/security/boot.properties
This is where you may give in and use weblogic/weblogic.
2.     Set the correct DB access password encryption in the jdbc/*.xml files.
a.     cd <domain>/bin
b.     . ./setDomainEnv.sh or if you?re on windows just run: setDomainEnv.cmd
c.     java weblogic.security.Encrypt <the_db_password>
d.     Edit the returned string into every <domain>/config/jdbc/*.xml
e.     Make sure the *.xml files point to the correct DB host, port, schema, DB name, DB user.
3.     Start the Admin server. I should come up. If it doesn?t it has to be not being able to create a connection to the DB, which depends on the *.xml having the correct user and DES-3 encrypted password.
4.     Edit the new console user/password on the managed instance bin/startManaged script or the local boot.properties.
5.     Start the managed instances.
2.5     Install patches on a host that does not have internet access
The short description is to run smart update on a host that does have internet access. Fetch out of the <domain>/utils/bsu/cache_dir     directory the downloaded patch jar and xml. Manually apply the patch to your non-internet accessible hosts.

I wrote a document for our portal project's production support that details how to fix several recuring problems with WLP9.2 (GA) in cluster. I'm sharing this with the community as a help.
Email me if you'd like updates or have additional scenarios / fixes or you'd like the word doc version.
Curt Smith, Atlanta WLP consultant, [email protected], put HELP WLP as a part of the subject please.
1     WLP 9.2 Environment
The cluster environment where these symptoms are frequently seen is described by the following:
1.     Solaris 9 on 4 cpu sparc boxes. 16Gb Ram. The VM is given ?Xmx1034m.
2.     Bea private patch: RSGT, fixed cluster deployments.
3.     Bea private patch: BG74, fixed session affinity, changed the session tracking cookie name back to the standard name: JSESSIONID.
4.     IBM UDB (DB2) using the Bea DB2 driver. FYI: the problems described below I don?t feel have any relationship to the DB used for a portal.
2     Common problems and their fixes
2.1     Failed deploy (Install) of a new portal application via the cluster console.
Problem symptoms:
After clicking Finish (or) Commit the console displays that there where errors. All errors require this procedure.
Fix steps:
1.     Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a.     Find the PID to kill: lsof ?C | grep <listen port number>
b.     kill <pid>
c.     Run kill again and if the pid is still running then do: kill -9 <pid>
2.     Admin server:
a.     Remove file: <domain>/config/config.lok
b.     Edit file: <domain>/config/config.xml
c.     Remove all elements of: <app-deployment> ? </app-deployment>
d.     Start the Admin server
e.     Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3.     Both Managed servers:
a.     cd <domain>/config
b.     rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c.     cd <domain>/servers/<managed_name>
d.     rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e.     Start each managed server.
f.     Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
You can now use the console to Install your applications.
2.2     The portal throws framework / container exceptions on one managed instance.
Problem symptoms:
If you see exceptions from the classloader re a framework class not found, serialization failure or error etc. In general the symptom is that the container is not stable, running correctly, not making sense or your application works on one managed instance but not on the other.
Fix steps:
1.     Shut down the problem managed instance. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a.     Find the PID to kill: lsof ?C | grep <listen port number>
b.     kill <pid>
c.     Run kill again and if the pid is still running then do: kill -9 <pid>
2.     Perform these clean up steps on one or both managed instances:
a.     cd <domain>/config
b.     rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c.     cd <domain>/servers/<managed_name>
d.     rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e.     Start each managed server.
f.     Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
3.     The libraries and applications should auto deploy as the managed instance comes up. Once the managed instance goes into the running state, or you Resume into the running state. Your application should be accessible. Sometimes it takes a few seconds after going into the running state for all applications to be instantiated.
2.3     Content propagation fails on the commit step.
Problem symptoms:
In the log of the managed instance you specified in the propagation ant script you?ll see exceptions regarding not being able to create or instantiate a dynamic delegated role.
There is an underlying bug / robustness issue with WLP9.2 (GA) where periodically you can?t create delegated roles either with the PortalAdmin or via the propagation utility.
Important issue:
This procedure was supplied by Bea which will remove from the internal LDAP and the portal DB your custom / created roles. This will leave your cluster in the new installation state with just the default users and roles: weblogic and portaladmin. The implications are that you?ll have to boot your cluster with console user: weblogic / weblogic. You can then add back your secure console user/password but you?ll have to do this over and over as propagations fail. The observed failure rate is once every 2-3 weeks if you do propagations daily.
Note:
The following assumes that you left the default console user weblogic password to be the default password of: weblogic. The following procedure deletes the local LDAP but leaves the rows in the DB.users table including the SHA-1 hashed passwords. The following procedure should still work if you changed the password for weblogic, but it probably won?t work if you try to substitute your secure console user/pw because there will be no delegated authorization roles mapping to your custom console user. You might experiment with this scenario.
Fix steps:
1.     Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a.     Find the PID to kill: lsof ?C | grep <listen port number>
b.     kill <pid>
c.     Run kill again and if the pid is still running then do: kill -9 <pid>
2.     Admin server:
a.     Remove directory: <domain>/servers/AdminServer/data/ldap
b.     Run this SQL script after you edit it for your schema:
delete from yourschema.P13N_DELEGATED_HIERARCHY;
delete from yourschema.P13N_ENTITLEMENT_POLICY;
delete from yourschema.P13N_ENTITLEMENT_RESOURCE;
delete from yourschema.P13N_ENTITLEMENT_ROLE;
delete from yourschema.P13N_ENTITLEMENT_APPLICATION;
commit;
c.     Start the Admin server
d.     Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3.     Both Managed servers:
a.     cd <domain>/servers/<managed_name>
b.     rm ?rf data
This forces the re-down load of the LDAP directory.
c.     Start each managed server.
d.     Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
2.4     The enterprise portal DB fails and needs to be restored OR switch DB instances
Restoring a portal DB or switching existing DBs are similar scenarios. The issues that you?ll face with WLP9.2 since it now uses a JDBCauthenticator to authenticate and authorize the console / boot user you need to first be able to connect to the DB before the admin and managed instances can boot. If you haven?t properly encrypted the DB user?s password in the <domain>/config/jdbc/*.xml files, then you?ll not be able to boot the admin server since you won?t be able to create a JDBC connection to the DB. The boot messages are not clear as to what the failure is.
You?ll need to know an Admin role user and password that?s in the DB you?re wanting to connect to, to put into boot.properties and on the managed instances in their boot.properties or startManaged scripts. Don?t forget that the managed instances have local credentials which is new for 9.2. They are in the startManaged script in clear text or a local boot.properties.
Note:
The passwords in the DB are SHA-1 hashed and there is no SHA-1 hash generator tool so you can?t change a password via SQL, but you can move the password from one DB to another. This is possible because the domain encryption salt is not used to generate the SHA-1 string. As it turns out, the SHA-1 string is compatible with all 9.2 cluster domains. IE the domain DES3 salt has nothing to do with password verification. The same password SHA-1 string taken from different domains or even same domain but different users will be different, this is just a randomization put into the algorithm yet every domain will be able to validate the given password against the DB?s SHA-1 string. Because of this, I?ve not had any problem moving DB instances between clusters, especially if I?ve given up on security and use weblogic/weblogic as the console user and this user / pw is in every DB.
Steps:
The assumption for restoring a DB is that the DB has been restored but it?s an older version and doesn?t have the console user/pw that is in boot.properties. At this point swaping a DB is the same as restoring an old version of the portal DB.
1.     Edit the console user and password as clear text into: <domain>/servers/AdminServers/security/boot.properties
This is where you may give in and use weblogic/weblogic.
2.     Set the correct DB access password encryption in the jdbc/*.xml files.
a.     cd <domain>/bin
b.     . ./setDomainEnv.sh or if you?re on windows just run: setDomainEnv.cmd
c.     java weblogic.security.Encrypt <the_db_password>
d.     Edit the returned string into every <domain>/config/jdbc/*.xml
e.     Make sure the *.xml files point to the correct DB host, port, schema, DB name, DB user.
3.     Start the Admin server. I should come up. If it doesn?t it has to be not being able to create a connection to the DB, which depends on the *.xml having the correct user and DES-3 encrypted password.
4.     Edit the new console user/password on the managed instance bin/startManaged script or the local boot.properties.
5.     Start the managed instances.
2.5     Install patches on a host that does not have internet access
The short description is to run smart update on a host that does have internet access. Fetch out of the <domain>/utils/bsu/cache_dir     directory the downloaded patch jar and xml. Manually apply the patch to your non-internet accessible hosts.

How to configure CA for access to a Web Service from an app deployed in WL

Hi everyone.
I have an app deployed in a WLS (10.3). This app acts like a web service client and works correctly (spring + cxf). The web service is provided by an external company and now they want to switch to https. They are using a self signed certificate. My company's support staff told me that they already configured the domain's trusted key store but the app fails to invoke the WS with the following error:
2010/12/03 13:06:12.314 [ERROR] [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-5] [ar.com.link.gp.services.impl.WebserviceConfirmacionServiceImpl - 55] - Error - informarPagos
javax.xml.ws.WebServiceException: Could not send Message.
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
at $Proxy549.confirmaPago(Unknown Source)
at ar.com.link.gp.services.impl.WebServiceClientServiceImpl.confirmaPago(WebServiceClientServiceImpl.java:103)
at ar.com.link.gp.services.impl.WebServiceClientServiceSinConceptoDecorator.confirmaPago(WebServiceClientServiceSinConceptoDecorator.java:33)
at ar.com.link.gp.services.impl.WebserviceConfirmacionServiceImpl.informarPagos(WebserviceConfirmacionServiceImpl.java:50)
at ar.com.link.gp.services.impl.ConfirmacionServiceImpl.procesarConfirmaciones(ConfirmacionServiceImpl.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at ar.com.link.logging.interceptor.LoggingInterceptor.invoke(LoggingInterceptor.java:74)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy514.procesarConfirmaciones(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.util.MethodInvoker.invoke(MethodInvoker.java:276)
at org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean$MethodInvokingJob.executeInternal(MethodInvokingJobDetailFactoryBean.java:260)
at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86)
at org.quartz.core.JobRunShell.run(JobRunShell.java:203)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
Caused by: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.checkEOF(SSLSocketImpl.java:1239)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.checkWrite(SSLSocketImpl.java:1251)
at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:43)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
at weblogic.net.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:238)
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleHeadersTrustCaching(HTTPConduit.java:1951)
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.onFirstWrite(HTTPConduit.java:1903)
at org.apache.cxf.io.AbstractWrappedOutputStream.write(AbstractWrappedOutputStream.java:42)
at org.apache.cxf.io.AbstractThresholdOutputStream.write(AbstractThresholdOutputStream.java:69)
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1969)
at org.apache.cxf.io.CacheAndWriteOutputStream.postClose(CacheAndWriteOutputStream.java:47)
at org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:188)
at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:637)
at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:483)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:309)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:261)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
... 25 more
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1591)
at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:187)
at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:181)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:975)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:123)
at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:516)
at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:454)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:884)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1096)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1123)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.getSession(SSLSocketImpl.java:1830)
at weblogic.net.http.HttpsClient.getSSLSession(HttpsClient.java:537)
at weblogic.net.http.HttpsURLConnection.connect(HttpsURLConnection.java:257)
at weblogic.net.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:237)
... 41 more
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:285)
at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:191)
at sun.security.validator.Validator.validate(Validator.java:218)
at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:126)
at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:209)
at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:249)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:954)
... 51 more
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:174)
at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:238)
at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:280)
... 57 more
I'm the app's developer and I don't have experience in this subjects. Is the wl misconfigured? Should I do something from the app to reference the keystore?
Thanks un advance.
Sorry for my english.

Hi user10939158, thank you for your response. Maybe I was not precise in my previous post. I know how certificates work and that I should not be using self signed ones. Due to a reason (non technical) we MUST use a self signed certificates. Considering this as a prerequisite let me clarify my situation:
- We added the certificate to the custom trust store connfigured in WL
- We configure the managed server to be more "verbose" about SSL stuff
- When the managed server start it outputs the following lines in the log:
<Dec 13, 2010 5:31:21 PM ARST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the JKS keystore file /wldomains/desa_domain/TrustCTWebservices.jks.>
<Dec 13, 2010 5:31:21 PM ARST> <Debug> <SecuritySSL> <BEA-000000> <SSLContextManager: loaded 1 trusted CAs from /wldomains/desa_domain/TrustCTWebservices.jks>
<Dec 13, 2010 5:31:21 PM ARST> <Debug> <SecuritySSL> <BEA-000000> <Subject: CN=jserver, OU=SWG, O=IBM, C=US; Issuer: CN=jserver, OU=SWG, O=IBM, C=US>
- In this lines we can see the certificate that interests us (jserver)
- When the app do a WS reqeust we see in the log:
<Dec 13, 2010 5:32:43 PM ARST> <Notice> <Stdout> <BEA-000000> <trustStore is: /opt/bea/jrockit_160_05/jre/lib/security/cacerts> (THE VM's DEFAULT KEYSTORE!!!!!!)
- If we add the cert to /opt/bea/jrockit_160_05/jre/lib/security/cacerts everything works ok but I have doubts that this is right.
Why the default keystore is used?
Thank you very much
Regards

Deployment error while running the application

Hi Every body,
I am new to JEE though an old pro at JDK.I have also worked on tomcat.
I have got Sun Java System Application Server 9.1 installed with NetBeans 6.1 on winXP.
I am trying to create a EJB app-client module.I even tried to run the sample application AnnotationOverrideInterceptor given in NetBeans . Every thing goes fine.The Build is also Successful but when i run it, i recieve the error message Deployment error .The module has not been deployed.
See the server log for details.
I am posting a part of server log stack.:
Application server startup complete.
[AutoDeploy] Selecting file C:\Program Files\glassfish-v2-b53\domains\domain1\autodeploy\amserver.war for autodeployment.
Initializing Sun's JavaServer Faces implementation (1.2_04-b19-p03) for context ''
javax.ejb.EJB.description()Ljava/lang/String;
Exception occured in J2EEC Phasejava.lang.IllegalStateException: javax.ejb.EJB.description()Ljava/lang/String;at com.sun.enterprise.deployment.annotation.AnnotationInfo@49bed2
com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [AnnotationOverrideInterceptor] -- javax.ejb.EJB.description()Ljava/lang/String;at com.sun.enterprise.deployment.annotation.AnnotationInfo@49bed2
at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:388)
at com.sun.enterprise.deployment.backend.AppDeployerBase.loadDescriptors(AppDeployerBase.java:358)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:226)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:148)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:191)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:905)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:279)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:774)
at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:187)
at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:223)
Caused by: java.lang.IllegalStateException: javax.ejb.EJB.description()Ljava/lang/String;at com.sun.enterprise.deployment.annotation.AnnotationInfo@49bed2
at com.sun.enterprise.deployment.archivist.Archivist.readAnnotations(Archivist.java:363)
at com.sun.enterprise.deployment.archivist.Archivist.readDeploymentDescriptors(Archivist.java:318)
at com.sun.enterprise.deployment.archivist.Archivist.open(Archivist.java:213)
at com.sun.enterprise.deployment.archivist.ApplicationArchivist.readModulesDescriptors(ApplicationArchivist.java:321)
at com.sun.enterprise.deployment.archivist.ApplicationArchivist.open(ApplicationArchivist.java:238)
at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:763)
at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:744)
at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:349)
... 10 more
Caused by: javax.ejb.EJB.description()Ljava/lang/String;at com.sun.enterprise.deployment.annotation.AnnotationInfo@49bed2
at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:360)
at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:368)
at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.processAnnotations(AnnotationProcessorImpl.java:282)
at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.processAnnotations(AnnotationProcessorImpl.java:264)
at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:192)
at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:129)
at com.sun.enterprise.deployment.archivist.Archivist.processAnnotations(Archivist.java:445)
at com.sun.enterprise.deployment.archivist.Archivist.readAnnotations(Archivist.java:346)
... 17 more
Caused by: java.lang.NoSuchMethodError: javax.ejb.EJB.description()Ljava/lang/String;
at com.sun.enterprise.deployment.annotation.handlers.EJBHandler.processNewEJBAnnotation(EJBHandler.java:276)
at com.sun.enterprise.deployment.annotation.handlers.EJBHandler.processEJB(EJBHandler.java:143)
at com.sun.enterprise.deployment.annotation.handlers.EJBHandler.processAnnotation(EJBHandler.java:98)
at com.sun.enterprise.deployment.annotation.handlers.AbstractResourceHandler.processAnnotation(AbstractResourceHandler.java:119)
at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:337)
... 24 more
Please help as i am trying the google and many other to find solution but i am unable to move forward.I am stuck up at this for last 15 days.It is very frustrating.
I haven't posted the full log as it is very long.I can post the entire server log, if asked for.
Please help
yoodleyee

Hi jwenting,
Thanks alot for replying.
But i am still unable to come out of the mess.Here is the program i am using please help me find out the error.
Here we go:
package hello;
import javax.ejb.Stateless;
@Stateless
public class HelloBean implements HelloRemote {
private String name="Yoodleyee";
public String sayHello() {
//return null;
return "My Name is "+name;
// Add business logic below. (Right-click in editor and choose
// "EJB Methods > Add Business Method" or "Web Service > Add Operation")
package hello;
import javax.ejb.Remote;
@Remote
public interface HelloRemote {
String sayHello();
In the Hello-app-client module i have main()==>>
package hello;
import javax.ejb.EJB;
public class Main {
@EJB
private static HelloRemote helloBean;
* @param args the command line arguments
public static void main(String[] args) {
// TODO code application logic here
System.out.println("Hi "+helloBean.sayHello());
since this program does not require deployment descriptor and also NetBean creates its own deployment discriptor hence i have not written any.
Please tell me where and waht i should change.Also tell me is diployment descriptor necessary.
Awaiting for the reply.
yoodleyee

Deployment Error on sap-j2ee engine

Hi
I build an EJB project,Web project and added these to EAR project and built an '.ear' file. When i tried to deploy on sapj2ee engine. I got the following deployment error.
My j2ee engine is up and running. What went wrong?
Help me,
Thanks
==========
May 24, 2006 5:39:51 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[003]Deployment aborted
Settings
SDM host : sapep
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp22811JCP_EAR.ear
Result
=> deployment aborted : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp22811JCP_EAR.ear
Aborted: development component 'JCP_EAR'/'sap.com'/'localhost'/'2006.05.24.15.58.19':
Caught exception during access of archive "D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.24.15.58.19\temp22811JCP_EAR.ear":
java.lang.RuntimeException: ERROR: Cannot initialize EARReader: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.24.15.58.19\temp22811JCP_EAR.ear to J2EE 1.3.Exception is: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.24.15.58.19\temp22811JCP_EAR.ear to J2EE 1.3.
     at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:185)
     at com.sap.engine.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:444)
     at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.initDeployManager(EngineApplOnlineDeployerImpl.java:300)
     at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:134)
     at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
     at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
     at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
     at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
     at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:46)
     at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
     at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
     at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
     at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
     at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
     at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:119)
     at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:88)
     at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
     at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
     at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)
     at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
     at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
     at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
     at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
     at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
     at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
     at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.IOException: The following archives that aredescribed in the ear descriptor are not found in the ear:      JCP_EJB.jar,Please check the ear content.
     at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.checkDescriptor(ExtendedEARReader.java:805)
     at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.getDescriptor(ExtendedEARReader.java:324)
     at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.<init>(ExtendedEARReader.java:87)
     at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:85)
     ... 30 more
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).null)
Deployment exception : The deployment of at least one item aborted

Hi Amol!
The password is admin for SDM, i redployed by building '.ear' file again.
You suggested to deploy the ear file on SDM remote gui, how to do that?
help me
Thanks
==========
I got the error as:
May 25, 2006 11:22:11 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : sapep
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp11022JCP_EAR.ear
Result
=> deployment aborted : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp11022JCP_EAR.ear
Aborted: development component 'JCP_EAR'/'sap.com'/'localhost'/'2006.05.25.11.17.51':
Caught exception during access of archive "D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.25.11.17.51\temp11022JCP_EAR.ear":
java.lang.RuntimeException: ERROR: Cannot initialize EARReader: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.25.11.17.51\temp11022JCP_EAR.ear to J2EE 1.3.Exception is: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.25.11.17.51\temp11022JCP_EAR.ear to J2EE 1.3.
     at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:185)
     at com.sap.engine.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:444)
     at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.initDeployManager(EngineApplOnlineDeployerImpl.java:300)
     at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:134)
     at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
     at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
     at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
     at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
     at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:46)
     at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
     at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
     at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
     at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
     at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
     at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:119)
     at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:88)
     at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
     at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
     at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)
     at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
     at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
     at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
     at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
     at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
     at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
     at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.IOException: The following archives that aredescribed in the ear descriptor are not found in the ear:      JCP_EJB.jar,Please check the ear content.
     at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.checkDescriptor(ExtendedEARReader.java:805)
     at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.getDescriptor(ExtendedEARReader.java:324)
     at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.<init>(ExtendedEARReader.java:87)
     at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:85)
     ... 30 more
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).null)
Deployment exception : The deployment of at least one item aborted

Deployment error: null. See ide log for details

When i succesfully compiled an application which has a conver in it, the Deployment progress monitor gives the error:
Deployment error: null. See ide log for details
And doesn't display my app.
Does anyone knows what this means?

The ide log file (C:\Documents and Settings\<username>\.Creator\EA\system\ide.log) is located here: "Help" menu -> "Java Studio Creator Log file"
Don't hesitate pasting it into this forum topic.
-Alexis

V11: EPMA App deploying error

Similar Messages

Maybe you are looking for