CRES BCE_Config_Signed.xml deployment

When I use the "Distribute Signed Configuration to Bulk List" section of the BCE Config, should the installed plugin automatically figure out that to do with it? and shoudln't it come in as a "Securedoc..."???
Right now its coming to my account as just the raw xml, and doesn't seem to be getting picked up by the plugin...

When you distribute a configuration via the CRES admin UI, it's supposed to send envelopes (securedoc....html's) containing the XML to all the recipients. When a recipient decrypts one of the envelopes, the plugin recognizes that it has a BCE config XML attachment and (assuming the signature verifies) apply the configuration in the XML. I'm surprised it's sending the raw XML, that's definitely not how it's supposed to work. I'd suggest opening a support case so it can be investigated.

Similar Messages

The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing

Hello,
I want to create web service from ejb but everytime I want to do it, I get the following error:
I'm using NWDS 7.2 and JDK 1.6
[004]Deployment aborted
Settings
SDM host : XXX
SDM port : 50118
URL to deploy : file:/C:/DOCUME1/XXXX/LOCALS1/Temp/temp3760382784932063822XXXWSProjectEar.ear
Result
=> deployment aborted : file:/C:/DOCUME1/XXX/LOCALS1/Temp/temp3760382784932063822XXX/WSProjectEar.ear
Aborted: development component 'XXXWSProjectEar'/'sap.com'/'localhost'/'2011.01.06.15.48.31'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/XXXWSProjectEar.. Reason: The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing. ; nested exception is: com.sap.engine.services.ejb.exceptions.deployment.EJBXMLParserException: The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
Can anyone tell me why am I getting this error.
Thnx for your help.
Best regards.

Hello Decio Junior,
Actually yes, I resolved my problem.
I'm developing an EJB 3.0 project. I'm using NWDS 7.2 and JDK 1.6 as I said.
The problem is that my server was using JDK 1.4 and that was the problem.
EJB 1.1 and 2.1 need ejb-jar.xml but EJB 3.0 use the annotations instead.
Check your server JDK Version. It should be JDK 1.5 or higher.
Something else that you should check, in your project properties :
In the Build PATH : Use JDK 1.5
In the Java Compiler : Set the java compiler compliance level to 1.6 and check use default compliance settings
Hope it would help.
If you need more explanations, I'm here
Good luck.

Disappearing weblogic.xml deployment descriptor elements

Using WebLogic 8.1 SP1
We have an application that we deploy with a weblogic.xml file. This file has
half-a-dozen deployment descriptor elements, and for some reason I'm unaware of,
several of the parameters specified by these elements are set to their default
values, and these elements don't show up in the weblogic.xml deployment decriptor
when displayed from within the WebLogic Server console. When deploying an exploded
EAR, I can change the value to something non-default , look at the deployment
descriptor and the element appears; change it back and the element is gone.
Is this expected behavior? Is there any configuration setting to display all
the elements no matter the value?
Thanks.

ram ram <> wrote:
should i used new jdk that comes with the upgrade package of 8.1.6 like
(jdk1.4.11)
my class path having the weblogic jar also.
this is my class path.:
E:\bea\weblogic81\server\lib\weblogic.jar and other my application
jars.
Add tools.jar from your Java installation to the classpath.
Bart
Schelstraete Bart
http://www.schelstraete.org
http://www.mqseries.be

XML Deployment Descriptor question

I am upgrading from WebLogic 4.5.1 to WebLogic 5.1 on Solaris 2.6. I
have several entity beans. I created XML deployment descriptors by
running the DDConverter, then splicing the resulting files together (I
had several entity beans in one directory). I've gotten past all the
problems except this last one. I get the following errors from ejbc
when I try to compile:
ERROR: Error from ejbc: Bean provided to WebLogic RDBMS CMP system is
invalid.
Please examine the following exceptions for specific problems:
0: An unknown error occurred while parsing the Weblogic CMP RDBMS
deployment descriptor. Check that the deployment descriptor contains
well-formed and valid XML.
I've checked the weblogic-cmp-rdbms-jar.xml file, compared it to the
examples, and can't find anything wrong with it. However, the WebLogic
examples don't have an example with multiple entity beans in a jar (can
this be done?). Here is the resulting xml file:
<!DOCTYPE weblogic-rdbms-bean PUBLIC
"-//BEA Systems, Inc.//DTD WebLogic 5.1.0 EJB RDBMS Persistence//EN"
"http://www.bea.com/servers/wls510/dtd/weblogic-rdbms-persistence.dtd">
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Address</table-name>
<attribute-map>
<object-link>
<bean-field>entity</bean-field>
<dbms-column>Entity</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>name</bean-field>
<dbms-column>Name</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>File_Cabinet</table-name>
<attribute-map>
<object-link>
<bean-field>folderContainer</bean-field>
<dbms-column>Folder_Container</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>maxCapacity</bean-field>
<dbms-column>Max_Capacity</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list>
<finder>
<method-name>findByHomeDomain</method-name>
<method-params>
<method-param>Long</method-param>
</method-params>
<finder-query><![CDATA[(= homeDomain $0)]]></finder-query>
</finder>
</finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Folder</table-name>
<attribute-map>
<object-link>
<bean-field>documentContainer</bean-field>
<dbms-column>Document_Container</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>name</bean-field>
<dbms-column>Name</dbms-column>
</object-link>
<object-link>
<bean-field>parentFolder</bean-field>
<dbms-column>Parent_Folder</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
<object-link>
<bean-field>fileCabinet</bean-field>
<dbms-column>File_Cabinet</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Origination_Activity</table-name>
<attribute-map>
<object-link>
<bean-field>homeInterface</bean-field>
<dbms-column>Home_Interface</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>type</bean-field>
<dbms-column>Type</dbms-column>
</object-link>
<object-link>
<bean-field>packageSpec</bean-field>
<dbms-column>Package_Spec</dbms-column>
</object-link>
<object-link>
<bean-field>url</bean-field>
<dbms-column>Url</dbms-column>
</object-link>
<object-link>
<bean-field>name</bean-field>
<dbms-column>Name</dbms-column>
</object-link>
<object-link>
<bean-field>displayable</bean-field>
<dbms-column>Displayable</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list>
<finder>
<method-name>findByName</method-name>
<method-params>
<method-param>String</method-param>
</method-params>
<finder-query><![CDATA[(= name $0)]]></finder-query>
</finder>
</finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Package</table-name>
<attribute-map>
<object-link>
<bean-field>forwardIndicator</bean-field>
<dbms-column>Forward_Indicator</dbms-column>
</object-link>
<object-link>
<bean-field>archiveFlag</bean-field>
<dbms-column>Archive_Flag</dbms-column>
</object-link>
<object-link>
<bean-field>beenReadFlag</bean-field>
<dbms-column>Been_Read_Flag</dbms-column>
</object-link>
<object-link>
<bean-field>deleteTimestamp</bean-field>
<dbms-column>Delete_Timestamp</dbms-column>
</object-link>
<object-link>
<bean-field>title</bean-field>
<dbms-column>Title</dbms-column>
</object-link>
<object-link>
<bean-field>sentBy</bean-field>
<dbms-column>Sent_By</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>patientName</bean-field>
<dbms-column>Patient_Name</dbms-column>
</object-link>
<object-link>
<bean-field>type</bean-field>
<dbms-column>Type</dbms-column>
</object-link>
<object-link>
<bean-field>folderName</bean-field>
<dbms-column>Folder_name</dbms-column>
</object-link>
<object-link>
<bean-field>importanceLevel</bean-field>
<dbms-column>Importance_Level</dbms-column>
</object-link>
<object-link>
<bean-field>creationTimestamp</bean-field>
<dbms-column>Creation_Timestamp</dbms-column>
</object-link>
<object-link>
<bean-field>sentTimestamp</bean-field>
<dbms-column>Sent_Timestamp</dbms-column>
</object-link>
<object-link>
<bean-field>sentOnBehalfOf</bean-field>
<dbms-column>Sent_On_Behalf_Of</dbms-column>
</object-link>
<object-link>
<bean-field>sentToAddrContainer</bean-field>
<dbms-column>Sent_To_Addr_Container</dbms-column>
</object-link>
<object-link>
<bean-field>ccToAddrContainer</bean-field>
<dbms-column>CC_To_Addr_Container</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>subject</bean-field>
<dbms-column>Subject</dbms-column>
</object-link>
<object-link>
<bean-field>text</bean-field>
<dbms-column>Text</dbms-column>
</object-link>
<object-link>
<bean-field>parentFolder</bean-field>
<dbms-column>Parent_Folder</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
<object-link>
<bean-field>readBy</bean-field>
<dbms-column>Read_By</dbms-column>
</object-link>
<object-link>
<bean-field>modifiedTimestamp</bean-field>
<dbms-column>Modified_Timestamp</dbms-column>
</object-link>
<object-link>
<bean-field>readTimestamp</bean-field>
<dbms-column>Read_Timestamp</dbms-column>
</object-link>
<object-link>
<bean-field>packageSize</bean-field>
<dbms-column>Package_Size</dbms-column>
</object-link>
<object-link>
<bean-field>creator</bean-field>
<dbms-column>Creator</dbms-column>
</object-link>
<object-link>
<bean-field>lastModifier</bean-field>
<dbms-column>Last_Modifier</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Package_Spec</table-name>
<attribute-map>
<object-link>
<bean-field>templateContainer</bean-field>
<dbms-column>Template_Container</dbms-column>
</object-link>
<object-link>
<bean-field>title</bean-field>
<dbms-column>Title</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>type</bean-field>
<dbms-column>Type</dbms-column>
</object-link>
<object-link>
<bean-field>destinationAddrContainer</bean-field>
<dbms-column>Destination_Addr_Container</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Service_Activity</table-name>
<attribute-map>
<object-link>
<bean-field>serviceContainer</bean-field>
<dbms-column>Service_Container</dbms-column>
</object-link>
<object-link>
<bean-field>homeInterface</bean-field>
<dbms-column>Home_Interface</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>type</bean-field>
<dbms-column>Type</dbms-column>
</object-link>
<object-link>
<bean-field>url</bean-field>
<dbms-column>Url</dbms-column>
</object-link>
<object-link>
<bean-field>name</bean-field>
<dbms-column>Name</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Service</table-name>
<attribute-map>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>packageSpec</bean-field>
<dbms-column>Package_Spec</dbms-column>
</object-link>
<object-link>
<bean-field>name</bean-field>
<dbms-column>Name</dbms-column>
</object-link>
<object-link>
<bean-field>destAddrContainer</bean-field>
<dbms-column>Dest_Addr_Container</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Xml_Default_Doc</table-name>
<attribute-map>
<object-link>
<bean-field>title</bean-field>
<dbms-column>Title</dbms-column>
</object-link>
<object-link>
<bean-field>docSize</bean-field>
<dbms-column>Doc_Size</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>text</bean-field>
<dbms-column>Text</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Xml_Doc_Template</table-name>
<attribute-map>
<object-link>
<bean-field>dtdOid</bean-field>
<dbms-column>DTD_OID</dbms-column>
</object-link>
<object-link>
<bean-field>title</bean-field>
<dbms-column>Title</dbms-column>
</object-link>
<object-link>
<bean-field>viewStyleSheetOid</bean-field>
<dbms-column>View_Style_Sheet_OID</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>defaultDocOid</bean-field>
<dbms-column>Default_Doc_OID</dbms-column>
</object-link>
<object-link>
<bean-field>editStyleSheetOid</bean-field>
<dbms-column>Edit_Style_Sheet_OID</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Xml_Dtd</table-name>
<attribute-map>
<object-link>
<bean-field>title</bean-field>
<dbms-column>Title</dbms-column>
</object-link>
<object-link>
<bean-field>docSize</bean-field>
<dbms-column>Doc_Size</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>version</bean-field>
<dbms-column>Version</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>text</bean-field>
<dbms-column>Text</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Xml_Stylesheet</table-name>
<attribute-map>
<object-link>
<bean-field>title</bean-field>
<dbms-column>Title</dbms-column>
</object-link>
<object-link>
<bean-field>docSize</bean-field>
<dbms-column>Doc_Size</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>version</bean-field>
<dbms-column>Version</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>text</bean-field>
<dbms-column>Text</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
Have Fun!
Lea Anne Troeger
Software Engineer
Telesynthesis, Inc.
[email protected]

There is one pool per RA (ra.xml/weblogic-ra.xml). One way to get almost what I think you
          are after is to use the <ra-link-ref> facility in WLS 6.1.
          HTH.
          YiQing Yang wrote:
          > Hi there,
          >
          > I have a question about connector. In weblogic-ra.xml Deployment Descriptor, you
          > define the parameters for connection factory and connection pool. Can you only
          > define one connection factory and connection pool or you can define more than
          > one? In other words, for each deployed connector, can it have more than one connection
          > pool?
          > Your help is appreciated.
          >
          > Thanks,
          >
          > YiQing Yang
          Tom Mitchell
          [email protected]
          Very Current Beverly, MA Weather
          http://www.tom.org:8080

Integrating orion-application.xml deployment with JDeveloper?

Hi all,
I am trying to create JAAS secured web/ear application but haven't found the
way to integrate the orion-application.xml file in the JDeveloper
deployment process. An alternative would be to insert orion-application.xml tags
into orion-web.xml and copy this one to the usual WEB-INF along with web.xml
another possibility would be directly copying orion-application.xml to the
%J2EE_HOME%\application-deployments\MyApp\orion-application.xml after deployed
in the OC4J Server, but would be lot easier just having JDeveloper deploy it
automatically, what is the way to do it?
Regards,
Giovanni

See http://forums.oracle.com/forums/message.jsp?id=978411&gid=315684

Missing data-sources.xml deploying war with jdeveloper 9i RC

When deploying a war file to an OC4J 1.0.2.2.1 server and error reports during the deployment that data-sources.xml is missing in the application-deployments/xxxx directory. Only the orion-application.xml file is present - which references a data-sources.xml file in the same directory. The problem is : it isn't there.
When I copy the xml files from the applications/xxxx directory to the application-deployments/xxxx directory and redeploy the war file everything works fine.
Is this a configuration issue or a bug ? Anyway, can somebody tell me how I can work around this problem ?
Thanks !

this is a bug and you have already found the workaround.

Build.xml deployment

I would like to replicate the action of JDeveloper compiling and deploying a given process to a remote BPEL PM Server.
When I establish the BPELPM server connection in jdev, I just specify the host/port and I'm prompted for password and domain at deployment time.
How can I replicate this in a build.xml using obant? The server is running on midtier of OAS on an OC4J titled OC4J_BPEL.
My real objective is to deploy to multiple servers in the same script, but need to get one working first.

I'd like to use the 'scp' ANT task via obant but it does not seem to be available with the default configuration. I fetched the jsh jar file as instructed by the ANT manual (http://ant.apache.org/manual/OptionalTasks/scp.html).
I'm still not able to use the 'scp' task. Below is the output from obant upon reading the 'scp' task:
Ant could not find the task or a class this task relies upon.
This is common and has a number of causes; the usual
solutions are to read the manual pages then download and
install needed JAR files, or fix the build file:
- You have misspelt 'scp'.
Fix: check your spelling.
- The task needs an external JAR file to execute
and this is not found at the right place in the classpath.
Fix: check the documentation for dependencies.
Fix: declare the task.
- The task is an Ant optional task and the JAR file and/or libraries
implementing the functionality were not found at the time you
yourself built your installation of Ant from the Ant sources.
Fix: Look in the ANT_HOME/lib for the 'ant-' JAR corresponding to the
task and make sure it contains more than merely a META-INF/MANIFEST.MF.
If all it contains is the manifest, then rebuild Ant with the needed
libraries present in ${ant.home}/lib/optional/ , or alternatively,
download a pre-built release version from apache.org
- The build file was written for a later version of Ant
Fix: upgrade to at least the latest release version of Ant
- The task is not an Ant core or optional task
and needs to be declared using <taskdef>.
- You are attempting to use a task defined using
<presetdef> or <macrodef> but have spelt wrong or not
defined it at the point of use
Remember that for JAR files to be visible to Ant tasks implemented
in ANT_HOME/lib, the files must be in the same directory or on the
classpath
Please neither file bug reports on this problem, nor email the
Ant mailing lists, until all of these causes have been explored,
as this is not an Ant bug.

XML deployment descriptor generation

How to let OC4J automatically generate ejb-jar.xml, orion-ejb-jar.xml, web.xml for me? It is a nightmare to write these deployment descriptor by hand.
By the way, I know that JDeveloper can generate this for us, but I am not using JDeveloper 9i. Can we just let OC4J generate these files for us?
Thanks.

How to let OC4J automatically generate ejb-jar.xml, orion-ejb-jar.xml, web.xml for me? It is a nightmare to write these deployment descriptor by hand.
By the way, I know that JDeveloper can generate this for us, but I am not using JDeveloper 9i. Can we just let OC4J generate these files for us?
Thanks. Hi,
there is no way (so far as I know) that an J2EE Application server (what oc4j is) makes the deployment descriptors, that's why they are called deployment descriptors, without them you can't deploy on any Application server.
I personally use JDeveloper, but most current JAVA IDE's support generation of deployment descriptors.
Basically my approach is to define the architecture within Rational Rose, which generates for me the stubs for the classes and for every ejb a deployment descriptor, later I copy all of them into one ejb-jar.xml and open the whole bunch with JDeveloper, it works fine with 903 preview, although there are some problems with the 902 version of JDeveloper.
Which IDE are you using?
--hery

How to edit web.xml deployment descriptor from console in weblogic 8.1?

In weblogic 7.0, deployment descriptor such as web.xml can be edited from the admin
console, but on weblogic 8.1 I can't find a way to do so.
Is this function taken out? Why is it taken out? Do I have an alternative to edit
it without unpacking and packing the EAR or WAR?
Thanks in advance.
Bill

In weblogic 7.0, deployment descriptor such as web.xml can be edited from the admin
console, but on weblogic 8.1 I can't find a way to do so.
Is this function taken out? Why is it taken out? Do I have an alternative to edit
it without unpacking and packing the EAR or WAR?
Thanks in advance.
Bill

Jboss kodo-service.xml deploy problem

Hi,
I'm trying to deploy kodo-service.xml in jboss-3.0.0RC1 and get this error:
2002-06-11 13:48:06,030 ERROR [org.jboss.deployment.MainDeployer] could
not start deployment
:file:/D:/jbossrc1/server/default/deploy/kodo-service.xml
java.lang.AbstractMethodError
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.<init>(JDBCPersistenceManagerFactory.java:153)
at
com.solarmetric.kodo.impl.jdbc.ee.EEPersistenceManagerFactory.<init>(EEPersistenceManagerFactory.java:53)
at
com.solarmetric.kodo.impl.jdbc.ee.JDOConnectionFactory.<init>(JDOConnectionFactory.java:41)
I get the same error using the default kodo-service.xml file included with
the downloaded package.
Any ideas?
Thanks!
Jesper

Note that neither Kodo JDO 2.3.0 beta nor Kodo JDO 2.2.5 does not exhibit
the 1.4 problem.
-Patrick
On 6/11/02 8:07 AM, "Jesper Ladegaard" <[email protected]> wrote:
Okay,
I can see from some other post it\'s a Java 1.4 problem.
/Jesper
Patrick Linskey [email protected]
SolarMetric Inc. http://www.solarmetric.com

WebSphere ServerRepository.xml / Deployed WAR Works, LH Command Line Fails

Anyone deploying to WebSphere that has gotten the LH Command Line tool to function with a ServerRepository.xml pointing to a DataSource within WebSphere?
We created a ServerRepository.xml that utilizes the WebSphere DataSource as the Performance is significantly greater for the idm.war deployed to WAS. The idm.war file works & performs better using this.
LH Command line fails with a ServerRepository.xml pointing to a WebSphere DataSource. I've been troubleshooting with SUN support & so far we have not made any progress to resolve this. LH fails trying to execute anything...see below for example & partial cut/pasted error message.
**set WSHOME, JAVA_HOME, & WAS_HOME 1st
$WSHOME/bin/lh -Djava.ext.dirs=$JAVA_HOME/jre/lib/ext:$WAS_HOME/lib:/ebiz/sim/dev/lib console -u configurator
Error:
com.waveset.util.InternalError:
==> com.waveset.util.ConfigurationError:
==> java.sql.SQLException: invalid arguments in callDSRA0010E: SQL State = null, Error Code = 17,433DSRA0010E: SQL State = null, Error Code = 17,433
at com.waveset.repository.ServerRepository.initDataStore(ServerRepository.java:1527)
at com.waveset.repository.ServerRepository.getPrimaryDataStore(ServerRepository.java:1343)
at com.waveset.repository.ServerRepository.getPrimaryDataStore(ServerRepository.java:1309)
at com.waveset.repository.ServerRepository.init(ServerRepository.java:717)
at com.waveset.repository.ServerRepository.<init>(ServerRepository.java:693)
at com.waveset.repository.ServerRepository.getRepository(ServerRepository.java:134)
at com.waveset.server.Server.init(Server.java:251)
at com.waveset.server.Server.start(Server.java:217)
at com.waveset.server.Server.getServer(Server.java:807)
at com.waveset.server.Server.getServer(Server.java:784)
at com.waveset.session.SessionFactory.getLoginConfigInfo(SessionFactory.java:849)
at com.waveset.session.SessionFactory.startupMode(SessionFactory.java:916)
at com.waveset.session.SessionFactory.getLoginModGrp(SessionFactory.java:885)
at com.waveset.session.SessionFactory.getSession(SessionFactory.java:170)
at com.waveset.session.SessionFactory.getSession(SessionFactory.java:390)
at com.waveset.session.SessionFactory.getSession(SessionFactory.java:456)
at com.waveset.session.WavesetConsole.newSession(WavesetConsole.java:361)
at com.waveset.session.WavesetConsole.start(WavesetConsole.java:331)
at com.waveset.session.WavesetConsole.main(WavesetConsole.java:218)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.waveset.util.CommandProcess.invokeMain(CommandProcess.java:212)
at com.waveset.util.CommandProcess.launch(CommandProcess.java:162)
at com.waveset.util.CommandProcess.run(CommandProcess.java:300)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.waveset.util.Command.main(Command.java:96)
Wrapped exception:
Architecture:
IDM 7.0
WebSphere 6.x
Oracle THIN Driver ojdbc14.jar - 10.2.0.x
AIX 5.3 ML3

To get the WAR deployed within WebSphere to function, I found the IDM Doc (IDM 7.0 Installation - "Configuring a WebSphere DataSource for Identity Manager" - Pgs 117 - 134) to be pretty decent for creating the actual JDBC DataSource.
My recommendation is to setup the DataSource at the Scope=Cell Level & use a WAS J2C Auth Entry for the DataSource so you do not need to use the -U or -P options in your setRepo command...this also helps ensure its truly connecting using WAS.
Looking at what you had, try this modified...
$WSHOME/bin/lh -Djava.ext.dirs=$JAVA_HOME/jre/lib/ext:$WAS_HOME/lib setRepo -n -tSQLServer -icom.ibm.websphere.naming.WsnInitialContextFactory -fjdbc/idm -uiiop://localhost:9810 -o"D:\apps\temp.xml"
*Additional comments
-n will bypass any checking and ignore any error message.
-f must be identical to the WAS JDBC DataSource Name jdbc/idm
**You do not need to redeploy after replacing the ServerRepository.xml; however, you do need to bounce the WAS AppServer & should monitor the AppServer SystemOut.log on startup to ensure the IDM WAR starts up successfully
***This is all assuming the DataSource you have within WAS is working (you can validate via the TestConnection)

JWSDP1.3 - 'pre-installed' XML deployment files

In the current JWSDP-1.3 Tutorial, there is the following text on p. 810 (chapter on JSF):
"Running the Examples Using the Pre-Installed XML Files
The Java WSDP 1.3 includes an XML file for each example application in the <JWSDP_HOME>/webapps directory. This file causes an application to be automatically deployed when you start Tomcat...."
However, in the JWSDP-1.3 (installable download), those files are not there (I have downloaded and installed it twice).
I assume this is an error. Where are these files in the v 1.3 release? How are they used? There appears to be inconsitencies between the 1.2 and 1.3 directory/file locations as indicated in the Tutorial documentation.
Thanks

You are right. The location of the context files changed in
1.3. They are now located in <jwsdp_home>/conf/Catalina/locahost.
Tom

SessionManager with XML deployment project problem

I switched over from DatabaseSession to using SessionManager. In my DatabaseSession code I had code like this to add two descriptors to the project:
        m_project = XMLProjectReader.read(fileName,
                RepositoryFactoryTLImpl.class.getClassLoader());
        m_project.addDescriptor(buildHoleToFlangeLimitDTOImplDescriptor());
        m_project.addDescriptor(buildHoleToWebLimitDTOImplDescriptor());
        m_session = m_project.createDatabaseSession();After changing to using SessionManager I have:
        m_serverSession = (ServerSession)SessionManager.
                getManager().getSession("FPRSAcceptanceRepos");
        m_project = m_serverSession.getProject();
        m_project.addDescriptor(buildHoleToFlangeLimitDTOImplDescriptor());
        m_project.addDescriptor(buildHoleToWebLimitDTOImplDescriptor());HOWEVER... all my tests work fine EXCEPT those whose descriptors are added in the Java code. I get 'Invalid query key in expression' errors like this one below.
LOCAL EXCEPTION STACK:
EXCEPTION [TOPLINK-6015] (TopLink - 9.0.3.1 (Build 426)): oracle.toplink.exceptions.QueryException
EXCEPTION DESCRIPTION: Invalid query key [materialCode] in expression.
QUERY: ReadAllQuery(com.metalsa.orator.fprs.db.HoleLimitDTOImpl$Flange)
     oracle.toplink.exceptions.QueryException oracle.toplink.exceptions.QueryException.invalidQueryKeyInExpression(java.lang.Object)
     oracle.toplink.expressions.Expression oracle.toplink.internal.expressions.RelationExpression.normalize(oracle.toplink.internal.expressions.ExpressionNormalizer)
     oracle.toplink.expressions.Expression oracle.toplink.internal.expressions.CompoundExpression.normalize(oracle.toplink.internal.expressions.ExpressionNormalizer)
     void oracle.toplink.internal.expressions.SQLSelectStatement.normalize(oracle.toplink.publicinterface.Session, oracle.toplink.publicinterface.Descriptor)
     oracle.toplink.internal.expressions.SQLSelectStatement oracle.toplink.internal.queryframework.ExpressionQueryMechanism.buildNormalSelectStatement()
     void oracle.toplink.internal.queryframework.ExpressionQueryMechanism.prepareSelectAllRows()
     void oracle.toplink.queryframework.ReadAllQuery.prepareSelectAllRows()
     void oracle.toplink.queryframework.ReadAllQuery.prepare()
     void oracle.toplink.queryframework.DatabaseQuery.checkPrepare(oracle.toplink.publicinterface.Session, oracle.toplink.publicinterface.DatabaseRow)
     java.lang.Object oracle.toplink.queryframework.DatabaseQuery.execute(oracle.toplink.publicinterface.Session, oracle.toplink.publicinterface.DatabaseRow)
     java.lang.Object oracle.toplink.queryframework.ReadQuery.execute(oracle.toplink.publicinterface.Session, oracle.toplink.publicinterface.DatabaseRow)
     java.lang.Object oracle.toplink.publicinterface.Session.internalExecuteQuery(oracle.toplink.queryframework.DatabaseQuery, oracle.toplink.publicinterface.DatabaseRow)
     java.lang.Object oracle.toplink.threetier.ServerSession.internalExecuteQuery(oracle.toplink.queryframework.DatabaseQuery, oracle.toplink.publicinterface.DatabaseRow)
     java.lang.Object oracle.toplink.threetier.ClientSession.internalExecuteQuery(oracle.toplink.queryframework.DatabaseQuery, oracle.toplink.publicinterface.DatabaseRow)
     java.lang.Object oracle.toplink.publicinterface.Session.executeQuery(oracle.toplink.queryframework.DatabaseQuery, oracle.toplink.publicinterface.DatabaseRow)
     java.lang.Object oracle.toplink.publicinterface.UnitOfWork.internalExecuteQuery(oracle.toplink.queryframework.DatabaseQuery, oracle.toplink.publicinterface.DatabaseRow)
     java.lang.Object oracle.toplink.publicinterface.Session.executeQuery(oracle.toplink.queryframework.DatabaseQuery, oracle.toplink.publicinterface.DatabaseRow)
     java.lang.Object oracle.toplink.publicinterface.Session.executeQuery(oracle.toplink.queryframework.DatabaseQuery)
     java.util.Collection com.metalsa.orator.fprs.db.HoleSetupReposTLImpl.getHoleLimits(java.lang.Class, java.lang.String, java.lang.String)
          HoleSetupReposTLImpl.java:105
     java.util.Collection com.metalsa.orator.fprs.db.HoleSetupReposTLImpl.getHoleToFlangeLimits(java.lang.String, java.lang.String)
          HoleSetupReposTLImpl.java:73
     void com.metalsa.orator.fprs.db.HoleSetupReposTest.getHoleLimits(com.metalsa.orator.fprs.db.HoleSetupReposTest$GetHoleLimitsParms, java.util.Collection)
          HoleSetupReposTest.java:462
     void com.metalsa.orator.fprs.db.HoleSetupReposTest.testGetHoleToFlangeLimits()
          HoleSetupReposTest.java:427
          native code
          TestCase.java:166
          TestCase.java:139
          TestResult.java:106
          TestResult.java:123
          TestResult.java:109
          TestCase.java:131
          TestSuite.java:173
          TestSuite.java:168
          TestRunner.java:644

Hi,
Using the SessionManager you already logged into the DB and run the TopLink validate before you tried to add your query key.
Option # 1 -
Please try to use the preLogin event. It should look something like this:
1) In sessions.xml <event-listener-class>EventDemo</event-listener-class>
2) In EventDemo.java you should have something like
public class EventDemo extends SessionEventAdapter
public void preLogin(SessionEvent evt) {
evt.getSession().getProject().addDescriptor(buildHoleToFlangeLimitDTOImplDescriptor());
evt.getSession().getProject().addDescriptor(buildHoleToWebLimitDTOImplDescriptor());
Option # 2
Build the ServerSession in the code
m_project = XMLProjectReader.read(fileName, RepositoryFactoryTLImpl.class.getClassLoader());
m_project.addDescriptor(buildHoleToFlangeLimitDTOImplDescriptor());
m_project.addDescriptor(buildHoleToWebLimitDTOImplDescriptor());
m_session = m_project.createServerSession(1, 2);
m_session.useExclusiveReadConnectionPool(2, 5);
m_session.logMessages();
. Etc .
m_session.login();
Raanan.

Web.xml deployment - The requested resource is not available

I am trying to deploy part of my project and cannot get it to work.
If I put this in:
<url-pattern>/traveltimes.do</url-pattern>and go to http://localhost/testLINK/traveltimes.do it works fine.
However when I put
<url-pattern>/milwaukee/traveltimes.do</url-pattern>and go to
http://localhost/testLINK/milwaukee/traveltimes.do
I get this error:
The requested resource (/milwaukee/milwaukee/traveltimes.jsp) is not available.I can't figure out why it is putting in that extra /milwaukee. Any ideas?
John

Well here is something really weird. If I change it to:
<servlet-name>Milwaukee Travel Times</servlet-name>
<url-pattern>/test/traveltimes.do</url-pattern>and go to http://localhost/testLINK/test/traveltimes.do
I get
/test/milwaukee/traveltimes.jspis not available. I have no idea where it is pulling that milwaukee from, and why it does so only when I have the extra level in the path.
Any ideas on where I can go from here?
John

XML Deployment

Does anyone know the XML to make a .jsp page able to download from behind the WEB-INF folder?

Sorry, I mean't .txt files, just stuff to download.....

CRES BCE_Config_Signed.xml deployment

Similar Messages

Maybe you are looking for