MDS directory structure - Standard guidelines

Hi,
I am trying to setup MDS repository for my SOA projects and looking for a standard directory structure which complies with AIA standards too.
In most of the company's we use structure like
*/apps
*/apps/xsd
*/apps/wsdl
or for AIA, we put like
/apps/ABCComponents/ApplicationObjectLibrary/[ApplicationShortname]/[Entity]/
Could someone please point me web doc or oracle article which describe these. I search in oracle support but could not find specific doc.

Hi,
With the AIA foundation pack you get the AIAMetaData directory structure provided:
See http://docs.oracle.com/cd/E23943_01/doc.1111/e17364/bldgintflows.htm#FPDEV128
We have had to make our own decisions regarding where we add our own bits to this. We tried to match the conventions used by AIA as far as possible.
I hope that helps
Robert

Similar Messages

What should be directory structure for Custom MDS files?

Hi,
I have personalize a page and then exported the personalization.
Now my requirment is to migrate this personalization to other server, for which clients want steps specific to UNIX.
My doubt is where should I copy these files on the server to import the personalization using XMLImporter command? ( Client do not have JDev on his server, so can not use impot command)
my custom_top structure is like '/u02/int/applmgr/CUSTOM/xbol/11.5.0'
The customization is part of product 'OTA'
I am confused about where to put(Directory structure on custom top) customization and other MDS file to import using XMLImport.
This customization is also using a Custom LOV for which, I have given the path xbol/oracle/apps/ota/admin/enrollment/webui/XbolGradeRN.
For now I have transfered the file from window based JDeveloper and things are working fine. I need the UNIX directory structure for MDS files.
Please help to clear my this doubt.
Regards,
Adarsh

There is nothing specific to UNIX since the files are never picked from the file system on a production instance. You can place them under a temp directory with the proper package structure, the same way you exported personalizations for the seeded pages and the same custom package structure for your new pages and run import command. It's only how you run your import command matters, if you have placed the files in the proper package under some temp directory just give the -rootdir to point to your temp directory and no -rootPackage option.

Guidelines regarding directory structure for multiple Oracle homes on Unix!

Hi All,
Are there any guidelines published regarding directory structures that should be defined while using multiple Oracle homes on Unix/Linux box?
I am looking for guidelines regarding admin and oradata folders so that we dont accidentally mess up with the DB contents with a wrong Oracle home.
Its a development server with 8i and 10g. 11g might also get loaded on the same server in future.
Thanks in advance...
Regards

Thanks Maran.
I have already checked many installation guides before posting here. All of them mention about creating folders like /admin or /oradata on various mount points but none of the naming conventions really indicate whether it is a 8i database or a 10g database.
This is required when you are having multiple Oracle installations under /opt and databases are running from different mount points.
Regards,

Changing file name and directory structure for use outside of iPhoto

Hi,
I was wondering if its possible to get iPhoto to name the files from my library to reflect the names that I've given the files in iPhoto. I'm thinking along the lines of iTunes, where its possible to chose in the preferences how the files are named, and there is some logical directory structure, such as "Artist/Album/01 - Track 1.mp3". These file names are updated to reflect any changes made in iTunes.
I've heard the argument that I shouldn't ever want to do anything with the files themselves because iPhoto can do everything I would ever want to do, but I want to organize the files so that not all of my organizational work is lost if I decide to stop using iPhoto and transition to a different system. Any suggestions would be appreciated.
Thanks,
Adrian

Adrian
No it's not possible.
You can rename the files before bringing them into iPhoto, you can rename them with the titles on Export (Use the File -> Export command, it gives you the option to use the title and filename) but when it's inside iPhoto you cannot rename the files.
However, all is not entirely lost. Using Film Rolls (View -> Film Rolls) you can move pics between rolls, name rolls, create rolls and so on, as long as you do this in the iPhoto Window, and these changes will be reflected in the iPhoto Library Folder.
If at some point you decide to chuck iPhoto then (if the new app won't read iPhoto database files) you can simply export each album you've created to a Folder (using the File -> Export command as I suggest above), this, along with exporting slideshows will preserve your organisational efforts.
The iTunes database has a rather simple job to do: track a file and it's assorted metadata. iPhoto, on the other hand, tracks a file and it's assorted metadata, plus a Modified version, plus a thumbnail. If you consider what happens when you edit a pic, for instance - Copy Original, perform edit, save modified version, remove Original Thumbnail and then create new one - you can see it's a rather more complex job.
Finally, the standard warning: It is strongly advised that you do not move, change or in anyway alter things in the iPhoto Library Folder as this can cause the application to fail and even lead to data loss. Any changes you make must be made in the iPhoto Window.
Need more info? by all means post again.
Regards
TD

Package and Directory Structure

Hello --
I work in a group that supports 3 web sites. (b2b, b2c, b2e)
We're just beginning to develop Java in-house and
currently using Solaris and JDK 1.2.x.
I need to propose a package and directory structure strategy.
The "reverse the domain name" guideline makes sense to me.
My first thoughts are: ("classes" dir could be created anywhere)
classes/com/ppco/b2X/ <--- for .java and .class files (development)
lib/ <--- for b2X JAR files (ready for test or production)
util/ <--- for our utility classes like DBAccessor
lib/ <--- for our JAR files
sun/ <--- for classes like com.sun.mail pkg
lib/ <--- for JAR files like mail.jar
org/ <--- for classes in org.omg.CORBA pkg
lib/ <--- for JAR files
We need to handle 3rd party classes.
Development would be done in the b2X tree and JAR files would
be installed the lib/ dir for testing and release to production.
Does anyone have recommendations or experiences to share ?
Are there some things to avoid ?
Thanks !
Al

Hello Al,
you are on the right track. A typical convention I follow is:
<project>
bin - for startup scripts, etc. to run your application
build - for build scripts (not necessary if you build using your IDE. See below.)
classes - for my compiled classes
lib - for my 3rd party libraries
src - for my source code
test - for my test code (see http://junit.org/ )
That's the project hierarchy. The src (i.e. the package heirarchy) structure is another story.
As you say, you start with the reverse domain name. This is to give your packages a unique namespace. After that, your best guide is practice. Packages can be larger or smaller, depending on your coding practices. Usually you would have these (exact names may differ), plus others:
com/ppco/client
com/ppco/server
com/ppco/common
com/ppco/db
I think your break down of sun, org, etc. is a bit too much. If you would like to do so, however, I recommend you do the separation under /lib. This way, the top level project directory is not polluted by the different types of libraries in use.
Regards,
Manuel Amago.
From build above: I would suggest you always build your release distribution directly with the JDK, not using any IDE compiler. This is because Sun's JDK is the reference implementation, thus, any compatibility issues are not yours.
An easy way to achieve this is by using ANT (see http://jakarta.apache.ort/ant/ ).

New Custom OAF project - Directory structure

Hello,
I am a newbie to the OAF. I am trying to set up a totally new custom OAF project (using Jdeveloper 9i)
In our current directory structure under $JAVA_TOP, there is no folder/directory for custom projects. Is there a recommended standard directory structure that needs to be used for custom projects/applications? or is it advisable to set up a new directory and the children directories underneath? If new directory needs to be set up what is the logical structure? Can any one provide an example?
Thanks,

Thank you Gyan for the feedback. One last question about the directory structure:
We have a custom schema in our current Oracle Apps DB (let us say 'zz'). As far as I know there is no specific responsibility associated to this schema. In the current non-OAF prod world, we develop custom forms/reports based of the tables in that schema 'zz'. We tend to think of this schema as a custom module. Eventhough there is no specific responsibility associated to this schema, forms/reports developed of this, would be registered to relavent module. ie., AP, GL, FL, PN etc.
If I want to use the tables from that schema and build OAF projects/pages, would my directory structure be still the same as I mentioned before but with zz as the module? i.e, $JAVA_TOP/xx/oracle/apps/zz/?
Thanks,

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>


     <target name="ear" depends="web">
          <echo>Entering the EAR process</echo>
          <ant antfile="ear.xml" target="${directive}"/>
     </target>

     <target name="web" depends="business">
          <echo>Entering the Web process</echo>
          <ant antfile="web.xml" target="${directive}"/>
     </target>

     <target name="business" depends="ats_ejb">
          <echo>Entering the Business process</echo>
          <ant antfile="business.xml" target="${directive}"/>
     </target>

     <target name="ats_ejb" depends="integration">
          <echo>Entering the Prototype EJB process</echo>
          <ant antfile="ejb.xml" target="${directive}"/>
     </target>

     <target name="integration" depends="common">
          <echo>Entering the Integration process</echo>
          <ant antfile="integration.xml" target="${directive}" />
     </target>

     <target name="common" depends="vo">
          <echo>Entering the Common process</echo>
     <ant antfile="common.xml" target="${directive}"/>
     </target>

     <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">
     
     <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"/>
     
     <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>
     
     <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>
     
     <target name="compile_source" depends="copy_files">
          <echo>Compiling source</echo>
          <javac srcdir="${localdir}/business/src" destdir="${build}" >
               <classpath refid="library.path"/>
          </javac>
     </target>
     
     <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

Web app directory structure

Is there some standard directory structure when building J2EE web application that consists for example JSP pages, servlets, EJB components, pictures etc.

place all your jsps in "jsp" folder under the project folder.
Create a folder called "WEB-INF" under the project folder which contains all your servlets, and web.xml and taglib.tld files. Your servlets that is .class files should be in a folder "classes" under "WEB-INF".
The .html files and picture files are under the project folder.
I hope it will help you some how.
But, the directory structure depends upon the Framework you are using such as Struts, Spring or Axis.

Where to keep new OA page(RN.XML in oracle Application Directory structure?

I have created a new XML region which I want to use in page through Personalization.
where should I copy this file into Application Directory structure?
I am using this command to import -
import C:\OA\jdevhome\jdev\myprojects\xbol\oracle\apps\ota\admin\enrollment\webui -jdk13 -mmddir "C:\OA\jdevhome\jdev\myhtml\OA_HTML\jrad" -rootdir C:\OA\jdevhome\jdev\myprojects -validate -username apps -password apps -dbconnection "(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(Host = xxxas.com)(Port = 0000)))(CONNECT_DATA = (SID = xxx)(SERVER = DEDICATED)))"

I imported the XML file but when I am trying to refer the xml file through personalization by giving path
'xbol\oracle\apps\ota\admin\enrollment\webui\XbolLearnerSearchRN'
It is erroring out saying
'Extends: Invalid value: xbol\oracle\apps\ota\admin\enrollment\webui\XbolLearnerSearchRN: the reference may not exist. (oracle.adf.mds.MetadataDefException: Unable to find component with absolute reference = xbol\oracle\apps\ota\admin\enrollment\webui\XbolLearnerSearchRN, XML Path = null. Please verify that the reference is valid and the definition of the component exists either on the File System or in the MDS Repository.)'
My requirment is - I want to use this xml file in FlexLayout for the personalization.
Please Guide me, where I am missing.

Best Practice Directory Structure

I'm new to programming and I'm creating a large application
that will have a lot of pages and components. As I continue to add
to the project, I find it harder and harder to easily locate the
pages and components that I need to work with. To help me with this
problem, I've decided to add a label to every component with the
location of where it can be found. Now when I view the application
and I see a component I want to work with, I know where it is
located.
This is problably not the best way to handle the problem, it
will be a pain to go back and remove or comment out these when I'm
fininshed with the project, but it wil help now.
Short of having a better memory :>), is there any best
practice guidelines I should look into and follow when I create my
directory structure of files and components that will intuitively
help me quickly locate a component? What do you use to help you?
Thanks for your ideas and suggestions

There are many ways to answer this. If you have a big project
you might consider using a Flex Library Project for your components
- think of it as writing a set of components you (or your company)
might one day sell to others - even if you never have that intent.
The idea is to make the components as reusable as possible in case
you need them for the next project. Having them in a separate Flex
Library project (which creates a .swc file) would make that easier.
The industry best-practice seems to be to create packages
that begin with your company's domain name, but in reverse order.
For example, components I write for Adobe go into a package
beginning with com.adobe which works out to be the file structure
com/adobe and then is further divided by the application and then
its parts (eg, com.adobe.scrapbook.editor). Using your company's
domain to distinguish your components enables you and others to
combine components from different places without naming conflicts.
If you divide your application into logical parts you can
figure out a good package naming convention that is easier to
remember. For example, I might put all of the skins for my
Scrapbook Editor into the com.adobe.scrapbook.editor.skins package.
I can easily find those files and add to them as necessary.
Other people follow a similar pattern and there are books on
the subject, too.

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/

Import statement and directory structure

First of all, sorry for such a long post, I believe part of it is because I am unsure of the concept of importing in Java. Secondly, Thanks to anyone who can ultimately enlighten me to the concept of import. I did ask this question before in the "erorr and error handling" forum, and the people who have helped me there did a great job. But, I believe I require a little more clarification and thus have decided to post here.
Anyhow, my question..
Could someone explain to me the concept of the import statement, or direct me to a webpage with sort of explanation for newbies? For some reason, I am having a hard time grasping the concept.
As I understand it, the import statement in Java, is very similar to the namespace keyword in C. That is to say, import doesn't actually "import" any source code, the way that the #include statement does in C.
So I suppose what my question is, say I have a java class file like below:
//filename: sentence.java
//located: c:\school\csc365
package csc365;
class sentence
//some variables here..
//some constructor here..
//some methods here..
And some sample program like the one below which implements the above..
//filename: test.java
//located: c:\school\csc365
import csc365.*;
import java.io.*;
class test.java
//creates some sentence object
//uses the object's methods
//some other things.
As I understand it, the test.java file should not compile because the csc365 package is not in the correct directory. (assuming of course, the classpath is like c:\school\csc365;c:\school )
But, ... where then should the sentence.java be located? In a subdirectory of c:\school called csc365 (i.e c:\school\csc365\) ?
And thus that would mean the test.java file could be located anywhere on the hard drive?
I suppose, I just need a little clarification on the correlation between a package's "name" (i.e package csc365; ) and its corresponding directory's name, and also how the javac compiler searches the classpath for java classes.
..So, theoretically if I were to set the classpath to look in every conceivable directory(provided the directory names were all unique) of the harddrive, then I could compile a test.java anywhere?
As a note: I have been able to get the test.java file to compile, by leaving out the import statement in the test.java file, and also leaving out the package statement for the sentence class, but I assume this is because the files are defaulted to the same package?

Hi Mary,
No, import isn't analogous to C++ namespace - Java package is closer to the namespace mark.
import is just a convenience for the programmer. You can go your whole Java career without ever writing an import statement if you wish. All that means is that you'll have to type out the fully-resolved class name every time you want to use a class that's in a package other than java.lang. Example:
// NOTE: No import statements
public class Family
   // NOTE: fully-resolved class names
   private java.util.List children = new java.util.ArrayList();
}If you use the import statement, you can save yourself from typing:
import java.util.ArrayList;
import java.util.List;
public class Family
   // NOTE: fully-resolved class names
   private List children = new ArrayList();
}import isn't the same as class loader. It does not bring in any source code at all.
import comes into play when you're compiling or running your code. Java will check to make sure that any "shorthand" class names you give it live in one of the packages you've imported. If it can't find a matching fully-resolved class name, it'll give you a message like "Symbol not found" or something like that.
I arrange Java source in a directory structure that matches the package structure in the .class files.
If I've got a Java source file like this:
package foo.bar;
public class Baz
   public static void main(String [] args)
        Baz baz = new Baz();
        System.out.println(baz);
   public String toString()
       return "I am a Baz";
}I'll store it in a directory structure like this:
root
+---classes
+---src
      +---foo
           +---bar
                +---Baz.javaWhen I compile, I go to root and compile by typing this:
javac -d classes foo/bar/*.javaI can run the code from root by typing:
java -classpath classes foo.bar.BazI hope this wasn't patronizing or beneath you. I don't mean to be insulting. - MOD

Organize iTunes file list by Directory Structure instead of artist/album?

Hello, I have searched for different audio players for os x which might have this feature but so far have had no luck. What I'm looking for is a feature similar to that of foobar2000 for win32 where I can organize my music by directory structure without the iTunes automatic organization by artist/album. Is there a way I can accomplish this in iTunes with some sort of xml config or hidden options? Thanks.

You don't have to have iTunes move music around on your hard drive (Preferences>Advanced>General, uncheck Keep iTunes Music folder organized and Copy files to iTunes Music folder when adding to library) but I suspect that's not what you're asking. You can't automatically view music from within iTunes by directory structure. iTunes organizes by ID3 tags ("mp3 tags"). You could, I suppose, spend a lot of time replicating your directory structure by using folders and playlists within iTunes but you'd probably have to do it all by hand.
You could check out Doug's Scripts to see if there are some scripts that might help.
http://dougscripts.com/itunes/index.php

How to create a tree based on directory structure

I want to create a hierarchical tree in Forms 6i based upon a file system directory structure (similar to Windows Explorer). How can I populate a tree with this information, is there something that I can call or write that would return the file system structure in a format that I can populate my tree?
Any advice would be greatly appreciated.
Thanks
Richard

Your link does not seem to work.They're re-jigging all the links to accomodate the hot poop on Oracle's latest and greatest, 10G. So at least the website is on schedule even if the actual software delivery dates have slipped :P
We can still get D2KWUTIL from here: http://te chnet.oracle.com/software/products/forms/content.html
Cheers, APC

Directory Structure for multiple applications at one host

Can I have multiple (more than one) WEB-INF directory structures in the public_html directory for different web applications? If I do this, how do setup the url-pattern in the Servlet Mapping tag in the web.xml file? How do I setup the URL that calls the servlet from the HTML that has been send to the user�s browser?

If I understand your question, you want multiple contexts. All App Servers/Web Servers allow you to setup multiple contexts. Normally if your root context is in /home/myhome/app_server/
then you would setup multiple contexts by creating a folder for each context:
/home/myhome/app_server/context1/
/home/myhome/app_server/context2/
Each would have their own full application/website. And the way to reference these would be as such:
if the domain, www.mydomain.com, is mapped to /home/myhome/app_server/
www.mydomain.com/context1/
www.mydomain.com/context2/
I think that is what you were asking. Hope it helps

MDS directory structure - Standard guidelines

Similar Messages

Maybe you are looking for