Opensso.war deployment fails in Sun App server 8.2 windows vissta business

I tried deploying opensso.war in Sun App server 8.2 on windows vista business machine. Am getting following error.
Deploying application in domain failed; C:\Program Files\Sun\JavaES5\appserver\domains\domain1\applications\j2ee-modules\opensso\assets\js\AjaxUtils.js (Access is denied) ; requested operation cannot be completed C:\Program Files\Sun\JavaES5\appserver\domains\domain1\applications\j2ee-modules\opensso\assets\js\AjaxUtils.js (Access is denied)
Am I missing something

This is windows permission to the folder issue

Similar Messages

Jndi lookup fails on Sun app server 8

My standalone client on java is able to lookup TopicConnectionFactory on localhost on Sun Server 7 perfectly, but fails on Sun Server 8. I've set up the resources correctly as described in the J2EE 1.4 tutorial, but I get the following error:
SEVERE: NAM5003: CommunicationException in SerialContext lookup()
java.lang.NullPointerException
     at com.sun.enterprise.naming.factory.ConnectorObjectFactory.getObjectInstance(ConnectorObjectFactory.java:64)
     at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:301)
     at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:148)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
javax.naming.CommunicationException:
     at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:174)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)What could be wrong??

It turned out to be a JMS library version issue. I had files for Server 8.0, but was running 8.1. Who knew it would be that big a deal.
Now that I have the right version, I'm able to look up topics and queues, but cannot lookup TopicConnectionFactory. The client does not return at connectionFactory = (TopicConnectionFactory)initial.lookup("jms/FieldTopicConnectionFactory"); and no error in server.log.
Here's the rest of the code:
try {
         Context initial = new InitialContext();
           connectionFactory = (TopicConnectionFactory)initial.lookup("jms/FieldTopicConnectionFactory"); //does not return
         dest = (Topic) initial.lookup("jms/FieldTopic"); //this works!!
} catch{...}I run my standalone through these JVM args:
-Dorg.omg.CORBA.ORBInitialPort=3700 -Dorg.omg.CORBA.ORBInitialHost=myserver.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

Error deploying EJBs on Sun App Server

Someone please help, I am getting a strange problem when deploying an EJB jar.
I have had this code working before (before Xmas), but now I am getting the following error:
java.lang.NoSuchMethodException: com.enterprise.entity.ContentBean.getId();Remote;public abstract java.lang.Integer com.enterprise.entity.ContentRemote.getId() throws java.rmi.RemoteException;_RequestID=e1c03c30-18d9-4f08-b57f-58d97180c1d9;|EJB5111:Bean class for ejb [content:java.lang.NoSuchMethodException: com.enterprise.entity.ContentBean.getId()] does not define a method corresponding to [Remote] interface method [public abstract java.lang.Integer com.enterprise.entity.ContentRemote.getId() throws java.rmi.RemoteException]
Code snippets of offending classes:
In remote interface:
public interface ContentRemote extends EJBObject {
public Integer getId() throws RemoteException;
}In bean class:
public Integer getId() throws RemoteException {
return new Integer(this.id);
}I think the code is right, please could someone suggest where I am going wrong, this is driving me up the wall.....
Thanks.....
null

Hello,
the build runs a verifier on your EJBs and makes sure everything is in proper order. The ear file holds everything, including the jsps which are inside the war file that gets created.
Regards jP

Deployed webservices is not compatible on sun app server 9

I build my webservices in automated form provided by excelent wizards of jdev.
I was not changed any name, and let all default descriptors generated to after I try to run it, and it run perfectly on oc4j, who is compatible with j2ee specification....
But when I deploy it on Sun App Server 9(stable), the follow error is throwed
"Invalid url pattern" like my screenshot: http://img115.imageshack.us/img115/4673/errojf1.gif
I have tried to replace this url, but without sucess to run my web services. Someone with more experience can help me?
I need to run it on SunAppServer.
Thanks all

You probably need to add the Sun specific deployment descriptor files to your WAR.
JDeveloper doesn't have a utility to do that automatically for Sun.

Deploying a WAR file to Sun App Server 8.1 PE

So I thought that if I downloaded Sun App Server PE 8.1 and put it on my soon-to-be production machine, it should be pretty easy right?
Nope. So I have JSC update 6 (which includes Sun Application Server 8.0) (God how I wish there was a catchy name like Tomcat or something)
And I have a machine running a good copy, installed and everything, of Sun Application Server 8.1 Platform Edition (another catchy name) up on the production target.
I create a WAR file in JSC, scp it up.
Then try to deploy it - so I get bit by the no DB connection thing.
Ok, but when I copy each of my connection's attributes (the driver (which I did copy up to the lib directory) is MySQL's Connector/J)
I copy the username, password, URL and DriverClass attributes to the connection pool.
I still get a
"Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Class name is wrong or classpath is not set for : com.sun.sql.datasource.DriverAdapter"
when I try to Ping the ConnectionPool
I have javax.sql.DataSource as the resource type... (same as 8.0 uses)
what JAR file is DriverAdapter in? anyone know?
cheers,
Kris

Okay. mysql folks - this works......
here's what happened, on the production server, different from the dev machine....
mysql 4.1.9
sun application server platform edition PE 8.1
connector/j - latest
and on the dev machine: JSC Update 6 and the app works fine on the dev machine.
first, there is a JAR file in ~whatever/Create/SunAppServer/lib/ named
driveradaptor.jar
and it it comtains
com.sun.sql.datasource.DriverAdapter
which 8.1 ain't got
and should be copied up to
/installdir/SunAppServer/domains/domain1/lib/ext/driveradapter.jar
(domain1 is your app svr domain that runs your app.)
your Connector/J JAR needs to go here too. I used:
mysql-connector-java-3.2.0-alpha-bin.jar
downloaded from mysql.com.
and then there is the whole thing about Added Properties in the Connection Pool page inside the 8.1 Admin Console (which is nice work guys). Gawd, I added a bunch of properties and am, frankly, not sure which ones actually work (for the Ping, for the initial connection creation and the eventual successful connection all seem to use different combinations...)
and I found this in the domain's domain.xml once all the admin console page filling was done - but you'll need to add each one as a Property in the connection pool:
<jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="com.sun.sql.datasource.DriverAdapter" fail-all-connections="false" [blah...]
<property name="Username" value="root"/>
<property name="Password" value="secret"/>
<property name="ValidationQuery" value="SELECT 1"/>
<property name="DriverClassName" value="com.mysql.jdbc.Driver"/>
<property name="LoginTimeout" value="0"/>
<property name="Url" value="jdbc:mysql://localhost/databasename?autoReconnect=true"/>
<property name="User" value="root"/>
<property name="password" value="secret"/>
<property name="PasswordCredential" value="secret"/>
</jdbc-connection-pool>
(and you see how User and Username and username are all the same thing? well, different parts of 8.1 seem to use different attributes...)
Just keep Adding Properties in the connection pool until you get them all....
Oh and, the two key class references for the pool are:
datasource class: com.sun.sql.datasource.DriverAdapter
resource type: javax.sql.ConnectionPoolDataSource
Finally: in the /installdir/SunAppServer/domains/domain1/applications/j2ee-modules/YourAppName/WEB-INF/
your 'sun-web.xml' (don't delete it, like some have advocated, I think that wrong) needs to look like:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 8.1 Servlet 2.4//EN" "http://www.sun.com/software/appserver/dtds/sun-web-app_2_4-1.dtd">
<sun-web-app xmlns="http://java.sun.com/xml/ns/j2ee">
<context-root>/yourcontext</context-root>
<resource-ref>
<res-ref-name>jdbc/Yourname</res-ref-name>
<jndi-name>jdbc/Yourname</jndi-name>
<default-resource-principal>
<name>root</name>
<password>secret</password>
</default-resource-principal>
</resource-ref>
</sun-web-app>
and I think that's all of it. the only Bug I would I would say is that the sun-web.xml should have the right res-ref-name, but then I think the Creator Team knows this and will fix it sometime soon.
cheers,
and Roger Federer lost in the Aussie Open. (I think he lost tomorrow too, that whole time zone thing being so damn Einsteinian...)
-Kristofer

Problem : App works with Sun App server 8.0 but fails with 8.1

Hi All
     I am experiencing some strange problem with executing my JSF application with Sun App Server.
     I have an EAR deployed on Sun Application Server 8.0 and 8.1.
     Strangely it works quite fine with 8.0 but fails with 8.1.
     In my JSP page ..I have a dummy component whose getter method is used as a "FormLoad" event of the page.
     <h:form id="imageForm" enctype="multipart/form-data">
     <h:messages showDetail="true" />
     <table width="980" border="1" cellpadding="0" cellspacing="0" bordercolor="#A9B8C2">
          <tr>
<td>
               <h:inputHidden value="#{Screen1.initializeService}"/>
          <h:selectOneListbox styleClass="style2" id="cmbMiddleArea" immediate="true" value="#{Screen1.selectedMiddleArea}">
          <f:selectItems value="#{Screen1.middleAreaList}" />
     </h:selectOneListbox>
     In my backing bean i have ..
     public String getInitializeService() {
          ..... Retrieve all the data from DB to initialize all the components on the JSP page
          .......setMiddleAreaList......
          .......setSelectedMiddleArea.....
          ........set the values of the individal component...
     I am retrieving all the data from DB in this getter method and intializing the components on the JSP page.
     I have also checked the code generated for JSP by both the servers.I am posting the code here for reference although
     i did not find any significant difference between the two...
     For Server 8.0
     private boolean jspxmeth_h_inputHidden_0(javax.servlet.jsp.tagext.JspTag jspxth_h_form_0, PageContext jspxpage_context)
     throws Throwable {
     JspWriter out = jspxpage_context.getOut();
     // h:inputHidden
     com.sun.faces.taglib.html_basic.InputHiddenTag jspxth_h_inputHidden_0 = (com.sun.faces.taglib.html_basic.InputHiddenTag) jspxtagPool_h_inputHidden_value.get(com.sun.faces.taglib.html_basic.InputHiddenTag.class);
     jspxth_h_inputHidden_0.setPageContext(_jspx_page_context);
     jspxth_h_inputHidden_0.setParent((javax.servlet.jsp.tagext.Tag) jspxth_h_form_0);
     jspxth_h_inputHidden_0.setValue("#{searchBean.initializeService}");
     int jspxeval_h_inputHidden_0 = jspxth_h_inputHidden_0.doStartTag();
     if (_jspx_th_h_inputHidden_0.doEndTag() == javax.servlet.jsp.tagext.Tag.SKIP_PAGE)
     return true;
     jspxtagPool_h_inputHidden_value.reuse(_jspx_th_h_inputHidden_0);
     return false;
     For Server 8.1
     private boolean jspxmeth_h_inputHidden_0(javax.servlet.jsp.tagext.JspTag jspxth_h_form_0, PageContext jspxpage_context)
     throws Throwable {
     PageContext pageContext = jspxpage_context;
     JspWriter out = jspxpage_context.getOut();
     // h:inputHidden
     com.sun.faces.taglib.html_basic.InputHiddenTag jspxth_h_inputHidden_0 = (com.sun.faces.taglib.html_basic.InputHiddenTag) jspxtagPool_h_inputHidden_value_nobody.get(com.sun.faces.taglib.html_basic.InputHiddenTag.class);
     jspxth_h_inputHidden_0.setPageContext(_jspx_page_context);
     jspxth_h_inputHidden_0.setParent((javax.servlet.jsp.tagext.Tag) jspxth_h_form_0);
     jspxth_h_inputHidden_0.setValue("#{searchBean.initializeService}");
     int jspxeval_h_inputHidden_0 = jspxth_h_inputHidden_0.doStartTag();
     if (_jspx_th_h_inputHidden_0.doEndTag() == javax.servlet.jsp.tagext.Tag.SKIP_PAGE)
     return true;
     jspxtagPool_h_inputHidden_value_nobody.reuse(_jspx_th_h_inputHidden_0);
     return false;
     Now the actual problem is "getInitializeService" method never gets called when i deploy and run the application on Sun App Server8.1
     However with Sun App Server 8.0 it woeks perfectly fine.
     Can anybody help me in resolving these issues ?


Actually generated JSP code can be referred as ...
For Server 8.0
     private boolean jspxmeth_h_inputHidden_0(javax.servlet.jsp.tagext.JspTag jspxth_h_form_0, PageContext jspxpage_context)
     throws Throwable {
     JspWriter out = jspxpage_context.getOut();
     // h:inputHidden
     com.sun.faces.taglib.html_basic.InputHiddenTag jspxth_h_inputHidden_0 = (com.sun.faces.taglib.html_basic.InputHiddenTag) jspxtagPool_h_inputHidden_value.get(com.sun.faces.taglib.html_basic.InputHiddenTag.class);
     jspxth_h_inputHidden_0.setPageContext(_jspx_page_context);
     jspxth_h_inputHidden_0.setParent((javax.servlet.jsp.tagext.Tag) jspxth_h_form_0);
     jspxth_h_inputHidden_0.setValue("#{Screen1.initializeService}");
     int jspxeval_h_inputHidden_0 = jspxth_h_inputHidden_0.doStartTag();
     if (_jspx_th_h_inputHidden_0.doEndTag() == javax.servlet.jsp.tagext.Tag.SKIP_PAGE)
     return true;
     jspxtagPool_h_inputHidden_value.reuse(_jspx_th_h_inputHidden_0);
     return false;
     For Server 8.1
     private boolean jspxmeth_h_inputHidden_0(javax.servlet.jsp.tagext.JspTag jspxth_h_form_0, PageContext jspxpage_context)
     throws Throwable {
     PageContext pageContext = jspxpage_context;
     JspWriter out = jspxpage_context.getOut();
     // h:inputHidden
     com.sun.faces.taglib.html_basic.InputHiddenTag jspxth_h_inputHidden_0 = (com.sun.faces.taglib.html_basic.InputHiddenTag) jspxtagPool_h_inputHidden_value_nobody.get(com.sun.faces.taglib.html_basic.InputHiddenTag.class);
     jspxth_h_inputHidden_0.setPageContext(_jspx_page_context);
     jspxth_h_inputHidden_0.setParent((javax.servlet.jsp.tagext.Tag) jspxth_h_form_0);
     jspxth_h_inputHidden_0.setValue("#{Screen1.initializeService}");
     int jspxeval_h_inputHidden_0 = jspxth_h_inputHidden_0.doStartTag();
     if (_jspx_th_h_inputHidden_0.doEndTag() == javax.servlet.jsp.tagext.Tag.SKIP_PAGE)
     return true;
     jspxtagPool_h_inputHidden_value_nobody.reuse(_jspx_th_h_inputHidden_0);
     return false;
     }

Can I run Servlets in the Sun App Server?

I am trying to run a servlet. I am not sure if I can run the same using the Sun app server. any help to clarify the following queries would be appreciated.
1. Should I have to specify a path in the environmental variables?
2. Is there a web site that tells me the same with respect to running the servlet on a Sun app server.
Thanks in advance.
--Srikanta

I'm not sure what you want in regards to question, but I can assure you that you can run servlets in S1AS7. My recommendation is to just package your servlet into a web archive (war) and deploy it. You can deploy it via the commandline (asadmin) or the web based administrative client (likely http://localhost:4848). For more information on this I suggest reading:
http://docs.sun.com/source/816-7150-10/index.html
You must likely want to read the section on assembling and deploying web applications.
Matt Bauer

What does the Sun App Server Use as a web container?

Does the Sun App Server use tomcat? Or is it some derivative of Tomcat?
thanks for the info.

Thanks.
Just to clarify for any others who are interested, heres the deal:
1) Package the static HTML files using the 'deploytool' (See Packaging Web Modules in Chapter 3 of The J2EE(TM) 1.4 Tutorial). This creates a .war file with the required deployment descriptors(?); anyway it creates a bunch of .xml files that have the right data in them.
2) Take the .war file and drop it in the 'quick deploy' icon (copies the .war file to the 'autodeploy' directory for the App Server instance).
Anyhow thats the drill.
Good luck.

Sun App Server as a Web Server

Can the Sun App Server be used as a simple Web Server (like Apache)? If so, how does one set the root directory for HTML files?
Thanks

Thanks.
Just to clarify for any others who are interested, heres the deal:
1) Package the static HTML files using the 'deploytool' (See Packaging Web Modules in Chapter 3 of The J2EE(TM) 1.4 Tutorial). This creates a .war file with the required deployment descriptors(?); anyway it creates a bunch of .xml files that have the right data in them.
2) Take the .war file and drop it in the 'quick deploy' icon (copies the .war file to the 'autodeploy' directory for the App Server instance).
Anyhow thats the drill.
Good luck.

Sun app server problem using asadmin tool

I have installed sun app server and trying to do the simplemessage tutorial. When I run the
ant create-cfcommand I get the following
[exec] Invalid user or password
[exec] CLI137 Command create-jms-resource failed.I have put an echo line in app-server-ant.xml to see what the command is and it is.
[echo] c:/Sun2/SDK/bin/asadmin.bat create-jms-resource --user admin --passwordfile C:/Sun2/SDK/javaee-5-doc-tutorial-1.0_03/javaeetutorial5/examples/common/admin-password.txt --host localhost --port 4850 --restype javax.jms.ConnectionFactory --enabled=true jms/ConnectionFactoryI have checked the password file and it is
AS_ADMIN_PASSWORD=adminadminAny ideas?
I have checked around about using parameter password but when running this I get an error saying this is not valid and that I should use passwordfile
Kelvin

You haven;t specified the exceptions you r getting ........while starting your default server.
if u r getting exception about InetClass then connect your system with LAN/Internet then your problem will be solved becoz i m using same location address as you specified, space doesn't matter at all - i think so, it is running fine........

Integrating Sun App Server with WebSphere MQ

Hi,
I am using Sun App server V8.1 . I also have a websphere MQ v5.3 installed in my system. I want to integrate this MQ with the App server.
I created a queueManager and a Queue in MQ and using the JMSAdmin console of the Mq, i created jndi lookup resources using INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
In the application server side, i created a Resource adapter using the command:
create-resource-adapter-config --property SupportsXA=true:ProviderIntegrationMode=jndi:RMPolicy=OnePerPhysicalConnection:JndiProperties=java.naming.factory.url.pkgs\\=com.ibm.mq.jms.naming,java.naming.factory.initial\\=com.sun.jndi.fscontext.RefFSContextFactory,java.naming.provider.url\\=file\\:D\\:\\MQ:LogLevel=finest mqra
Then i deployed this resource adaptor using the command :
deploy name mqra target server "D:\Sun\AppServer\lib\addons\resourceadapters\genericjmsra\genericra.rar"
Using this resource adapter i created a connection pool, connector resource and an admin object using the commands
create-connector-connection-pool raname mqra connectiondefinition javax.jms.QueueConnectionFactory transactionsupport XATransaction property ConnectionFactoryJndiName=MQQCF mymqpool
create-connector-resource --poolname mymqpool jms/MyMqQCF
create-admin-object raname mqra restype javax.jms.Queue --property DestinationJndiName=RTQueue jms/MyMqQueue
After that, i wrote a java code to lookup these resources and put a message into the queue.
This is the snippet of my java code
InitialContext ic = new InitialContext();
QueueConnectionFactory cnxFact = (QueueConnectionFactory)ic.lookup("jms/MyMqQCF");
Queue qu = (Queue)ic.lookup("jms/MyMqQueue");
try {
QueueConnection qConn = cnxFact.createQueueConnection();
QueueSession qSess = qConn.createQueueSession(false,Session.AUTO_ACKNOWLEDGE);
QueueSender qSend = qSess.createSender(qu);
TextMessage msg = qSess.createTextMessage();
msg.setText("1");
qSend.send(msg);
qConn.close();
I am getting an exception in the line, QueueConnection qConn = cnxFact.createQueueConnection();
here is the stack trace
java.lang.ClassCastException: com.ibm.mq.jms.MQQueueConnectionFactory
at com.sun.genericra.outbound.ManagedQueueConnectionFactory.createXAConnection(ManagedQueueConnectionFactory.java:45)
at com.sun.genericra.outbound.AbstractManagedConnectionFactory.createPhysicalConnection(AbstractManagedConnectionFactory.java:127)
at com.sun.genericra.outbound.AbstractManagedConnectionFactory.createManagedConnection(AbstractManagedConnectionFactory.java:111)
at com.sun.enterprise.resource.ConnectorAllocator.createResource(ConnectorAllocator.java:90)
at com.sun.enterprise.resource.IASNonSharedResourcePool.getUnenlistedResource(IASNonSharedResourcePool.java:437)
at com.sun.enterprise.resource.IASNonSharedResourcePool.internalGetResource(IASNonSharedResourcePool.java:355)
at com.sun.enterprise.resource.IASNonSharedResourcePool.getResource(IASNonSharedResourcePool.java:250)
at com.sun.enterprise.resource.PoolManagerImpl.getResourceFromPool(PoolManagerImpl.java:213)
at com.sun.enterprise.resource.PoolManagerImpl.getResource(PoolManagerImpl.java:174)
at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:286)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:145)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:121)
at com.sun.genericra.outbound.ConnectionFactory.createConnection(ConnectionFactory.java:69)
at com.sun.genericra.outbound.ConnectionFactory.createQueueConnection(ConnectionFactory.java:101)
Can anybody help???

bump
update:
So to avoid this problem I added spring.jar to the server classpath. that got rid of this message but then it started complaining that its missing struts2 core jar..i added that in server classpath as well...I did same for 4 other files and in the end it said 'bean for xwork has already been initialized' (because all these jars are in the application as well).
So I am stuck. if I add all jars to server classpath..it says beans have already been initialized. If I take out the jars from server classpath then it says that stuff is missing (eg. contextLoader.properties missing - orig post)
again, all this goes away when I restart the server..so i am just trying to avoid having to restart server every code change.

Can JSC support Sun App Server 9?

Does anyone know if JSC can support sun app server 9?
Last I heard was that 8.2 is the max version.
Along the same line, is there any word of another update to JSC
that will work with app server 9 and jdk 6???

Hi!
Actually You can deploy your application to Sun App Server 9.0, but probably not all features will work. But now You can download NetBeans 5.5 and Visual Web Pack for it (it's a next step of Creator's evolution) and this IDE supports GlassFish (opensourced Sun App Server 9.0).
Thanks,
Roman.

Is soap provider agent only available for Sun app server 9.1?

See the blue print on securing web services with soap provider agent. Is this agent embedded within the J2EE agent for sun app server 9.1? Is the same "soap provider agent" available for websphere 6.x or iis server?
Thanks

the agentadmin --install script does not seem to add all the required things to the server-classpath in the domain.xml
mine now looks like this:
/opt/j2ee_agents/appserver_v9_agent/lib/agent.jar
/opt/j2ee_agents/appserver_v9_agent/locale
/opt/j2ee_agents/appserver_v9_agent/Agent_001/config
/opt/j2ee_agents/appserver_v9_agent/lib/amclientsdk.jar
/opt/j2ee_agents/appserver_v9_agent/lib/fmclientsdk.jar
/opt/j2ee_agents/appserver_v9_agent/lib/opensso-installtools.jar
/opt/j2ee_agents/appserver_v9_agent/lib/opensso-installtools-launcher.jar
AND, I've added a system property:
-Dcom.sun.identity.agents.config.location=/opt/j2ee_agents/appserver_v9_agent/Agent_001/config/AMAgent.properties
I now at least get a different error:
Servlet.service() for servlet jsp threw exception
java.lang.ExceptionInInitializerError
     at com.sun.identity.agents.filter.URLPolicyTaskHandler.initialize(URLPolicyTaskHandler.java:63)
com.sun.enterprise.web.HttpServiceWebContainer.service(HttpServiceWebContainer.java:2114)
Caused by: java.lang.RuntimeException: Exception caught in AmWebPolicyManager initializer: Unable to load IAmWebPolicy: com.sun.identity.agents.policy.AmWebPolicy
     at com.sun.identity.agents.policy.AmWebPolicyManager.<clinit>(AmWebPolicyManager.java:135)
     ... 24 more

"Message Driven Bean" doesn't work with Sun App Server

Hello all,
i have a little bit problems, running a simple "Message Driven Bean" under the Sun App Server. The deployment of it works fine, but after starting the SUN App Server i get the following error message:
An error occurred during the message-driven beancontainer initialization at runtime. The most common cause for this is that the physical resource(e.g. Queue) from which the message-driven bean is consuming either does not exist or has been configured incorrectly. Another common error is that the message-driven bean implementation class does not correctly implement the required javax.ejb.MessageBean or MessageListener interfaces.
Has anybody a workaround for this problem?
The queue seems to be correctly installed. A simple client programm from the Sun Tutorial (Consumer & Producer) works fine without any Errors or Exceptions.
I am a little bit confused, because the queue seems to work with the client programms but not with a MDB running on the SUN App Server.
Thanks for you help!
Greetings
Manuel

Hello Mr Manuel!
could you plz help me with the steps for creating a message driven bean using netbeans ver 5.0(with Sun Java� System Application Server Platform Edition 8.2 )
I just know how to work with Session beans & Entity Bean, and am try to learn to work on Message Driven Beans too. there are no proper tutorials where i can find steps for creating these..
I need the steps from the scratch.,like creating QueueConnection Factory & Destination etc..
It will be gr8 if you can help me with this at the earliest .
Thank you
Bye

Opensso.war deployment fails in Sun App server 8.2 windows vissta business

Similar Messages

Maybe you are looking for