Weblogic template directory structure.

I was looking at the weblogic portal personalization template and I found that there is a project with a build.xml on it. If i run it manually I don't see the script been invoked but I can see it whenever I use the configuration wizard. How can I trigger the build.xml to be executed when is executed manually from the WLST?

Ricardo,
I've done a lot of VM installations of WebLogic 11g w/ Forms but never used these VM "templates" that you use. I've always installed weblogic and Forms on a freshly installed operating system (Solaris,OEL,Redhat,Windows,etc..).
Please refer to forms installation documentation provided by Oracle: http://download.oracle.com/docs/cd/E14571_01/install.1111/e10421/toc.htm
Secondly, the statement "Oracle weblogic 10gR3" concerns me - what exact version of oracle weblogic server is installed?
You need 11g Forms with 11g Oracle WebLogic Server. The versions are a little confusing but you need one of the following setups:
1.) WebLogic Server 11g (v10.3.2) with Forms 11g (11.1.1.2)
1.) WebLogic Server 11g (v10.3.3) with Forms 11g (11.1.1.3)
2.) WebLogic Server 11g (v10.3.4) with Forms 11g (11.1.1.4) (Just recently released)
Note: Forms 11.1.1.3 and Forms 11.1.1.4 are patchsets.
Thirdly, for system specs. All minimum requirements are noted in the installation guide link i mentioned above. It depends on what environment this is and how many apps, users, etc. etc. However, for development environments i've done: usually 25GB+ HDD space, 4GB RAM, 1 CPU (1.5 Ghz+) has been sufficient.
Hope this helps.
Thanks,
Gavin

Similar Messages

  • Weblogic directory structure with explanation.

    Hi,
    I am looking for weblogic 11 directory structure and their working. Can someone guide me

    Here is my favorite:
    http://www.slideshare.net/mobile/jambay/oracle-weblogic-server-basic-concepts-presentation
    Jon petter

  • Where to put simple html-file in WebLogic directory structure?

    After installing JDeveloper 11g and WebLogic 10.3 which came in the same exe-file (jdevstudio11110install.exe), I want to try WebLogic as a ordinary web server for a simple html-file. Where should the file be placed in WebLogics directory structure, and are there any settings that need to be done to get this to work?

    Thank you, Maxence -
    I made it work this way:
    - Entered the following in weblogic.xml for a simple dummy-servlet...
    (WebLogicServletTest-ProjectWebLogicServletTest-context-root)
    ... deployed to the WebLogic server:
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <weblogic-web-app>
    <virtual-directory-mapping>
    <local-path>C:\WorkScratch\</local-path>
    <url-pattern>*.html</url-pattern>
    </virtual-directory-mapping>
    </weblogic-web-app>
    WebLogic served up the hoppla.html-file in the C:\WorkScratch directory with the following browser URL:
    http://192.168.15.108:8900/WebLogicServletTest-ProjectWebLogicServletTest-context-root/hoppla.html

  • Is there any way to specify a URL in the servlet-mapping that doesn't need to be in the directory structure?

              I migrated from WebLogic 5.1 to 7.0.2 Something I used to have set-up in 5.1 no
              longer
              works.
              I am using the weblogic.servlet.FileServlet and have the URL "/cxedocs/" mapped
              to this
              servlet. So whenever the URL http://localhost:7001/cxedocs/en_US/index.html
              is used it would use the docHome associated with the /cxedocs/ URL and then append
              the "en_US/index.html" on to it. So let's say d:\temp\en_US\index.html
              But now for WL 7.0.2 it appears that the URL also needs to be in the directory
              structure.
              So it now takes the docHome "d:\temp" adds the URL "/cxedocs/" and then appends
              the
              rest - so d:\temp\cxedocs\en_US\index.html.
              I can't require that the "cxedocs" directory be there. Is there anyway to map
              a certain URL
              without requiring it in the directory structure. I looked at virtual directory
              mapping too but
              it still seemed to require this.
              Any help would be appreciated!
              Thanks!
              -Lori
              

              I opened up a case with support on this. After some research they came back with
              that
              NO there is no way to do this. In 6.0 it was changed to follow the spec which
              restricts this.
              The URL must be part of the directory path.
              -Lori
              "Lori Ronning" <[email protected]> wrote:
              >
              >I migrated from WebLogic 5.1 to 7.0.2 Something I used to have set-up
              >in 5.1 no
              >longer
              >works.
              >
              >I am using the weblogic.servlet.FileServlet and have the URL "/cxedocs/"
              >mapped
              >to this
              >servlet. So whenever the URL http://localhost:7001/cxedocs/en_US/index.html
              >is used it would use the docHome associated with the /cxedocs/ URL and
              >then append
              >the "en_US/index.html" on to it. So let's say d:\temp\en_US\index.html
              >
              >But now for WL 7.0.2 it appears that the URL also needs to be in the
              >directory
              >structure.
              >So it now takes the docHome "d:\temp" adds the URL "/cxedocs/" and then
              >appends
              >the
              >rest - so d:\temp\cxedocs\en_US\index.html.
              >
              >I can't require that the "cxedocs" directory be there. Is there anyway
              >to map
              >a certain URL
              >without requiring it in the directory structure. I looked at virtual
              >directory
              >mapping too but
              >it still seemed to require this.
              >Any help would be appreciated!
              >Thanks!
              >-Lori
              

  • Export images to a directory structure based on a collection tree?

    A question:
    Will lightroom have the capability to export images to a directory structure which mirrors a collections logical structure?
    The reason I ask this is that when I create websites using third party tools (eg, Jalbum) I typically generate a flash or HTML based site with an menu structure for navigating the images.
    So, the image interface is not simply a "flat-file" display as per the templates in Lightroom beta.
    To do this, with previous image management tools (eg, iMatch) I create a hierarchy of images based on the categories (or collections) that the images are assigned to, export the images in a folder tree reflecting their categories (or collection), then use, say, Jalbum, to generate the website with the menu tree reflecting the folders/images.
    This is extremely useful for more complicated image websites with categories and a large no of images.
    If this function was built into Lightroom I guess it would be in the export function such that the "write to folder" box could take an argument {collection name} which would create a folder tree reflecting the collections logical tree which is being exported.
    Apologies if this topic has been raised previously. But this function is extremely useful if you are using third party html tools or simply building websites by hand.
    Regards
    Alistair

    I started simmilar thread in Lightroom Feature Requests few months ago, but can't find it anymore since new forum version...
    What I can suggest as a new feature is export to directory structure from collections or second option from keywords. Probably more usable and easier to implement would be from collections.
    What I need it to export many photos to different directories pretty often, and this would be great help since I could arrange them in collections and collection sets. Then select collection set and export it in a manner that collection set would be main export directory, and each collection within the set would be exported to its own folder within main collection set export folder.
    This would be much appreciated feature in near future
    Thank you for great product by the way

  • Directory Structure ?s for an Exploded Web Application

    We have an application that consists only of JSPs and Servlets, no
    EJBs. I am researching whether or not it's worthwhile to start using
    EJBs. We're also migrating from Weblogic 5 to 6.1. I've managed to
    migrate our application fine and have it up and running on WLS 6.1.
    I'm confused about the exploded directory structure, the
    application.xml file, where to put the EJBs and whether or not I have
    to jar them. Here's our current directory structure:
    DefaultWebApp/               JSPs here
    DefaultWebApp/WEB-INF          web.xml and weblogic.xml here
    DefaultWebApp/WEB-INF/classes     Servlets and other classes here
    DefaultWebApp/WEB-INF/lib     do my un-jar-ed EJBs go here?
    I've been reading a lot of BEA's documentation, particularly
    ‘Deploying an Exploded J2EE Application' and a ‘Web Application PDF',
    and looking for relevant threads on the weblogic.developer.interest
    groups. It looks like the application.xml should go in a new
    DefaultWebApp/META-INF directory. But where do the EJBs go?
    I also see some directory structures with another /web directory
    that's confusing me.
    Oh, I've also managed to compile and jar up a trial Stateless Session
    EJB. Then I think I ‘auto-deployed' it into the /applications
    directory, and Weblogic seems to recognize it. But when I tried to
    reference it in a JSP, I got an error message ‘class x is public,
    should be declared in a file named x.java'. I'm assuming this is
    related to the application.xml, where I need to define the ejb
    directory.
    Thanks.

    To deploy your web app together with your EJBs, you need to create
    an "EAR" structure. Both your webapp and your EJB jars will be within
    this new structure, at the same level. You may jar up your EJBs, or you
    may explode their structure, it's up to you.
    The resulting structure should look something like below:
    EnterpriseApp/ <-- new top level
    EnterpriseApp/META-INF/
    EnterpriseApp/META-INF/application.xml
    EnterpriseApp/lib/ <-- shared libraries (if any)
    EnterpriseApp/EJB/ <-- ejbs go here
    EnterpriseApp/EJB/META-INF/ejb-jar.xml
    EnterpriseApp/EJB/META-INF/weblogic-ejb-jar.xml
    EnterpriseApp/EJB/com/your/ejb/classes/here
    EnterpriseApp/WebApp/ <-- move your current app here
    EnterpriseApp/WebApp/index.jsp <-- JSPs goes here
    EnterpriseApp/WebApp/other.jsp
    EnterpriseApp/WebApp/WEB-INF/web.xml
    EnterpriseApp/WebApp/WEB-INF/weblogic.xml
    EnterpriseApp/WebApp/WEB-INF/lib <-- ui libraries go here
    EnterpriseApp/WebApp/WEB-INF/classes <-- servlets go here
    The above structure is identical to the structure to an EAR file, only "exploded"
    as actual files and directories instead of being "jarred" into a single EAR file.
    Your application.xml in this case would specify something like:
    <application>
    <display-name>EnterpriseApp</display-name>
    <description>My Enterprise Application</display-name>
    <module>
    <ejb>EJB</ejb>
    </module>
    <module>
    <web>
    <web-uri>WebApp</web-uri>
    <context-root>/yourAppRoot</context-root>
    </web>
    </module>
    </application>
    And in config.xml you would have an entry similar to:
    <Application Deployed="true" Name="EnterpriseApp"
    Path=".\config\mydomain\applications\EnterpriseApp">
    <WebAppComponent Name="ui" Targets="myserver" URI="WebApp"/>
    <EJBComponent Name="ejb" Targets="myserver" URI="EJB"/>
    </Application>
    regards,
    -Ade

  • Directory structure for the new Data Services Project

    1) I do as prescribed in the manual "Building and deploying
    Flex 2 Applications", page 325
    "To create a web application make a copy of the /flex
    directory and its contents. Rename the copy and store it in the
    same location under /servers/default directory."
    ("flex" is an empty Flex Data Services application that
    serves as a template for creating your custom application)
    2) I create a corresponding project from Flex Builder 2 :
    Project type: Flex Data Services
    Root folder: C:\fds2\jrun4\servers\default\MyDS
    Root URL:
    http://localhost:8700/default/MyDS
    Project name: MyDS
    Project contents: C:\fds2\jrun4\servers\default\MyDS
    2) I build the project
    Immediately after "build project" the directory structure at
    C:\fds2\jrun4\servers\default\MyDS becomes the following:
    .settings
    bin
    ----------------META-INF
    ----------------WEB-INF
    ---------------- --------------- classes
    ---------------- ---------------flex
    --------------------------------jsp
    --------------------------------lib
    -------------------------------sessions
    html-template
    META-INF
    WEB-INF
    ----------------classes
    ----------------flex
    ----------------jsp
    ----------------lib
    ----------------sessions
    Notice that bin directory now contains another pair of
    META-INF and WEB-INF in addition to those already existing in the
    template project "flex".
    Can anybody comment on this directory structure?
    Which META-INF and WEB-INF are supposed to be used for
    configuration?
    What is the purpose of having two pairs of META-INF and
    WEB-INF in the same web app?

    Hello -
    first, those folders are necessary in deployment - You need
    only the contents of the bin folder for deployment, not the
    sources. Since you're compiling the application locally in FB2 it
    places all of the supporting and necessary files into one location
    namely the "bin" folder. You'd deploy the "bin" folder's contents
    to the FDS server, perhaps another FDS server that is not your
    "development" server -- like a production server. The data and
    configuration information that your app needs for FDS services are
    stored in the WEB-INF and META-INF folders so these need to travel
    with the final product. On the production server you'd just cop the
    "bin" folder and it's contents to the /servers/default folder -
    where you could then rename your bin folder to "MyDS"
    HTH, Bill

  • Directory structure and files in Oracle Application server 10g and 11g

    Hi all,
    I am doing a lab migration from 10g to 11g based on the use of JAXB. There were some directory structures used in 10g to store the JAXB jar files and some other custom jar files. I want to know the equivalent folder structures in SOA 11g server. The 10g server directories are mentioned below:-
    1.<OracleAS_Home>\webservices\lib.
    2. server.xml located at <OracleAS_Home>\j2ee\home\config in 10g. Where can I find the equivalent file to "server.xml" in 11g server?
    3. <OracleAS_Home>\bpel\system\classes\com\oracle\bpel\xml\util.
    4. <OracleAS_Home> \bpel\system\classes.

    Here are the equivalents as per best of my knowledge:
    1. <WebLogic Home>\server\lib
    For example, D:\Middleware\wls1036\wlserver_10.3\server\lib
    2. config,xml located at <Domain_Home>\config\
    For example, D:\Middleware\wls1036\user_projects\domains\ArunBaseDomain1036\config\config.xml
    3. It should be the same as 10g (instead of OracleAS_Home, it will be ORACLE_Home) if you install the BPEL product. Since, I have not installed BPEL/SOA, I am not very sure.
    4. It should be the same as 10g (instead of OracleAS_Home, it will be ORACLE_Home) if you installed the BPEL product.
    Also, I would recommend that you consider using ORACLE Smart Upgrade (JDeveloper component) to help you with the upgrade process. It exactly points out these mappings of file/directory structures AND the necessary configuration changes as well.
    If you are requirement, is only about making the library jars available to your application, then consider reading the below discussion.
    Re: XIncludeAwareParserConfiguration cannot be cast to XMLParserConfiguration
    Arun

  • OVM 3.0.1 - directory structure & adding resources

    Afternoon everyone,
    I've got OVM 3.0.1 up and running, so far so good.
    I had a question about the repository directory structure. If this has been addressed already, my apologies.
    In OVM 2.x, it was possible to copy over a variety of data (.iso's, .img's, templates, etc.) directly into the seed, iso and running pools on OVS and then register them through OVM. Is there a way to do this in OVM/OVS 3.0.1? Is it a matter of getting the correct syntax in the 'download location' dialog box that refers to the OVS 3.0.1 box? Or do you need a remote staging resource set up in order to import data?
    Best regards,
    J.

    861743 wrote:
    In OVM 2.x, it was possible to copy over a variety of data (.iso's, .img's, templates, etc.) directly into the seed, iso and running pools on OVS and then register them through OVM. Is there a way to do this in OVM/OVS 3.0.1? Is it a matter of getting the correct syntax in the 'download location' dialog box that refers to the OVS 3.0.1 box? Or do you need a remote staging resource set up in order to import data?You need a remote server to import data. This can be the Oracle VM Manager machine itself, as long as you can access it via http/https from the Oracle VM Servers (as the import happens on the Oracle VM Server machines). Just install Apache on your VM Manager machine and stash your templates/assemblies in /var/www/html.

  • What is the directory structure of EJB applications?

    I am new to EJB program. I know that after the development is done, we package the EJB components into .jar file, and package the Web components (HTML/JSP/Servlets/JavaBeans) into .war file, and then together we package .jar file and .war file into a single .ear file. Then we just deploy the .ear file into WebLogic's application directory.
    But, before the deployment, I mean during the development, what kind of directory structure is good for us to develop our EJB, HTML, JSP, Servlets, and JavaBean components?
    Previously, when I was doing JSP/Servlets applications, my directoy structure is:
    webapps\
    --------myapplication\
    -----------------------*.html
    -----------------------images\
    ------------------------------*.jpeg, *.gif
    -----------------------jsp\
    ------------------------------*.jsp
    -----------------------WEB-INF\
    ------------------------------web.xml
    ------------------------------classes\
    -------------------------------------Java Servlets located here
    -------------------------------------beans\
    -------------------------------------------JavaBeans are located here
    Now, I am doing EJB applications, what should be the directory structure?
    Thank you very much for your help!
    Jingzhi

    I have been involved in a few enterprise applications but have not been happy with the packaging structures used and am starting a new one now and am looking for other examples.
    this is what I've used before.
    web/
    classes/
    client/
    server/
    but if a class was used in the client and server it was put under the server/ package. I feel that more separation is needed.

  • An EFFECTIVE development directory structure for J2EE platform?

    Hi, here we r talking about deployment environment more than development
    environment. Have u ever think about designing an EFFECTIVE development
    directory structure for J2EE platform( e.g. weblogic )? u r not using the
    deployment directories for coding, r u? :)
    I used to construct a dir structure for dev and want to improve it.
    d:/wholesystem/*.prj // Project files
    ...../module1/src/com/.... // Module source files
    ...../module1/doc/... // Module doc files
    ...../module1/classes/... // Module class files
    ...../module2/...
    ...../web/*.jsp // web page files
    ...../web/images/... // web page images
    ...../web/WEB-INF/... //...
    Do u have any good ideas? Thanks!
    * Name: Gary Wang
    * Tele: 010-65546668-8119
    * Mail: [email protected]

    Create a web-inf folder at the same level of src and
    jsp folder inside src
    i mean
    /build.xml
    /src/
    /src/java/<package>/...../*.java
    /src/demo/<package/...../*.java
    /src/test/<package>/....../*.java
    /src/jsp
    /web-infSo, would you put in /src/jsp only the *.jsp?
    And what in /WEB-INF ? What woud you put there? Would you do something like:
    /WEB-INF/web.xml
    /WEB-INF/src/<package>/..../<my_servlets_and_j2ee_stuff>.java
    /WEB-INF/classes/<package>/..../<my_servlets_and_j2ee_stuff>.java
    In this manner sources and classes are in the same tree, it does not seem very clean to me, expecially if you consider that probably I must have a "test" directory to unit test some j2ee stuff (as for the j2se stuff in "src"): how would you do that?
    Is this directory structure anyway what you meant or not?
    alessio

  • Directory Structure Problem

    Hi i am niew to EJB
    my directory structure is like this
    App
    -----JSP,s
    -----WEB-INF
    --------classes
    -------package name
    -----------servlet class file
    -----PAckage Name
    -----------Sesion Bean Class File
    my servlet is calling the session bean but when i open this app in weblogic builder it only shows jsp/servlet related setting
    what is the correct directory structure
    jsp is calling a servlet which in turn calles a session bean
    kindly tell me
    Puneet

    I don't know why but weblogic builder sometimes behaves weird. Anyway, my suggestion is to try out to edit your application.xml manually.
    good luck,
    Fehmi

  • Ant Directory structure.

    Hi,
    We are developing J2EE application that would contain number of components. Each component would be a ear file that would contain EJB jars and war which can be deployed in any J2EE compliant application server.
    We are currently using Bedrock framework for applications deployed in Weblogic. It provides a very robust directory structure with most of the ant targets. However it is very custom for Weblogic.
    Is there a similar framework that provides a robust directory structure (with built ant targets) which can be delopyed into Orion/Oracle Application Server.
    If not, is there any standard directory structure for building J2EE applications? Any recommended source directory structure and why?
    Any help is greatly appreciated.
    Thanks
    Sumanth

    ATProject
    |
    |-->Business
    |
    |-->Common
    |
    |-->Ear
    |
    |-->Ejb
    |
    |---- . so on
    like this the folderers are created for modularizing and also separation of code for
    easier maintainance.
    the Build.xml for ant i am posting here
    <?xml version="1.0" encoding="UTF-8"?>
    <project name="MainDeploy" default="development_build">
         <target name="development_build">
              <antcall target="ear">
                   <param name="directive" value="development"/>
              </antcall>
         </target>
         <target name="integration_build">
              <antcall target="ear">
                   <param name="directive" value="development"/>
              </antcall>
         </target>
         <target name="qa_build">
              <antcall target="ear">
                   <param name="directive" value="qa"/>
              </antcall>
         </target>
         <target name="production_build">
              <antcall target="ear">
                   <param name="directive" value="production"/>
              </antcall>
         </target>
    <!-- ################################ Build Calls ################################# -->
    <!-- ********************** Build the ats_ear.ear ******************** -->          
         <target name="ear" depends="web">
              <echo>Entering the EAR process</echo>
              <ant antfile="ear.xml" target="${directive}"/>
         </target>
    <!-- ********************* Build the ats.war ******************* -->          
         <target name="web" depends="business">
              <echo>Entering the Web process</echo>
              <ant antfile="web.xml" target="${directive}"/>
         </target>
    <!-- ********************* Build the ats_business.jar ******************* -->     
         <target name="business" depends="ats_ejb">
              <echo>Entering the Business process</echo>
              <ant antfile="business.xml" target="${directive}"/>
         </target>
    <!-- ********************** Build the ats_ejb.jar ******************** -->     
         <target name="ats_ejb" depends="integration">
              <echo>Entering the Prototype EJB process</echo>
              <ant antfile="ejb.xml" target="${directive}"/>
         </target>
    <!-- ******************** Build the prototype_integration.jar ************** -->
         <target name="integration" depends="common">
              <echo>Entering the Integration process</echo>
              <ant antfile="integration.xml" target="${directive}" />
         </target>     
    <!-- ********************** Build the ats_common.jar ******************** -->     
         <target name="common" depends="vo">
              <echo>Entering the Common process</echo>
         <ant antfile="common.xml" target="${directive}"/>
         </target>
    <!-- ********************** Build the ats_vo.jar ******************** -->          
         <target name="vo">
              <echo>Entering the VO process</echo>
              <ant antfile="vo.xml" target="${directive}"/>
         </target>
    </project>
    /// End of Build.xml
    Start of modular xml.. for examlpe Business.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <project name="business" default="development">
         <!-- set global properties -->
         <property file="global.properties"/>
         <path id="library.path">
              <fileset dir="${localdir}/lib">
                   <include name="**/*.jar"/>
                   <include name="**/*.zip"/>
              </fileset>
         </path>
         <property name="build" location="${localdir}/business/build"/>
         <!-- set properties based on build type -->
         <target name="development">
              <antcall target="create_jar"/>
         </target>
         <target name="integration">
              <antcall target="create_jar"/>
         </target>
         <target name="qa">
              <echo>Creating the business archive for qa</echo>
              <param name="promo" value="qa"/>
              <antcall target="create_jar"/>
         </target>
         <target name="production">
              <echo>Creating the business archive for production</echo>
              <param name="promo" value="production"/>
              <antcall target="create_jar"/>
         </target>
         <!-- Run during every execution -->
         <target name="copy_files">
         <mkdir dir="${localdir}/business/build"/>
         <copy overwrite="yes" todir="${build}">
         <fileset dir="${localdir}/business/src">
              <exclude name="**/*.java"/>
              <exclude name="**/*.class"/>
              <exclude name="**/*.jpx"/>
              <exclude name="**/*.dep2"/>
         </fileset>
         </copy>
         </target>
         <!-- Compile the java source into the deploy directory with optimization -->
         <target name="compile_source" depends="copy_files">
              <echo>Compiling source</echo>
              <javac srcdir="${localdir}/business/src" destdir="${build}" >
                   <classpath refid="library.path"/>
              </javac>
         </target>
         <!-- Create the JAR file to be deployed -->
         <target name="create_jar" depends="compile_source">
              <echo>Creating JAR file from compiled source</echo>
              <jar jarfile="${localdir}/lib/ats_business.jar"
                   basedir="${build}"/>
         </target>
    </project>
    Hope you could get me
    Alll The BEst

  • Directory Structures

    Hi,
    This is about the directory structures to use for development and
    deployment under weblogic. By default, as you all know, weblogic comes with
    a server called "myserver" whose directory strcuture has within it the
    public_html, serverclasses, servletclasses and clientclasses directories,
    with the jar files for the examples all residing in the myserver directory.
    The general tendency for developers is to use simply use that very structure
    as is. I think that may prove to be unwieldy during deployment (especially
    when there will be multiple servers running on multiple machines, etc.) as
    well as during development (integrating with source code control, etc.)
    Here are my questions:
    1) How have people weblogic developers organized their directory structures
    for deployment? It seems to me that it would make sense to have a directory
    structure that has at least a "lib" directory under which the jar files were
    put, a "log" directory for log files, a "cert" directory for certificates,
    etc.
    2) In addition, is there an absloute need for the myserver directory to sit
    under the weblogic tree? I would think it would make sense to not have the
    deployment directory structures not tied to the weblogic installation's
    location.
    3) If there are multiple servers that will be deployed (each instantiating
    its own set of services that are implemented as session and entity EJBs),
    does one introduce an entire directory structure for each server or have a
    common directory structure with each server having its own properties file ?
    Currently, I have it setup so that each server that is introduced, e.g.,
    pricing servers, fulfillment servers, etc. has its own properties file and
    that the entire directory tree sits separate from the weblogic installation,
    to facilitate tight integration with source code control. Having resolved
    the regular issues that arise with the CLASSPATH, ClassCastExceptions, etc.,
    we're up and running, but I have had a tough time convincing my developers
    about the merits of deviating from the standard development tree stcucture.
    Do people have any opinions about this, and are there any experiences they
    can share with me? I'd be more than willing to to change course based on
    others' experiences.
    Sorry for the long-winded message.
    TIA,
    Prashanth

    Prashanth Nandavanam wrote:
    >
    Hi,
    This is about the directory structures to use for development and
    deployment under weblogic. By default, as you all know, weblogic comes with
    a server called "myserver" whose directory strcuture has within it the
    public_html, serverclasses, servletclasses and clientclasses directories,
    with the jar files for the examples all residing in the myserver directory.
    The general tendency for developers is to use simply use that very structure
    as is. I think that may prove to be unwieldy during deployment (especially
    when there will be multiple servers running on multiple machines, etc.) as
    well as during development (integrating with source code control, etc.)
    Here are my questions:
    1) How have people weblogic developers organized their directory structures
    for deployment? It seems to me that it would make sense to have a directory
    structure that has at least a "lib" directory under which the jar files were
    put, a "log" directory for log files, a "cert" directory for certificates,
    etc.That's how I'd do it. I think that the locations of all the
    resources you need are configurable. If they're not, let us know.
    2) In addition, is there an absloute need for the myserver directory to sit
    under the weblogic tree? I would think it would make sense to not have the
    deployment directory structures not tied to the weblogic installation's
    location.No, it can be anywhere you like. Make sure you adjust the security
    policy
    file so Java 2 will let the server access your classes.
    3) If there are multiple servers that will be deployed (each instantiating
    its own set of services that are implemented as session and entity EJBs),
    does one introduce an entire directory structure for each server or have a
    common directory structure with each server having its own properties file ?
    Currently, I have it setup so that each server that is introduced, e.g.,
    pricing servers, fulfillment servers, etc. has its own properties file and
    that the entire directory tree sits separate from the weblogic installation,
    to facilitate tight integration with source code control. Having resolved
    the regular issues that arise with the CLASSPATH, ClassCastExceptions, etc.,
    we're up and running, but I have had a tough time convincing my developers
    about the merits of deviating from the standard development tree stcucture.The "standard" directory tree exists only for the purpose of running
    the examples that are shipped with WLS. The WebLogic development
    team does exactly what you propose to do, and for the reasons you
    state: to keep our deployment configuration under source control in a
    location that keeps it separate from the examples support in myserver
    and to make it easy to re-install the server without disturbing our
    configuration files. We routinely run WebLogic Server from a
    configuration
    that completely ignores the WEBLOGICHOME/myserver directory.
    Do people have any opinions about this, and are there any experiences they
    can share with me? I'd be more than willing to to change course based on
    others' experiences.
    Sorry for the long-winded message.
    TIA,
    Prashanth--
    Chuck Karish BEA Systems
    (415) 402-7692 http://www.bea.com/

  • Can't I change the directory structure?

              Hello Everybody,
              So far everything is working when use the default directory structure,i.e. mydomain/applications/myWebApp/WEB-INF/classes/some package structure.
              But we have application with lot of html files which call servlets like this..myWebApp/WebApp/myServlet.
              In order not to change my html files, I've created this WebApp directory under weblogic directory structure shown above.
              I've done some trial and error in web.xml file to make servlets execute. But 404 error is showing up.
              I tried putting in web.xml like this...
              <servlet>
              <servlet-name>/WebApp/HelloWorldServlet</servlet-name>
              <servlet-class>com.reliable.servlets.HelloWorldServlet</servlet-class>
              </servlet>
              <servlet-mapping>
              <servlet-name>HelloWorldServlet</servlet-name>
              <url-pattern>/WebApp/HelloWorldServlet/*</url-pattern>
              </servlet-mapping>
              I also tried taking out slash(/) before WebApp but no luck.
              Can any one guide how to make this work.
              Thanks so much,
              Sri
              

    What he needs is something like:
              <servlet>
              <servlet-name>HHH</servlet-name>
              <servlet-class>com.reliable.servlets.HelloWorldServlet</servlet-class>
              </servlet>
              <servlet-mapping>
              <servlet-name>HHH</servlet-name>
              <url-pattern>HelloWorldServlet/*</url-pattern>
              </servlet-mapping>
              HHH is simply to link the mapping declaration to the servlet declaration.
              Then the URL would be something like:
              http://myserver:8801/appname/HelloWorldServlet/abc
              If this is the default app, then appname/ drops out.
              There is a good discussion of this in our docs and
              the servlet spec discusses this as well.
              mark
              Keith wrote:
              > Hi Sri and Alfonso,
              > Did you ever get the code? I am interested in seeing how I can do that too. I
              > have to migrate my servlets and jsp from tomcat and all the html files are referencing
              > the servlets with this format:
              > http://abc/servlet/servletA
              >
              > Thanks!
              > keith
              >
              > "sri" <[email protected]> wrote:
              > >
              > >Hi Alfonso,
              > >Thanks for trying to help me. In your response you said "Just copy my code".
              > >But I didn't find any code in your reply.
              > >Can you please clarify.
              > >Thanks so much,
              > >Sri
              > >"alfonso" <[email protected]> wrote:
              > >>
              > >>You are in wrong, the servlet name is a short name to identify the servlet
              > >in xml file not in URL. You can not load many servlet without to register
              > >it,one by one. But i found a solution, that you can find in servlet without
              > >registration subject. (pe: we have servlets calls as http;//b2web/servlet/XXX)
              > >>just copy my code, or email me if you have problems to [email protected]
              > >>
              > >>"sri" <[email protected]> wrote:
              > >>>
              > >>>Hello Everybody,
              > >>>So far everything is working when use the default directory structure,i.e.
              > >mydomain/applications/myWebApp/WEB-INF/classes/some package structure.
              > >>>
              > >>>But we have application with lot of html files which call servlets like
              > >this..myWebApp/WebApp/myServlet.
              > >>>
              > >>>In order not to change my html files, I've created this WebApp directory
              > >under weblogic directory structure shown above.
              > >>>I've done some trial and error in web.xml file to make servlets execute.
              > >But 404 error is showing up.
              > >>>I tried putting in web.xml like this...
              > >>you are in wrong, the servlet name is
              > >>> <servlet>
              > >>> <servlet-name>/WebApp/HelloWorldServlet</servlet-name>
              > >>> <servlet-class>com.reliable.servlets.HelloWorldServlet</servlet-class>
              > >>> </servlet>
              > >>> <servlet-mapping>
              > >>> <servlet-name>HelloWorldServlet</servlet-name>
              > >>> <url-pattern>/WebApp/HelloWorldServlet/*</url-pattern>
              > >>> </servlet-mapping>
              > >>>
              > >>>I also tried taking out slash(/) before WebApp but no luck.
              > >>>
              > >>>Can any one guide how to make this work.
              > >>>
              > >>>Thanks so much,
              > >>>Sri
              > >>
              > >
              

Maybe you are looking for