Add weblogic.properties to the weblogic.

hi people
          how do i can to tell to the weblogic to start with another
          weblogic.properties when he starts,
          that is, to start with the weblogic.properties and other property into
          another directory ?
          any help will be appreciated

You can set the system property weblogic.system.name:
          java ... -Dweblogic.system.name=foo ... weblogic.Server,
          and create directory 'foo' and put server-specific weblogic.properties
          there.
          ruben <[email protected]> wrote:
          > hi people
          > how do i can to tell to the weblogic to start with another
          > weblogic.properties when he starts,
          > that is, to start with the weblogic.properties and other property into
          > another directory ?
          > any help will be appreciated
          Dimitri

Similar Messages

Add OWN property to the weblogic.properties

Hi.
I tried to add my own property to the weblogic.properties.
ERROR: "Found undeclared property"
Is it at all possible?
TIA,

If you simply want to define a Java System property, you can do that
like so:
java.system.property.my.property=foo
This has the same effect as using the -Dmy.property=foo argument to the
JVM and is retrievable programmatically by calling
System.getProperty("my.property")
Hope this helps,
Robert
Daniel Ilkanayev wrote:
Hi.
I tried to add my own property to the weblogic.properties.
ERROR: "Found undeclared property"
Is it at all possible?
TIA,

How do I add calculating properties to the fields?

Used a template on Forms Central and made some changes. Trying to add calculating fields to three of the text fields and one drop down box but can't find how to do this? Have double clicked on the text or drop down box but the properties does not have a calculation tab?? using Adobe Pro XI. thanks in advance for your help.

So is this a PDF form or a FormsCentral form? The two are quite different.
On Fri, Dec 5, 2014 at 9:12 AM, Vikrantt Singh <[email protected]>

Help: why I cannot find the weblogic.mycluster.properties file

When I first config the cluster. While Setting up the weblogic.properties
          Files, Open and read the cluster properties file (installed by default as
          weblogic/mycluster). Any properties set in the cluster properties file will
          override the same properties that were set from the global properties file.
          But I cannot find this file, Also I copy the weblogic.properties to
          weblogic.mycluster.properties,Also,I cannot find the
          weblogic.cluster.enable=true,etc.
          thanks


It is required to put it in command line.
          Cheers - Wei
          Atish Ray <[email protected]> wrote in message
          news:[email protected]...
          > What happens if I set this property thru the properties file ? It still
          > works. Is there a known problem on this ?
          >
          >
          >
          > Wei Guan wrote in message <[email protected]>...
          > >Yes, the default cluster name is mycluster.
          > >
          > >Create an directory named 'mycluster' under your weblogic home, copy
          > >weblogic.properties to mycluster/weblogic.properties will do the trick.
          > >
          > >weblogic.cluster.enable=true has to be set via command-line. That is, add
          > >'-Dweblogic.cluster.enable=true' in your startup script.
          > >
          > >--
          > >Cheers - Wei
          > >
          > >
          > >
          > >hhb <[email protected]> wrote in message
          > >news:[email protected]...
          > >> When I first config the cluster. While Setting up the
          weblogic.properties
          > >> Files, Open and read the cluster properties file (installed by default
          as
          > >> weblogic/mycluster). Any properties set in the cluster properties file
          > >will
          > >> override the same properties that were set from the global properties
          > >file.
          > >> But I cannot find this file, Also I copy the weblogic.properties to
          > >> weblogic.mycluster.properties,Also,I cannot find the
          > >> weblogic.cluster.enable=true,etc.
          > >>
          > >> thanks
          > >>
          > >>
          > >>
          > >
          > >
          >
          >

Add weblogic.properties

hi people
how do i can to tell to the weblogic to start with another
weblogic.properties when he starts,
that is, to start with the weblogic.properties and other property into
another directory ?
any help will be appreciated

ruben <[email protected]> wrote:
          > another cuestion,
          > i have into the starting of the weblogic this sentences:
          > lun nov 27 12:56:49 GMT+01:00 2000:<I> <WebLogicServer> Read global
          > properties c:\weblogic\weblogic.properties
          > lun nov 27 12:56:49 GMT+01:00 2000:<I> <WebLogicServer> No per-server
          > properties files found
          > how do i config the weblogic to have yes into per-erver properties file
          > found
          This means that you have directory with the same name as system name, but there
          is no weblogic.properties file there.
          The order in which weblogic reads weblogic.properties files is like this:
          weblogic_home/weblogic.properties
          weblogic_home/cluster_name/weblogic.properties (if clustering is enabled)
          weblogic_home/cluster_name/system_name/weblogic.properties
          or
          weblogic_home/system_name/weblogic.properties (if clustering is disabled)
          Dimitri

Unable to execute the cmp using the weblogic

I was trying to execute cmp using weblogic server7.0.
It a simple program,
The remote interface-
import javax.ejb.*;
import java.rmi.RemoteException;
public interface SportTeam extends EJBObject{
public void setOwnerName(String ownerName) throws RemoteException;
public String getOwnerName() throws RemoteException;
public void setFranchiseName(String franchiseName) throws RemoteException;
public String getFranchiseName() throws RemoteException;
}The home interface
import javax.ejb.*;
import java.rmi.RemoteException;
import java.util.Collection;
public interface SportTeamHome extends EJBHome{
SportTeam create(String sport,String nickName)throws RemoteException,CreateException;
SportTeam create(String sport,String nickName,String ownerName,String franchisePlayer)throws RemoteException,CreateException;
SportTeam findByPrimaryKey(SportTeamPK sportTeam) throws RemoteException,FinderException;
Collection findByOwnerName(String ownerName) throws RemoteException,FinderException;
}The bean
import javax.ejb.*;
import javax.naming.*;
import java.rmi.RemoteException;
import java.sql.*;
import java.util.*;
public abstract class SportTeamEJB implements EntityBean{
public SportTeamPK ejbCreate(String sport,String nickName) throws CreateException {
setSport(sport);
setNickName(nickName);
setOwnerName(null);
setFranchiseName(null);
return null;
public void ejbPostCreate(String sport,String nickName){}
public SportTeamPK ejbCreate(String sport,String nickName,String ownerName,String franchiseName) throws CreateException {
setSport(sport);
setNickName(nickName);
setOwnerName(ownerName);
setFranchiseName(franchiseName);
return null;
public void ejbPostCreate(String sport,String nickName,String ownerName,String franchiseName){}
public void ejbLoad(){}
public void ejbStore(){}
public void ejbRemove(){}
public void ejbActivate(){}
public void ejbPassivate(){}
public void setEntityContext(EntityContext ctx){}
public void unsetEntityContext(){}
abstract public String getSport();
abstract public void setSport(String sport);
abstract public String getNickName();
abstract public void setNickName(String nickName);
abstract public String getOwnerName();
abstract public void setOwnerName(String ownerName);
abstract public String getFranchiseName();
abstract public void setFranchiseName(String franchiseName);
}the client side program
import java.rmi.RemoteException;
import javax.ejb.*;
import javax.naming.*;
import javax.rmi.PortableRemoteObject;
import java.util.Properties;
import java.util.Collection;
import java.util.Iterator;
public class TestClient{
public static void main(String[] args){
try{
     Properties prop=new Properties();
     prop.setProperty(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
     prop.setProperty(Context.PROVIDER_URL,"t3://localhost:7001");
     InitialContext initial=new InitialContext(prop);
     Object objref=initial.lookup("CMPSportBean");
     SportTeamHome home=(SportTeamHome)PortableRemoteObject.narrow(objref,SportTeamHome.class);
     System.out.println("Creating a row.");
     home.create("basketball","Kings","Joe Maloof","Jason Williams");
     System.out.println("Looking up by primary key...");
     SportTeam team=home.findByPrimaryKey(new SportTeamPK("basketball","Kings"));
     System.out.println("Current franchise player:");
     System.out.println(team.getFranchiseName());
     System.out.println("Looking by by owner...");
     Collection col=home.findByOwnerName("Joe Maloof");
     if(     0 == col.size()     ){
          System.out.println("Found no such owner");
     }else {
          Iterator iter=col.iterator();
          while(iter.hasNext()){
          Object objref2=iter.next();
          SportTeam teamRef2=(SportTeam) PortableRemoteObject.narrow(objref2,SportTeam.class);
          System.out.println("Owner name:"+ teamRef2.getOwnerName());
team.remove();
}catch(RemoveException re){
     re.printStackTrace();
}catch(NamingException ne){
     ne.printStackTrace();
}catch(CreateException ce){
     ce.printStackTrace();
}catch(FinderException fe){
     fe.printStackTrace();
}catch(RemoteException re){
              re.printStackTrace();
}The primary key class
//package sportBean.cmp;
import java.io.Serializable;
public class SportTeamPK implements Serializable{
public String sport;
public String nickName;
public SportTeamPK(){}
public SportTeamPK(String sport,String nickName){
this.sport =sport;
this.nickName=nickName;
public String getSport(){
return sport;
public String getNickName(){
return nickName;
public int hashCode(){
return (sport+nickName).hashCode();
public boolean equals(Object other){
     if( (other == null) ||! (other instanceof SportTeamPK) ){
        return false;
     SportTeamPK otherPK=(SportTeamPK)other;
     return sport.equals(otherPK.sport) && nickName.equals(otherPK.nickName);
The program has complied successfully .
The META-INF directory has been created automatically
the ejb-jar.xml file
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>

<ejb-jar>
<enterprise-beans>
    <entity>
      <ejb-name>CMPSportBean</ejb-name>
      <home>SportTeamHome</home>
      <remote>SportTeam</remote>
      <ejb-class>SportTeamEJB</ejb-class>
      <persistence-type>Container</persistence-type>
      <prim-key-class>SportTeamPK</prim-key-class>
      <reentrant>False</reentrant>
      <abstract-schema-name>SportEJB</abstract-schema-name>
      <cmp-field>
        <field-name>sport</field-name>
      </cmp-field>
      <cmp-field>
        <field-name>nickName</field-name>
      </cmp-field>
      <cmp-field>
        <field-name>ownerName</field-name>
      </cmp-field>
      <cmp-field>
        <field-name>franchiseName</field-name>
      </cmp-field>
      <query>
        <query-method>
          <method-name>findByOwnerName</method-name>
          <method-params>
            <method-param>java.lang.String</method-param>
          </method-params>
        </query-method>
        <ejb-ql><![CDATA[SELECT OBJECT(o) FROM SportEJB AS o WHERE o.ownerName=?1]]></ejb-ql>
      </query>
    </entity>
</enterprise-beans>
<assembly-descriptor>
</assembly-descriptor>
</ejb-jar>the weblogic-ejb-jar.xml file
<!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB//EN' 'http://www.bea.com/servers/wls700/dtd/weblogic-ejb-jar.dtd'>

<weblogic-ejb-jar>
<weblogic-enterprise-bean>
    <ejb-name>CMPSportBean</ejb-name>
    <entity-descriptor>
      <pool>
      </pool>
      <entity-cache>
        <max-beans-in-cache>1000</max-beans-in-cache>
        <idle-timeout-seconds>600</idle-timeout-seconds>
        <read-timeout-seconds>600</read-timeout-seconds>
        <cache-between-transactions>False</cache-between-transactions>
      </entity-cache>
      <persistence>
        <persistence-use>
          <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
          <type-version>6.0</type-version>
          <type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
        </persistence-use>
      </persistence>
      <entity-clustering>
      </entity-clustering>
    </entity-descriptor>
    <transaction-descriptor>
      <trans-timeout-seconds>2</trans-timeout-seconds>
    </transaction-descriptor>
    <jndi-name>CMPSportBean</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>the weblogic-cmp-rdbms-jar.xml file
<!DOCTYPE weblogic-rdbms-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB RDBMS Persistence//EN' 'http://www.bea.com/servers/wls700/dtd/weblogic-rdbms20-persistence-700.dtd'>

<weblogic-rdbms-jar>
<weblogic-rdbms-bean>
    <ejb-name>CMPSportBean</ejb-name>
    <data-source-name>myjdbcjndi</data-source-name>
    <table-map>
      <table-name>sportsteams</table-name>
      <field-map>
        <cmp-field>ownerName</cmp-field>
        <dbms-column>ownername</dbms-column>
      </field-map>
      <field-map>
        <cmp-field>franchiseName</cmp-field>
        <dbms-column>franchisename</dbms-column>
      </field-map>
      <field-map>
        <cmp-field>nickName</cmp-field>
        <dbms-column>nickname</dbms-column>
      </field-map>
      <field-map>
        <cmp-field>sport</cmp-field>
        <dbms-column>sport</dbms-column>
      </field-map>
    </table-map>
    <weblogic-query>
      <query-method>
        <method-name>findByOwnerName</method-name>
        <method-params>
          <method-param>java.lang.String</method-param>
        </method-params>
      </query-method>
    </weblogic-query>
    <check-exists-on-method>False</check-exists-on-method>
</weblogic-rdbms-bean>
<create-default-dbms-tables>True</create-default-dbms-tables>
</weblogic-rdbms-jar>I tried to write config.xml file
<JDBCDataSource
   Name=" "
   JNDIName="myjdbcjndi"
   PoolName="MyJDBC Connection Pool"
   Targets="myserver"
/>
<JDBCConnectionPool
   Name="MyJDBC Connection Pool"
   Targets="myserver"
    URL="jdbc:odbc:test"
    DriverName="sun.jdbc.odbc.JdbcOdbcDriver"
    InitialCapacity="1"
    MaxCapacity="10"
/>When i tried to deploy, it showed me errors-
weblogic.management.ApplicationException: activate failed forcmp
Start server side stack trace:
weblogic.management.ApplicationException: activate failed forcmp
Module Name: cmp, Error: Exception activating module: EJBModule(cmp,status=PREPARED)
Unable to deploy EJB: CMPSportBean from cmp:
weblogic.ejb20.WLDeploymentException: The DataSource with the JNDI name: myjdbcjndi could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
     at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:138)
     at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:211)
     at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:181)
     at weblogic.ejb20.manager.DBManager.setup(DBManager.java:162)
     at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:945)
     at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1296)
     at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:349)
     at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1592)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1029)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1016)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1112)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:732)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
TargetException:
Unable to deploy EJB: CMPSportBean from cmp:
weblogic.ejb20.WLDeploymentException: The DataSource with the JNDI name: myjdbcjndi could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
     at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:138)
     at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:211)
     at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:181)
     at weblogic.ejb20.manager.DBManager.setup(DBManager.java:162)
     at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:945)
     at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1296)
     at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:349)
     at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1592)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1029)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1016)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1112)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:732)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1035)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1016)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1112)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:732)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
End server side stack trace
Module Name: cmp, Error: Exception activating module: EJBModule(cmp,status=PREPARED)
Unable to deploy EJB: CMPSportBean from cmp:
weblogic.ejb20.WLDeploymentException: The DataSource with the JNDI name: myjdbcjndi could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
     at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:138)
     at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:211)
     at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:181)
     at weblogic.ejb20.manager.DBManager.setup(DBManager.java:162)
     at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:945)
     at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1296)
     at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:349)
     at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1592)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1029)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1016)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1112)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:732)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
TargetException:
Unable to deploy EJB: CMPSportBean from cmp:
weblogic.ejb20.WLDeploymentException: The DataSource with the JNDI name: myjdbcjndi could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
Start server side stack trace:
weblogic.ejb20.WLDeploymentException: The DataSource with the JNDI name: myjdbcjndi could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
     at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:138)
     at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:211)
     at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:181)
     at weblogic.ejb20.manager.DBManager.setup(DBManager.java:162)
     at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:945)
     at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1296)
     at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:349)
     at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1592)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1029)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1016)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1112)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:732)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
End server side stack trace
     <<no stack trace available>>
     <<no stack trace available>>
I tried to put the file into the directory structure.
I kept the class files into the WEB-INF/classess
I could'nt understand whats wrong with it.
Please help me it is urgent, if i could understand it i can proceed further

Hi,
I had the same error as you. I'm agree with arvind_India (previous). You must :
1. Define a correct Connection Pool (warning: deploy it on your managed server).
2. Test your connection Pool on your managed server.
3. Create a DataSource from your connection Pool.
4. Deploy your DataSource on your managed server.
5. Verify the JNDI TREE of your managed server (Now, the JNDI name of your dataSource must appair).
6. Deploy your Entity Bean (the error has disapeared).
David (Paris-France).

Changing Weblogic Server properties without restarting Weblogic Server

I have an application that requires a few things to be set at the start of the
Weblogic server (email addresses,criteria settings, etc.). These are contained
in a properties file that is referenced in the Weblogic properties file. The
problem is when I want to make a change in the application property file (change
an email address, increment a criteria) I have to "reboot" the Weblogic server.
These defeats the whole purpose of property files. Is there anyway to get Weblogic
to "recache" the properties files without a Weblogic server "reboot"?
Thanks,
Bryan

I very much doubt that you would be able to refresh the WebLogic properties
file at run-time (is this WebLogic 5.1 or 6.0 you are talking a about?).
If you want to be able to update properties run-time (as opposed to
boot-time) then don't use WebLogic's property file - use either your own
properties file or store the properties elsewhere such as in the database or
in JNDI. You will of course have to implement your own refresh algorithm.
If you are using EJBs then a simple READ-ONLY entity bean with a refresh
period of a few seconds may suffice.
Myles
"Bryan Freed" <[email protected]> wrote in message
news:3b1e5986$[email protected]..
>
I have an application that requires a few things to be set at the start ofthe
Weblogic server (email addresses,criteria settings, etc.). These arecontained
in a properties file that is referenced in the Weblogic properties file.The
problem is when I want to make a change in the application property file(change
an email address, increment a criteria) I have to "reboot" the Weblogicserver.
These defeats the whole purpose of property files. Is there anyway toget Weblogic
to "recache" the properties files without a Weblogic server "reboot"?
Thanks,
Bryan

Servlet configuration in Weblogic 5.1.. web.xml vs weblogic.properties..

Can someone please tell me how the <servlet> entry differs from
          weblogic.httpd.register.snoop=examples.servlets.SnoopServlet
          in weblogic properties?
          Do these perform identical functions?


Yes this is the source of my confusiong. It seems to be that WL can be told
          about servlets
          two ways. Firstly through the web.xml file and also via weblogic.properties.
          I don't understand
          why the second one exists.
          "Cameron Purdy" <[email protected]> wrote in message
          news:[email protected]...
          > I only work with WAR files, so I cannot speak to non-WARd servlets with
          any
          > confidence. I know that WL could use web.xml for non-WARd servlets in
          order
          > to obtain the other information associated with the servlet:
          >
          > <!ELEMENT servlet (icon?, servlet-name, display-name?, description?,
          > (servlet-class|jsp-file), init-param*, load-on-startup?,
          > security-role-ref*)>
          >
          > --
          >
          > Cameron Purdy
          > http://www.tangosol.com
          >
          >
          > "Robert Nicholson" <[email protected]> wrote in message
          > news:[email protected]...
          > > If what you say is true then why is there the need to also tell WL about
          > the
          > > servlets themselves?
          > >
          > > Presumably this is for when the servlets exist outside of a WAR then?
          > >
          > > "Cameron Purdy" <[email protected]> wrote in message
          > > news:[email protected]...
          > > > The weblogic.properties tells WL to load a WAR or specific servlet.
          The
          > > > <servlet> entry (I assume you refer to
          > > > http://java.sun.com/j2ee/dtds/web-app_2_2.dtd) defines the presence of
          a
          > > > servlet within a WAR (a deployment unit):
          > > >
          > > > >
          > > > The servlet element contains the declarative data of a
          > > > servlet. If a jsp-file is specified and the load-on-startup element is
          > > > present, then the JSP should be precompiled and loaded.
          > > > [end-quote]
          > > >
          > > > In the case of a WAR deployment, you have to tell WL that the WAR
          > exists,
          > > > then it will look in the WAR and figure out what servlets are there
          from
          > > the
          > > > <servlet> tags in your web.xml. You set up a WAR in the
          > > weblogic.properties
          > > > as such:
          > > >
          > > > weblogic.httpd.webApp.<http-path>=<os-path>
          > > >
          > > > For example:
          > > > weblogic.httpd.webApp.website=c:/weblogic/website.war
          > > >
          > > > --
          > > >
          > > > Cameron Purdy
          > > > http://www.tangosol.com
          > > >
          > > >
          > > > "Robert Nicholson" <[email protected]> wrote in message
          > > > news:[email protected]...
          > > > > Can someone please tell me how the <servlet> entry differs from
          > > > >
          > > > > weblogic.httpd.register.snoop=examples.servlets.SnoopServlet
          > > > >
          > > > > in weblogic properties?
          > > > >
          > > > > Do these perform identical functions?
          > > > >
          > > > >
          > > >
          > > >
          > >
          > >
          >
          >

Clustering weblogic.properties

Hello All. Can anyone give me an idea as to all properties that exist
          for weblogic.clustering. For eg the documentation just has the following
          to be set in the cluster wide weblogic.properties file.
          weblogic.httpd.clustering.enable=true
          weblogic.httpd.session.persistence=true
          weblogic.httpd.session.persistentStoreType=replicated
          weblogic.cluster.name
          weblogic.cluster.multicastPort
          What abt the other properties that were added with the service packs
          like
          the one used to control the buffer for the messages used for broadcast
          on MultiCastIP and other properties related to clustering.
          Any help will be greatly appreciated.
          Thanks.
          Srivats


Hello All. Can anyone give me an idea as to all properties that exist
          for weblogic.clustering. For eg the documentation just has the following
          to be set in the cluster wide weblogic.properties file.
          weblogic.httpd.clustering.enable=true
          weblogic.httpd.session.persistence=true
          weblogic.httpd.session.persistentStoreType=replicated
          weblogic.cluster.name
          weblogic.cluster.multicastPort
          What abt the other properties that were added with the service packs
          like
          the one used to control the buffer for the messages used for broadcast
          on MultiCastIP and other properties related to clustering.
          Any help will be greatly appreciated.
          Thanks.
          Srivats

Weblogic patch for the "Authentication for user wlsadmin denied" issue

Hi Everyone,
When I try to login to the weblogic console using the weblogic user id and password, I got below issue in the production server..Sometime back I saw a thread that Oracle has provided a patch for this issue. If any of you is aware of it then could you please provide us the patch file and its location please. This is quite a bit urgent. Awaiting for your response. Thanks in advance.
<Apr 3, 2011 10:41:02 PM ICT> <Critical> <Security> <BEA-090403> <Authentication for user wlsadmin denied>
<Apr 3, 2011 10:41:02 PM ICT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user wlsadmin denied
I need to communicate to onsite members about the patch details etc.
Edited by: user11290902 on May 13, 2011 1:27 AM

Faisal, Thank you for your response. Here the weblogic console id & password are known to few people so the guess you are making might be correct. Could anyone might have tried with incorrect credentials couple of times before we face this issue, I am not sure though. The moment we provide the credentials and upon click on Log In button we are getting j_security_check.
http://asdo0002:9683/console/j_security_check
Authentication Denied.
The username or password has been refused by WebLogic Server. Please try again.
Any information about the work--arounds or patches from weblogic would be helpful to me... Thanks a lot.

To check the weblogic edition.

Hi,
Could anyone pls help me to find out the weblogic edition (stardard / enterprise / express). tried with java weblogic.version with verbose, displays the patch and verion,. no clue.
BEA\weblogic92\server\bin>java weblogic.version -verbose
WebLogic Server Temporary Patch for 8065523 Wed Oct 14 15:00:06 IST 2009
WebLogic Temporary Patch for CR303287 Thu Feb 8 17:55:36 2007
WebLogic Server 9.2 MP1 Sun Jan 7 00:56:31 EST 2007 883308
Thanks
Kishore.

Hi all,
Even I Couldn't get any information about the weblogic edition we are using. We are always bothered about the version while installing weblogic and which can be found through various commands.
But I want to know which edition we use as there are different types of editions mentioned for weblogic even in the WEBLOGIC SITE.
Can anyone please help with this query,
Regards,
Rahul.

Add properties to the Resource Statistics Report (Parameters)

Hello everyone!
I need to generate some reports based on predefined properties I created to classified the documents.
For example, I want to know how many documents were classified to the property Brazil, or to the property Germany...
There are some properties already defined on the Resource Statistics Report (Parameter), like create by, modified by... I wanted to know if there is any way to add my properties to the list.
thanks,
Luisa

Hi Luisa,
You can develop your own report, you can read about that in this link:
Implementing Customer Reports Using the KM Reporting API
This tutorial describes the implementation of customer reports using the Reporting API of KM
Sample for implementing the reporting API.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6b30b090-0201-0010-829d-e988d093ac65
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/kmc/implementing customer reports using the km reporting api.article
Patricio.

How to deal with security when migrating application from weblogic 5.1 to weblogic 6.1?

Dear All,
I have one statement int weblogic 5.1 weblogic.propertis as follow,
weblogic.security.realmClass=com.tbcn.security.realm.TestRealm
but after converting to weblogic 6.1 there are no corresponding statement in
the file config.xml. And when i start the new application, error occured.
what should I do?
The error message is:
<2001/8/27 am 11:33:42> <Notice> <Management> <Loading configuration file
.\config\tbcn\config.xml
<2001/8/27 am 11:33:49> <Emergency> <Server> <Unable to initialize the
server: 'Fatal initializatio
Throwable: java.lang.NullPointerException
java.lang.NullPointerException
at
weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
at
weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.NullPointerException
java.lang.NullPointerException
at
weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
at
weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception

Dear Satya,
My weblogic propertis file as follow,
# CORE PROPERTIES
# You should set these before you start the WebLogic Server the first time.
# If you need more instructions on individual properties in this
# section, check the same section in the Optional Properties, where
# we've left the long explanations. Or, better yet, go to our
# website and read all about properties, at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# CORE SYSTEM PROPERTIES
# TCP/IP port number at which the WebLogic Server listens for connections
weblogic.system.listenPort=7001
# CORE SECURITY-RELATED PROPERTIES
# Read important information about security at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# REQUIRED: The system password MUST be set in order to start the
# WebLogic Server. This password is case-sensitive, at least 8 characters.
# The username for the privileged user is ALWAYS "system".
# This username and password also includes httpd access (see
# HTTPD properties below).
weblogic.password.system=12345678
# RECOMMEND Set to 'everyone' if HTTPD is enabled
weblogic.allow.execute.weblogic.servlet=everyone
# Set individual ACLs to restrict access to HTTP-related resources,
# such as the Administration servlets.
# To make your own servlets generally available, follow this
# pattern (provide a weblogic.allow.execute) for your packages and
# set ACLs as appropriate.
# CORE SECURITY-RELATED PROPERTIES FOR SSL
# Read important information about SSL at:
# http://www.weblogic.com/docs51/classdocs/API_secure.html
# Enable SSL
# (default if property not defined is false)
weblogic.security.ssl.enable=true
# SSL listen port
weblogic.system.SSLListenPort=7002
# Servlets for SSL
# Authentication servlet for creating tokens for applets
weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationS
ervlet
# Limits number of unclaimed stored tokens
weblogic.security.certificateCacheSize=3
# Capture CA root of client servlet
weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
# Certificates for SSL
# Name of acceptable CA roots
# For client authentication change value to a valid .pem file
#weblogic.security.clientRootCA=SecureServerCA.pem
# Server certificates for SSL
weblogic.security.certificate.server=democert.pem
weblogic.security.key.server=demokey.pem
weblogic.security.certificate.authority=ca.pem
# registration for certificate generator servlet
weblogic.httpd.register.Certificate=utils.certificate
weblogic.allow.execute.weblogic.servlet.Certificate=system
# CORE HTTPD ADMINISTRATIVE PROPERTIES
# True permits the HTTPD to run (default)
# Uncomment this property to disable HTTPD
#weblogic.httpd.enable=false
# If authentication is required, add username/password for each user
# who will be included in an ACL, as in this commented-out example:
#weblogic.password.peter=#8gjsL4*
# SYSTEM PROPERTIES
# System properties in this section are set to system defaults
# Performance pack. The shared library must be accessible from your
# PATH (NT) or from your shared library path (UNIX; the name of the
# variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
weblogic.system.nativeIO.enable=true
# Outputs logging information to the console as well as to the log file
weblogic.system.enableConsole=true
# Sets the directory or URL for the WebLogic Admin help pages
# The help pages are shipped in the "docs/adminhelp" directory, in the
# default document root in public_html
weblogic.system.helpPageURL=/weblogic/myserver/public_html/docs51/adminhelp/
# If you prefer to access the most recent help pages, you can do so online
# by commenting out the previous property and uncommenting this one:
#weblogic.system.helpPageURL=http://www.weblogic.com/docs51/adminhelp/
# Properties for tuning the server's performance
# Number of WebLogic Server execute threads.
weblogic.system.executeThreadCount=15
# Other optional system properties
# Limits size of weblogic.log (in K) and versions old log
weblogic.system.maxLogFileSize=1024
# Adjust minimum length of password
weblogic.system.minPasswordLen=8
# UNIX only: If running on port 80 on UNIX, enable the setUID program
#weblogic.system.enableSetUID=false
# UNIX only: Unprivileged user to setUID to after starting up
# WebLogic Server on port 80
#weblogic.system.nonPrivUser=nobody
# CLUSTER-SPECIFIC PROPERTIES
# Cluster-specific properties in this section are set to system defaults.
# CLUSTER USERS: Note that ALL Cluster-specific properties should be set
# in the per-cluster properties file ONLY.
# Time-to-live (number of hops) for the cluster's multicast messages
# (default 1, range 1-255).
#weblogic.cluster.multicastTTL=1
# Sets the load-balancing algorithm to be used between
# replicated services if none is specified. If not specified,
# round-robin is used.
#weblogic.cluster.defaultLoadAlgorithm=round-robin
# SERVER-SPECIFIC CLUSTER PROPERTIES
# Cluster-related properties in this section are set to system defaults.
# CLUSTER USERS: Note that these server-specific cluster-related properties
# should be set in the per-server properties file ONLY.
# Sets the weight of the individual server for the weight-based
load-balancing.
# Range is 0 - 100.
# Larger numbers increase the amount of traffic routed to this server.
#weblogic.system.weight=100
# SYSTEM STARTUP FILES - Examples
# CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
# objects should be registered in the per-server properties file.
# All other startup classes should be registered in the per-cluster
# properties file.
# For more info on writing and using startup file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs51/classdocs/API_t3.html
# Register a startup class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.startupClass.[virtual_name]=[full_pathname]
# Add arguments for the startup class
#weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
# This example shows the entry for examples/t3client/StartupQuery.java
#weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
#weblogic.system.startupArgs.doquery=\
# query=select * from emp,\
# db=jdbc:weblogic:pool:demoPool
# SYSTEM SHUTDOWN FILES - Examples
# For more info on writing and using shutdown file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs51/classdocs/API_t3.html
# Register a shutdown class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
# Add arguments for the shutdown class
#weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
# This example shows the entry for examples/t3client/ShutdownTest.java
#weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
#weblogic.system.shutdownArgs.ShutdownTest=\
# outfile=c:/temp/shutdown.log
# SECURITY-RELATED PROPERTIES FOR WORKSPACES
# For backward compatibility, the following entries disable Access
# Control on Workspaces
weblogic.allow.read.weblogic.workspace=everyone
weblogic.allow.write.weblogic.workspace=everyone
# JOLT FOR WEBLOGIC PROPERTIES
# These properties configure a BEA Jolt connection pool for use with
# the simpapp and bankapp examples, and register a servlet for use with
# with the simpapp example. The default server address provided here
# points to a public TUXEDO server that is hosted by BEA for use with
# this example.
# Servlet registration for simpapp example:
#weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServle
t
# Pool creation and cleanup
# note this example is set up to work with the public
# demo TUXEDO server available from BEA's website:
#weblogic.system.startupClass.demojoltpoolStart=\
# bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
#weblogic.system.startupArgs.demojoltpoolStart=\
# poolname=demojoltpool,\
# appaddrlist=//beademo1.beasys.com:8000,\
# failoverlist=//beademo1.beasys.com:8000,\
# minpoolsize=1,\
# maxpoolsize=3
#weblogic.system.shutdownClass.demojoltpoolStop=\
# bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
#weblogic.system.shutdownArgs.demojoltpoolStop=\
# poolname=demojoltpool
# WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
# The registrations enable a BEA IIOP connection pool and
# register servlets for use with the simpapp and university examples.
# Configure for your environment and uncomment to use.
# Uncommenting these properties requires WebLogic Enterprise Connectivity
# and an operating WebLogic Enterprise Server.
# Servlet registration for simpapp servlet example
#weblogic.httpd.register.SimpappServlet=\
# examples.wlec.servlets.simpapp.SimpappServlet
#weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
# Servlet registration for simpapp EJB example
# (You'll need to add the wlec_ejb_simpapp.jar to the
# weblogic.ejb.deploy property in this file.)
#weblogic.httpd.register.ejbSimpappServlet=\
# examples.wlec.ejb.simpapp.ejbSimpappServlet
#weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
# Pool creation and cleanup for the simpapp example
#weblogic.CORBA.connectionPool.simplepool=\
# appaddrlist=//wlehost:2468,\
# failoverlist=//wlehost:2468,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# domainname=simpapp
# Servlet registration for university Servlet example:
#weblogic.httpd.register.UniversityServlet=\
# examples.wlec.servlets.university.UniversityServlet
#weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
# Pool creation and cleanup for the University example:
#weblogic.CORBA.connectionPool.Univpool=\
# appaddrlist=//wlehost:2498,\
# failoverlist=//wlehost:2498,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# apppassword=wlepassword,\
# domainname=university
# WEBLOGIC FILE PROPERTIES
# Maps a volume name to a path, for client file read/write
#weblogic.io.fileSystem.[volumeName]=[fullPathName]
# WEBLOGIC JMS DEMO PROPERTIES
# CLUSTER USERS: Note that ALL JMS deployment should be done in the
# per-cluster properties file ONLY.
# You set up a JDBC connection pool if you want persistent messages
# (including durable subscriptions). To use JMS and EJBs in the same
# transaction, both must use the same JDBC connection pool. Uncomment
# the following property to use the default JDBC connection pool
# 'demo', which is defined in the Demo connection pool section of this file.
#weblogic.jms.connectionPool=demoPool
# The JMS Webshare example demonstrates how the ClientID for a
# durable subscriber is configured in the connection factory:
#weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
#weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
#weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
#weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
# The JMS trader example shows how to use JMS with an EJB. In addition
# to uncommenting the following properties, you must also set up and
# deploy the EJB example examples.ejb.basic.statelessSession.Trader in
# ejb_basic_statelessSession.jar to try out this JMS example:
#weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
#weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
#weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
#weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
# Registers the underlying servlet
#weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
# These properties are used with the ServerReceive JMS example,
# which demonstrates how to establish a JMS message consumer
# in a startup class:
#weblogic.system.startupClass.serverReceive=\
# examples.jms.startup.ServerReceive
#weblogic.system.startupArgs.serverReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
# These properties are used with the PoolReceive JMS example,
# which demonstrates how to establish a pool of JMS message consumers
# in a startup class:
#weblogic.system.startupClass.poolReceive=\
# examples.jms.startup.PoolReceive
#weblogic.system.startupArgs.poolReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
#weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
# WEBLOGIC RMI DEMO PROPERTIES
# CLUSTER USERS: Note that pinned RMI objects should be registered
# in the per-server properties file ONLY. All other RMI startup
# classes should be registered in the per-cluster properties file.
# Remote classes registered at startup after the pattern:
#weblogic.system.startupClass.[virtualName]=[fullPackageName]
# These examples can be compiled to see RMI in action. Uncomment to use:
#weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
#weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
#weblogic.system.startupClass.stock=examples.rmi.stock.StockServer
# WEBLOGIC EJB DEMO PROPERTIES
# CLUSTER USERS: Note that ALL EJB deployment should be done in the
# per-cluster properties file ONLY.
# See WebLogic Demo Connection Pool below for a connection pool
# to use with these examples.
# Deploys EJBeans. Uncomment the appropriate lines below and
# modify DBMS-related info and paths to match your particular installation:
# TBCN EJB PROPERTIES
weblogic.ejb.deploy=\
C:/weblogic/myserver/AccountSB.jar, \
C:/weblogic/myserver/AddressEntryDet.jar, \
C:/weblogic/myserver/AddressEntry.jar, \
C:/weblogic/myserver/Affiliate.jar, \
C:/weblogic/myserver/ContactPerson.jar, \
C:/weblogic/myserver/ContactSB.jar, \
C:/weblogic/myserver/Factory.jar, \
C:/weblogic/myserver/FactorySups.jar, \
c:/weblogic/myserver/LoginUsers.jar, \
c:/weblogic/myserver/Member.jar, \
c:/weblogic/myserver/MemberQuotaUsage.jar,\
c:/weblogic/myserver/MemberToCategory.jar,\
c:/weblogic/myserver/Organization.jar, \
c:/weblogic/myserver/Person.jar, \
c:/weblogic/myserver/QuotaType.jar,\
c:/weblogic/myserver/Registration.jar, \
c:/weblogic/myserver/TempAccounts.jar, \
c:/weblogic/myserver/TempDomain.jar, \
c:/weblogic/myserver/UserAccount.jar, \
c:/weblogic/myserver/UserRole.jar, \
c:/weblogic/myserver/BuyerProducts.jar, \
c:/weblogic/myserver/Catalog.jar, \
c:/weblogic/myserver/Categories.jar, \
c:/weblogic/myserver/CategoryToCategory.jar, \
c:/weblogic/myserver/CountryToCategory.jar, \
c:/weblogic/myserver/InvitedMember.jar, \
c:/weblogic/myserver/ProductOrigin.jar, \
c:/weblogic/myserver/ProductOtherFee.jar,\
c:/weblogic/myserver/ProductSups.jar, \
c:/weblogic/myserver/Products.jar,\
c:/weblogic/myserver/ProductToCategory.jar, \
c:/weblogic/myserver/SecondaryQcEntry.jar, \
c:/weblogic/myserver/CodeClass.jar,\
c:/weblogic/myserver/ConfirmationSB.jar, \
c:/weblogic/myserver/PurchasedPackage.jar,\
c:/weblogic/myserver/RejectReasonCode.jar, \
c:/weblogic/myserver/ServiceOrder.jar,\
c:/weblogic/myserver/ServiceOrderLog.jar,\
c:/weblogic/myserver/ServiceOrderState.jar,\
c:/weblogic/myserver/ServiceOrderType.jar,\
c:/weblogic/myserver/ServicePackageDetails.jar, \
c:/weblogic/myserver/ServicePackage.jar, \
c:/weblogic/myserver/ServicePayment.jar, \
c:/weblogic/myserver/ServiceReqSB.jar, \
c:/weblogic/myserver/TAM.jar, \
c:/weblogic/myserver/SubscriptionEB.jar, \
c:/weblogic/myserver/PostingCategoryEB.jar, \
c:/weblogic/myserver/PostingBrowsedEB.jar, \
c:/weblogic/myserver/PostingInfoEB.jar, \
c:/weblogic/myserver/TransactionLogEB.jar, \
c:/weblogic/myserver/PostingSB.jar
#weblogic.ejb.deploy=\
# d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
# d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
# d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
# d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
# d:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
# d:/weblogic/myserver/ejb_extensions_readMostly.jar, \
# d:/weblogic/myserver/ejb_subclass.jar, \
# d:/weblogic/myserver/jolt_ejb_bankapp.jar
# Servlet used by the EJB basic beanManaged example
# Uncomment to use:
weblogic.httpd.register.beanManaged=\
examples.ejb.basic.beanManaged.Servlet
# Add a list of users (set the password with
weblogic.password.[username]=XXX)
# to set an ACL for this servlet:
#weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
#weblogic.password.user1=user1Password
#weblogic.password.user2=user2Password
# WEBLOGIC XML DEMO PROPERTIES
# These properties are required to run the XML examples.
# Uncomment to use.
# CLUSTER USERS: Note that ALL servlets should be set up
# in the per-cluster properties file ONLY.
#weblogic.httpd.register.StockServlet=examples.xml.http.StockServlet
# BizTalk example properties
#weblogic.jms.queue.tradeIncoming=biztalk.jms.tradeIncoming
#weblogic.jms.queue.tradeError=biztalk.jms.tradeError
#weblogic.httpd.register.BizTalkServer=examples.xml.biztalk.BizHttpProtocolA
dapter
#weblogic.httpd.initArgs.BizTalkServer=bizQueue=biztalk.jms.tradeIncoming
# WEBLOGIC ZAC DEMO PROPERTIES
# These registrations enable the ZAC Publish Wizard.
weblogic.zac.enable=true
# Set the publish root for a WebLogic Server. Edit and
# uncomment to use.
#weblogic.zac.publishRoot=d:/weblogic/zac
# Set an ACL for each package you publish. The [name] is
# the "Package name" you assign in the ZAC Publish Wizard.
# Publish a package, edit this property, and uncomment to use.
#weblogic.allow.read.weblogic.zac.[name]=[user list]
#weblogic.allow.write.weblogic.zac.[name]=system
# HTTPD ADMINISTRATIVE PROPERTIES
# Enables logging of HTTPD info in common log format and
# sets the log file name (default is "access.log" in "myserver")
weblogic.httpd.enableLogFile=true
weblogic.httpd.logFileName=access.log
# Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
weblogic.httpd.enableEvents=false
# Enables HTTP sessions
weblogic.httpd.session.enable=true
# Sets an optional cookie name. The default name is "WebLogicSession".
# Prior to version 4.0, the default was "TengahSession". To make
# this backward compatible with cookies generated from previous
# installations, you should set this property to "TengahSession".
# Uncomment this line and set this to any string of your choice,
# or comment out this property to use the default.
#weblogic.httpd.session.cookie.name=WebLogicSession
# MIME types
weblogic.httpd.mimeType.text/html=html,htm
weblogic.httpd.mimeType.image/gif=gif
weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
weblogic.httpd.mimeType.application/pdf=pdf
weblogic.httpd.mimeType.application/zip=zip
weblogic.httpd.mimeType.application/x-java-vm=class
weblogic.httpd.mimeType.application/x-java-archive=jar
weblogic.httpd.mimeType.application/x-java-serialized-object=ser
weblogic.httpd.mimeType.application/octet-stream=exe
weblogic.httpd.mimeType.text/vnd.wap.wml=wml
weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
# In seconds, the keep-alive for HTTP and HTTPS requests
weblogic.httpd.http.keepAliveSecs=60
weblogic.httpd.https.keepAliveSecs=120
# WEBLOGIC JDBC DRIVER PROPERTIES
# Enables JDBC driver logging and sets the file name for the log
# The weblogic.jdbc.logFile is placed in the per-server
# directory (default is "myserver")
weblogic.jdbc.enableLogFile=false
weblogic.jdbc.logFileName=jdbc.log
# WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
# CLUSTER USERS: Note that ALL JDBC connection pools should be set up
# in the per-cluster properties file ONLY.
# For creating JDBC connection pools. This example shows a connection
# pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
# to use 4 JDBC connections (with a potential for up to 10 connections,
# incremented by two at a time, with a delay of 1 second between each
# attempt to connect to the database), to an Oracle database server called
# "DEMO." If more than 4 connections are opened, after 15 minutes, unused
# connections are dropped from the pool until only 4 connections remain
open.
# Every 10 minutes, any unused connections in the pool are tested and
# refreshed if they are not viable.
#weblogic.jdbc.connectionPool.oraclePool=\
# url=jdbc:weblogic:oracle,\
# driver=weblogic.jdbc.oci.Driver,\
# loginDelaySecs=1,\
# initialCapacity=4,\
# maxCapacity=10,\
# capacityIncrement=2,\
# allowShrinking=true,\
# shrinkPeriodMins=15,\
# refreshMinutes=10,\
# testTable=dual,\
# props=user=SCOTT;password=tiger;server=DEMO
# Get more details on each argument for this property in the
# Administrators Guide on setting properties at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# Set up ACLs for this connection pool with the following:
weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
# guest,joe,jill
#weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
#weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
# This property is an ACL that specifies the users who can
# create dynamic connection pools:
#weblogic.jdbc.connectionPoolcreate.admin=joe,jill
# Read more about setting up and using connection pools in the
# developers guide for WebLogic JDBC at:
# http://www.weblogic.com/docs51/classdocs/API_jdbct3.html#T5a
# TBCN JDBC CONNECTION POOL MANAGEMENT
weblogic.jdbc.connectionPool.oraclePool=\
url=jdbc:oracle:thin:@202.109.102.151:1521:tbcn,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=2,\
maxCapacity=10,\
capacityIncrement=2,\
allowShrinking=true,\
shrinkPeriodMins=15,\
refreshMinutes=10,\
testTable=dual,\
props=user=tbcn;password=ca91768
weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
weblogic.jdbc.TXDataSource.oracleDataSource=oraclePool
weblogic.jdbc.DataSource.oracleReadOnlyDataSource=oraclePool
# WEBLOGIC DEMO CONNECTION POOL PROPERTIES
# CLUSTER USERS: Note that ALL JDBC connection pools should be set up
# in the per-cluster properties file ONLY.
# This connection pool uses the sample Cloudscape database shipped
# with WebLogic. Used by the EJBean, JHTML, JSP and JMS examples.
# Uncomment to use:
#weblogic.jdbc.connectionPool.demoPool=\
# url=jdbc:cloudscape:demo,\
# driver=COM.cloudscape.core.JDBCDriver,\
# initialCapacity=1,\
# maxCapacity=2,\
# capacityIncrement=1,\
# props=user=none;password=none;server=none
# Add a TXDataSource for the connection pool:
#weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.demoPool=demoPool
# Add an ACL for the connection pool:
#weblogic.allow.reserve.weblogic.jdbc.connectionPool.demoPool=everyone
# WEBLOGIC HTTP SERVLET PROPERTIES
# CLUSTER USERS: Note that ALL servlets should be set up
# in the per-cluster properties file ONLY.
# WebLogic offers different types of servlets for various uses.
# Classpath servlet registration
# The ClasspathServlet is used to serve classes from
# the system CLASSPATH. It is used by applets to load
# classes they depend upon, and is registered against
# the virtual name 'classes' here by default. This means
# you should set your applet codebase to "/classes".
# You can register multiple virtual names for this servlet.
# Note that it can also be used to serve other
# resources/files from the system CLASSPATH.
# Don't confuse the ClasspathServlet with the ServletServlet. The
# ClasspathServlet is used for serving classes for client-side Java only.
# The ServletServlet is used to invoke unregistered servlets.
# See the Administrators Guide "Setting up WebLogic as an HTTP server"
# http://www.weblogic.com/docs51/admindocs/http.html#classfile for more
info.
weblogic.httpd.register.classes=weblogic.servlet.ClasspathServlet
# We also set an open ACL for everyone to call the ClasspathServlet
# so that applets work without requiring further changes.
weblogic.allow.execute.weblogic.servlet.classes=everyone
# File servlet registration
# FileServlet searches below the documentRoot for the requested file
# and serves it if found. If the requested file is a directory,
# FileServlet will append the defaultFilename to the requested path
# and serve that file if found.
weblogic.httpd.register.file=weblogic.servlet.FileServlet
weblogic.httpd.initArgs.file=defaultFilename=index.html
weblogic.httpd.indexFiles=zh_TW/index.htm
# ServerSideInclude servlet registration
# SSIServlet searches below the documentRoot for the
# requested .shtml file and serves it if found.
weblogic.httpd.register.*.shtml=weblogic.servlet.ServerSideIncludeServlet
# Example URL: http://localhost:7001/portside/welcome.shtml
# for the file /weblogic/myserver/public_html/portside/welcome.shtml
# PageCompileServlet (used by JHTML)
# See the information below under WebLogic JHTML
# JSPServlet (used by JSP)
# See the information below under WebLogic JSP
# ServletServlet registration
# Allows unregistered servlets in the servlet classpath (see Servlet
# reload properties below) to be r

Show properties in the Search Result window

Hello all,
I would like to add few properties in the Search Result window such that the corresponding values are visible at a glance rather than checking the same in the respective Details wondow.
Example: Ia have created new Properties like ReqNo, ReqDate... and would like them to appear in the Search Result window.
Please help me solve this.
Im also reading the UI topic given in help.sap.com but am unable to find the answer.
Awaiting Reply.
Thanks and Warm Regards,
Ritu

Hi Ritu,
Go to KM Config > Content Management > User Interface > Settings > Layout Set and put "Search" in the filter. You should see "SearchResultLayoutSet" and this is the Layout Set that is used to display Search Results. Within the Collection Renderer there is Displayed Properties, this is what you need to focus on.
There are some other threads and documents associated with your question here on SDN. If you do a search for "SearchResultLayoutSet" in the SDN search you should get enough information to achieve your objective.
Sorry for the brief reply but I have one foot out the door heading for the airport and won't be back online for another couple of days.
Let me know how you go
Paul

How can I get all the settings from weblogic.properties ?

Hi, and excuse me for my poor english.....
I have a T3Client and I want to obtain all the settings from weblogic
properties...
With the sentence getT3Services().config().getProperty("......"), I can
obtain the property, but my problem is that at runtime, I don`t know
established names....
I want to obtain something as the AdminProps servlet, but with a non-web
client.....
Can anybody help me ?

Hi, and excuse me for my poor english.....
I have a T3Client and I want to obtain all the settings from weblogic
properties...
With the sentence getT3Services().config().getProperty("......"), I can
obtain the property, but my problem is that at runtime, I don`t know
established names....
I want to obtain something as the AdminProps servlet, but with a non-web
client.....
Can anybody help me ?

Add weblogic.properties to the weblogic.

Similar Messages

Maybe you are looking for