Virtual hosting on leopard server

Hello,
I have a leopard server on which I want to have two sites served from the same ip address port combination.
I am using the Server Admin tool bundled with OSX server to configure Apache.
I have created two sites in Sites tab. One has the name "mydomain.org" and the other has the name "machinename".
They are both configured to serve from the same local IP address.
The name "mydomain.org" is served by DNS and the name "machinename" is configured on the client's /etc/hosts file.
From what I know of virtual hosting, the web server receives a http header called 'Host' with the host name that was used on the browser, to select the files to serve. I have sniffed the http network packets from my client machine to the web server and seen this header set correctly to the hostname used on the browser.
The problem is that just one site is being served to both names. I want to select the site according to name.
What can I be doing wrong ?

Done it the hard way.
StuG

Similar Messages

  • How to properly setup virtual hosts on leopard server

    I am not just new to leopard server but new to “server” as a whole. I have bought a 10-client leopard server and installed it on my old macbook couple of days ago because of the gui and seemingly ease-of-setup of a leopard server. I have watched and followed a tutorial on Lynda.com to install my server. Unfortunately, that tutorial focuses mainly on running a single web server. My main purpose of setting up the leopard server is to run multiple virtual hosts. Now my server (which has its own public ip address and I shall refer to it as just IP) is up and running but I seem not to be able to get virtual hostings to work properly. Below is a summary of what I have setup and I hope somebody from the community can take a look and point out what I have done wrong (thanks in advance):
    - server setup as advanced
    - dns settings:
    o I am not sure whether a different zones should be setup for each domain, so I have opted to define 1 primary zone only and then define the other domain as a machine. For simplicity sake, I have only used two domains in the example below. I actually need to setup at least half a dozen.
    o primary zone
    • my1stdomain.com. is the primary zone name
    • ns.my1stdomain.com. is the only nameserver
    • mail.my1stdomain.com. is the only mail exchanger
    • www.my1stdomain.com. as machine and IP as value
    • www.my2nddomain.com. as machine and IP as value
    • mail.my1stdomain.com. as machine and IP as value
    • server.my1stdomain.com. as machine and IP as value
    • ns.my1stdomain.com. as machine and IP as value
    o reverse zone
    • ip reverse mapping ns.my1stdomain.com.
    - web settings:
    o sites:
    • I have defined the following 2 sites and point each of them to a different folder:
    • my1stdomain.com
    • my2nddomain.com
    - I have setup dns at my domain registrar to reference ns.my1stdomain.com for both my1stdomain.com and my2nddomain.com,
    I have no problem accessing www.my1stdomain.com but I couldn’t reach www.my2nddomain.com. and I have a hunch it has to do with my dns settings.

    It sounds like there are two compounding errors here.
    • www.my1stdomain.com. as machine and IP as value
    • www.my2nddomain.com. as machine and IP as value
    By definition, www.my2nddomain.com cannot be a record in my1stdomain.com's zone.
    You MUST have one zone for my1stdomain.com (that contains my1stdomain.com's NS, MX, mail, www etc. records) and a SECOND, separate zone for my2nddomain.com that contain's its records.
    Now the records in my2nddomain.com's zone may contain the same data (e.g. the same A record), or even reference my1stdomain.com (e.g. 'www.my2nddomain.com is a CNAME to www.my1stdomain.com), but they are separate zones.
    Secondly.
    I have defined the following 2 sites and point each of them to a different folder:
    • my1stdomain.com
    • my2nddomain.com
    If you want to access the site via 'www.my1stdomain.com' (or 'www.my2nddomain.com') then your site needs to be setup for www.my1stdomain.com, not my1stdomain.com
    As far as the web server is concerned, 'my1stdomain.com' is a completely different address (and therefore a different site) from 'www.my1stdomain.com. While most poeple set them to the same it is entirely appropriate and valid for them to be two different sites as far as the web server is concerned.
    Therefore you need to change your sites' configuration to reference the 'www' version of its hostname.
    If you want to run both 'my1stdomain.com' and 'www.my1stdomain.com' as the same site then add the other hostname under Aliases (this tells Apache what hostnames should map to this virtual host).
    Try fixing those two elements and try again.
    Finally, it's often far easier for others to debug this kind of problem when you talk in real names, not dummy ones. Telling us what the domains in question are, for example, would allow others to query DNS to see what values you're actually publishing, and would go a long way to answering the question for sure, as opposed to just speculation.

  • Apache virtual host with OSX Server?

    I have been running OSX Server for a while now, and just recently I decided to get McMyAdmin for my Minecraft server. The web client for McMyAdmin runs on port 8080, but I wanted it on port 80. I wanted to use it with my domain, so I just created a sub domain and pointed it to my server. The problem is that OSX Server apparently doesn't let me use port 80, even when websites are turned off. I decided to delete Server and just use plain apache. This worked until I realized that my website was only accessible locally. I have all the correct ports forwarded, etc. But I get the error:
    Response Error.
    Technical description:
    502 Bad Gateway - Response Error, a bad response was received from another proxy server or the destination origin server.
    when I try to connect from outside my network. This is probably just some simple thing I missed but it would be nice if someone could just point out what I did wrong here. Back to the point, I want to know how to run the proxy to my web client on port 8080 AND ALSO run OSX Server with or without apache virtualhost.
    Thanks in advance,
    Eamon

    Web is stupidly easy - Apache has extensive support for multiple virtual hosts in a single server and will happily support as many domains/hostnames as you can throw at it.
    Mail is a little trickier since it needs to hook into some kind of directory server to validate user addresses.
    Mac OS X's Open Directory does support this, but it's a little cumbersome (basically every user has to exist in the main Open Directory domain as well as having a secondary email address(es) in the other domain(s).
    This can get especially tricky when you have users with the same shortname in different domains - for example if you give [email protected] a secondary email address of [email protected] and you then get a new user [email protected], you can't give the third 'joe' the address 'joe' in Open Directory since that's already taken. This means he'll have to login using different credentials from his email address. Confused yet? You bet.
    If you're prepared to eschew Open Directory you can just use Postfix's built-in support for virtual hosting, but it's a little more complex to setup and support and is entirely command-line based (i.e. there's no GUI for setting it up or supporting it).
    So, for that reason you might be prepared to setup multiple virtual machines for each domain. It really depends on how much the domains are related (if at all).

  • Virtual Host on WebLogic Server 5.1

    I need to configure my weblogic server 5.1 on windows 2000 server to make a virtual
    host address.
    How I can do it ????
    Thanks a lot for any help.
    Bye

    Hi Andy,
    I think a good approach for you would be to use a proxy server --
    browser -> proxy that supports virtual hosting -> WebLogic
    Use a proxy which supports virtual hosting, and which can have a separate
    certificate bound to each virtual host.
    That way you can do SSL between the browser and the proxy, and you can
    have the proxy do cleartext to WebLogic.
    This situation gets around WebLogic's limitation of allowing only one
    certificate per instance of the server.
    You could also use 5.1 as the proxy in the following manner:
    Run 3 instances of Weblogic, each as a proxy server, each bound to a
    different IP address and DNS name, having its own certificate --
    one instance for aaa.com, another for bbb.com, and a third for ccc.com
    Then have each of these three instances of WebLogic proxy to your "app
    server" instance of WebLogic on the backend.
    Hope this makes sense.
    Joe Jerry
    Andy Walker wrote:
    Hello,
    I am tasked with implementing a virtual hosting situation that must
    use SSL. It goes like this: https://www.aaa.com, https://www.bbb.com
    and https://www.ccc.com all having separate IPs. These URLs must
    forward the request to the same WebLogic Server instance. The problem
    is each URL must have its own certificate while WLS 5.1 only uses one
    certificate per instance.
    I was thinking about using a proxy server such that all three Web
    servers that would host the URLs would be sent to a proxy server which
    would redirect to the WLS 5.1 instance.
    My questions are, would this be feasible using WLS 5.1 as the Web
    Server and again WLS as the App Server? How secure is this
    arrangement? Is it preferable to use another vendor's software as the
    WebServer(IPlanet, Apache)

  • Defining Virtual Hosts so the Server App does not hijack them?

    Does anyone know how one might define manually define virtualhosts in Lion Server so the OS does not go and trash them, or mess with the conf files? Right now the server keeps stealing any virtual hosts I create manually and creating conf files to the standard of the Server App. The problem is I have several virtual hosts that have custom information in them and I need to restore the file whenever this happens. Any ideas?

    Put all your config files in something unknown to Apple. I like to use 'vhosts' instead of 'sites'.
    Then just add this to your httpd.conf...
    Include /private/etc/apache2/vhosts/*.conf
    I would keep a copy of your httpd.conf at all times. Apple likes to wipe that out on system updates.

  • SSL with virtual hosting in Weblogic Server 5.1(WLS5.1)

    Hello,
    I am tasked with implementing a virtual hosting situation that must
    use SSL. It goes like this: https://www.aaa.com, https://www.bbb.com
    and https://www.ccc.com all having separate IPs. These URLs must
    forward the request to the same WebLogic Server instance. The problem
    is each URL must have its own certificate while WLS 5.1 only uses one
    certificate per instance.
    I was thinking about using a proxy server such that all three Web
    servers that would host the URLs would be sent to a proxy server which
    would redirect to the WLS 5.1 instance.
    My questions are, would this be feasible using WLS 5.1 as the Web
    Server and again WLS as the App Server? How secure is this
    arrangement? Is it preferable to use another vendor's software as the
    WebServer(IPlanet, Apache)

    Hi Andy,
    I think a good approach for you would be to use a proxy server --
    browser -> proxy that supports virtual hosting -> WebLogic
    Use a proxy which supports virtual hosting, and which can have a separate
    certificate bound to each virtual host.
    That way you can do SSL between the browser and the proxy, and you can
    have the proxy do cleartext to WebLogic.
    This situation gets around WebLogic's limitation of allowing only one
    certificate per instance of the server.
    You could also use 5.1 as the proxy in the following manner:
    Run 3 instances of Weblogic, each as a proxy server, each bound to a
    different IP address and DNS name, having its own certificate --
    one instance for aaa.com, another for bbb.com, and a third for ccc.com
    Then have each of these three instances of WebLogic proxy to your "app
    server" instance of WebLogic on the backend.
    Hope this makes sense.
    Joe Jerry
    Andy Walker wrote:
    Hello,
    I am tasked with implementing a virtual hosting situation that must
    use SSL. It goes like this: https://www.aaa.com, https://www.bbb.com
    and https://www.ccc.com all having separate IPs. These URLs must
    forward the request to the same WebLogic Server instance. The problem
    is each URL must have its own certificate while WLS 5.1 only uses one
    certificate per instance.
    I was thinking about using a proxy server such that all three Web
    servers that would host the URLs would be sent to a proxy server which
    would redirect to the WLS 5.1 instance.
    My questions are, would this be feasible using WLS 5.1 as the Web
    Server and again WLS as the App Server? How secure is this
    arrangement? Is it preferable to use another vendor's software as the
    WebServer(IPlanet, Apache)

  • DNS settings for virtual host 10.6 server

    We have just gone through a rebranding exercise, i.e. the company name has changed from 'mycompany' to our 'ourcompany'.
    For various reasons we have decided to not rename our complete setup, but rather add a virtual host for our mail server including a second primary DNS zone for the new domain 'ourcompany'.
    We are hosting our website externally, however since we added the second primary DNS zone incl. an A record (www) pointing to our external website hosts IP for 'ourcompany', workstations on our LAN can no longer access the website.
    Running DIG for 'www.ourcompany.com.au' results in the correct A record IP address being shown, but it is still not showing in any browser – we also made sure we emptied our caches.
    Although we thought this should work relatively easily, we are now totally confused as to the additional primary zones general settings... currently we allow zone transfer and provide an entry in the nameserver section.
    Any ideas as to what might be going on here would be greatly appreciated.

    Mr. Hoffman,
    Than you very much for your reply - unfortunately, despite studying and testing your advice (incl. wesbite) we seem to not get much further.
    Please find our comments inserted below...
    MrHoffman wrote:
    FWIW, both mycompany.com.au and ourcompany.com.au are real and registered domains; I'll presume they're not the domains you're migrating from or to.  Accordingly, I'll use example.org for your old stuff, and example.com for your new stuff; the example domains are RFC-reserved for this usage.
    Correct we are not using my bad example domains.
    Each host should have one A record (and one AAAA record, if you have IPv6 active), and one of the more common errors in these migrations is setting up an A record for each new domain that might arrive; each host has one A (and possibly one AAAA) record, and that's the canonical name for that host.  Externally, that'll probably be the latest name in any sequence (such as www.example.com), and all previous names (including www.example.org) will have CNAME entries.
    To clarify do you mean the following: internally we should not have more than one A record for each host... i.e. one for example.org and one for example.com and presumably any other subdomains should be CNAME records?
    2. externally we should change the A record for www.example.org to a CNAME record and create a new A record for www.example.com;
    Internally (and here's why having a different domain inside is handy) use one of the old names; use example.org, for instance.  This means you can use the public DNS services for the external web sites and resources; your internal DNS servers receive the requests for example.com hosts and go "duh, lemme ask somebody else for that", and that somebody else is the (public) DNS server your external DNS services for example.com hosts.
    Exactly what we had initially done - basically we (naively) thought we could get away with only relying on external DNS translations... however that resulted in mail clients on our LAN loosing their connection every 5-10 minutes, thus we decided to setup another primary DNS zone which fixed that problem but created the other.
    Please also note we have created a subdomain admin.example.com which properly resolves to the CMS backend - btw. from within this backend you can then preview the any page on the regular website with their non www. URLs.
    Since the current setup resolves to the correct IP address I wonder if it could be a problem with the .htaccess rewrite rules the web developer has setup to remove the www. ... or is this too far fetched?
    The usual trigger for not reaching the external A (or AAAA) records is either a stale cache on the particular client (for translations inside the Time To Live (TTL) values for the old DNS translations, or pending a local cache flush on each client), or (and this is more common) confusion over authoritative DNS servers; you have your internal DNS configured as authoritative for the new www.example.com domain, and also authoritative for the old www.example.org domain, and your external DNS is also authoritative for (probably) both domains.  Internal requests get as far as the internal server, and get an authoritative translation (possibly being "no such host"), and don't go any further.
    Safari & Firefox present with 'Server not found' errors.
    So we are still stuck thus any further advice would be much appreciated.

  • IP Virtual Host w/SSL serving on port 80 and 443

    We have an OS 10.3.8 system and we've configured several virtual hosts using the system admin panel. One IP has several hosts on it. We have a seperate IP with one virtual host on it since it is running SSL. I have it configured for port 443 and I have all the security certificates installed OK. The site operates correctly over HTTPs. If I try to access it with standard HTTP I get a service not available error (which makes sense since server admin sets the config files to port 443 ... not 80).
    The only way I can get it to work is to add another virual host in server admin running on that IP at port 80. Unfortunately, that means it will be logged seperately (which I don't really want it to do). What do I need to change to get a single virtual host on a specific IP to respond correctly to both 443 and 80 using the file layout generated by server admin (I can modify them manually)?
    Thanks in advance ...
    Tom

    >The only way I can get it to work is to add another virual host in server admin running on that IP at port 80.
    That's correct. That's how you run a site as both HTTP and HTTPS - they're two sites.
    > Unfortunately, that means it will be logged seperately
    Why? You can set both sites to use the same log file and their hits will be combined in a single file.
    > What do I need to change to get a single virtual host on a specific IP to respond correctly to both 443 and 80 using the file layout generated by server admin (I can modify them manually)?
    You can't, but if your issue is the logging, my answer above should take care of that.

  • Virtual Hosts and CF Server Install

    CF8
    FC8 (yes I know it really has to be RHEL for support)
    Apache 2.2.6
    I am testing out a new webserver for a client. We are trying
    to use apache virtual hosts with a single instance of CF8. This
    will just be a few virtualhosts, not a large amount.
    After some difficulty with installations and the connector I
    was able to get CF8 running with apache. After setting up the
    virtualhosts I only could get to the CFIDE directory after adding
    it as an alias in the virtualhost config.
    If I try to pull up a test cfm file in a virtualhost site CF
    reports file not found. Yet it will pull up the administrator site.
    I assume thats because the /CFIDE path matches that in the main
    webserver root directory.
    Can I run a single instance of CF across apache and its
    virtualhosts? I know CF is running in the VirtualHosts as its an
    error screen from CF. However it just seems like CF is very
    confused when it comes to directory paths.

    I've been fighting the issue all day long. I was so glad to
    come across your post. Unfortunately, there was no answer attached.
    :-( I've figured it out in my install. Hopefully it will be of
    benefit to you.
    Turns out the problem was a permissions error. When
    Coldfusion couldn't read my virtualhost's directory it defaulted to
    the standard wwwroot. To fix it I did a "chmod -R a+rX
    /home/jason/public_html. Then I tried loading the page again and
    all was good.

  • IPlanet Messaing Server v5.1 support Virtual Hosting ?

    Hello, I'm using the iPlanet v5.1 messaging server. I've check the release note said it can support virtual hosting (1 mail server with serveal domain). But, I don't kno whow to configure it. Could you help, please ?

    See chapter two of the Provisioning Guide, http://docs.iplanet.com/docs/manuals/messaging/ims50/pg/domains.htm#16678
    I used the example entries on my home system, worked just fine.

  • Server Migration failed to migrate web server virtual hosts

    I just migrated from an my Mac OS X Server 10.4 to a brand new 10.6 machine. It seems to have copied all my files but failed to bring across the extensive list of virtual hosts I was serving. Entering them in one by one is going to take a while, so does anyone know how to pull them across? I have the old server attached in target mode, but not sure where apache keeps the configuration file for that.

    After some more digging, it appeared that migration assistant just completely failed to set up the Open Directory on the new server. Fortunately, I managed to get the old drive cloned to an ATA drive, which I used to boot an ancient G4 tower, from whence I was able to do an Open Directory export and import into the new server.
    I seem to be having the same inability to Kerberize the Open Directory that a lot of other people seem to have, but I don't actually need that feature, so it's not a big deal.

  • Virtual Hosts - What am I doing wrong?

    Hi,
    I have been running virtual hosts on Tiger Server for over two years with no problems. Now I have installed a new server running Leopard Server and am trying to move the sites from Tiger to Leopard (on different machines)
    No matter what I do on the Leopard server I can not get the virtual hosts to work. As far as I can see I have configured them the same way that they were on Tiger, but when you go to the domain for the virtual host you are taken to the default server.
    If you disable the default server you get to the correct page, but that's probably because the virtual host is now acting as the default server.
    I have * as the address. If I change that so that the default server is * and the virtual host is the IP address of the server then it works, until I try to add another virtual host and the same thing starts all over again.
    Any ideas what I might be doing wrong?
    Regards
    Craig

    Ok that's weird. (or is it?)
    If I change the order of the sites in Server Admin so that the default server is now the last entry, the vhosts suddenly work. This wasn't necessary in Tiger.
    So if I have a list of sites like this:
    Enabled - <no domain> - Address: * - Port: 80
    Enabled - vhost1.com - Address: * - Port: 80
    Enabled - vhost2.com - Address: * - Port: 80
    Then either of vhost1.com and vhost2.com are redirected to the site hosted under the default domain.
    If I make the list like this:
    Enabled - vhost1.com - Address: * - Port: 80
    Enabled - vhost2.com - Address: * - Port: 80
    Enabled - <no domain> - Address: * - Port: 80
    Then the server works as it should.
    It's almost like the last entry is a catch all. Which would make sense since that is effectively what I use it for anyway. But I never had to do this in Tiger server, and technically what should it matter?
    Or is this indicative of some other config error on my installation?
    Cheers
    Craig
    Message was edited by: Craig Hind

  • How to confiture virtual hosts with multiple domain names

    hello,
    I've read through some of the postings here on virtual hosts, but I thought I'd better solicit advice before I actually try some of the things I've read about.
    In a nutshell, I've purchased multiple domain names that I'd like to alias to a new site (currently it is just a subfolder in the main site directory) on my OS 10.3.x server. There is only the one main site configured right now on the box, so I know I need to set up a second "virtual site" pointing to the files in this subfolder to make it function as its own site.
    I've dabbled around with the sites settings in the GUI, but I'd probably be most comfortable setting all this up in the httpd.conf by hand if I could. But I'm weary of this because I know it might be better to use the GUI because of OS X Server's flavor of WebObjects and Apache (sigh).
    So, I have two main questions:
    1) How would I set up this second site using the GUI in server settings? Do I need to first move the subfolder out of the main folder before it can be designated its own site? Or can I just point to it in the GUI? Can I use one of my purchased domain names in the domain field?
    2) Currently, I have URL Forwarding set with my multiple domain names, but I'm thinking there might be a better way to do this? For SEO I'd rather use some type of redirect rather than being penalized by search engines for having what looks to be multiple domains pointing to the same site.I'm thinking I should create virtual sites for each domain name I've purchased with a hard redirect back to the main site?
    Any suggestions would be appreciated.
    Thanks
    G4 Mac OS X (10.3.9) 10.3.9 Server
    G4 Mac OS X (10.3.9) 10.3.9 Server

    thank you for your reply.
    > You can create each site as a new Site in Server
    Admin. When you do this you can choose any
    directory on disk as the document root for each
    site.This means you can move the sites' folders out of
    /Library/WebServer/Documents if you like - you could
    create /Library/WebServer/site1,
    /Library/WebServer/site2, etc. (or even be outside of
    /Library/WebServer if you want).
    so, are you are saying that I could designate one site to be
    /Library/WebServer/Documents/site1
    and another to be
    /Library/WebServer/Documents/site1/directory1
    even though directory1 is contained within site1's structure? I'm not advancing this as a good idea, necessarily. I'm just wondering if Apache would complain.
    > Each site should have the domain name set as per your
    registered domains. Apache will need this to
    determine the correct site to serve for each
    request.
    Well, after some additional research I'm thinking I'm missing a critical piece of the puzzle. That being access to the DNS host server that manages the context of my server. I have purchased domain names through an outside registrar that point to my site and I can create virtual hosts on my server, but I don't have the ability to add the new virtual host names into the DNS server that manages my box. If that makes sense. Or maybe I'm missing something?
    >
    I'm not sure why you're using URL forwarding at all.
    Without that piece of information it's impossible to
    tell you whether you should continue using them or
    not - in general there's no need to use URL
    forwarding if you have multiple Virtual Hosts setup,
    but it sounds like you have multiple hostnames
    pointing to the same content, so your needs may be
    different.
    I'm using forwarding for the reason I list above. I didn't purchase hosting with the registrar where I purchased my domain names, so they are parked on the registrar's name server with URL forwarding to my server. The DNS server that manages my box resides in a different location and I don't have the ability to add DNS entries pointing to virtual hosts that I want to set up. Am I stuck?
    G4 Mac OS X (10.3.9) 10.3.9 Server

  • Do OS-X style Virtual Hosts work in 10.5.5?

    The tips for setting up virtual hosting I've seen in these discussions suggest that OS X Virtual Hosting wasn't working before. Is it now or do I need to edit things with Terminal?

    pterobyte wrote:
    The instructions in the PDF you refer to do not say that you will get separate mailboxes, just how to associate multiple e-mail addresses with one account (=1 mailbox).
    From the PDF: "For example, if your domain is example.com and the virtual host domain is server.com, and you want mail addressed to [email protected] to be delivered to user bob, open bob’s user record in Workgroup Manager," and "This causes mail sent to your mail server for [email protected] to be actually sent to the real mail account for user bob. "
    This clearly states mail for [email protected] will go to user bob and not to a seperate mailbox.
    The very last line of that section (which you didn't quote) says "Meanwhile, mail to [email protected] will go to another designated mail account."
    I took that to mean that if [email protected] was also a short name under bob, then those two address = two mail boxes (so as each domain was under Virtual Hosts and not under aliases).
    Re-reading it now, I'd say that sentence is rather ambiguous. I can see how it could support what you say, but also how it leads me to believe what I did.
    Do you actually need separate mailboxes at all?
    Yep. It's only for a few people. Consultants who work under various domains, and need/want segregated mail boxes.
    I'm moving these accounts from a Communigate server where separate mailboxes are already the experence these people are accustomed to.
    At any rate, multiple users it is, and the 10-user revelation is also a a big help to know that creating multiple users is not an issue.
    It's a shame the GUI doesn't have Long Name and then a Domain field (which would then be used in User lists) -- kinda lame to have to write the Long Name with extra stuff to tell them apart. (without memorizing the IDs). I suppose I could manually assign ID ranges to imply my own arbitrary groupings. 1200+ = domain x, 1500+ = domain y ? Not very explicit though.
    Thanks for the discussion.
    -- gw

  • How to get virtual hosts to have their own default webapps?

    Is there a way to have several virtual hosts to have their own default
    webapps?
    I have five virtual hosts on my server, and I used to be able to deploy the
    webapps to the server, target a server and a virtual host, and then the
    default app to use. But I can't see that anymore in wls8.1. I looked
    around the web for some help, and all I could find was some reference to the
    <context-root> node. The problem with that solution is, when I put that in
    each of the webapps for the virtual hosts, only one gets the "/"
    context-root, and the rest can't use that.
    I would like to be able to have users just type out the virtual hosts URL to
    get access to the webapp. Surely a server as powerful as WebLogic can do
    that. I used to be able to do this in 7.0sp1. Any ideas? Thanks.

    Unfortunately you cannot split (nor merge) items purchased with an AppleID.  I am not clear on what you will have to do to allow them continued access to their music on your account.  Apple no longer has DRM protection in its music but then I also hear people have all kinds of authorization issues when trying to synch so it sounds like they still keep restrictions on what you can do with the music when trying to move it about.  I'll let somebody more experienced with syncing answer this part.  You may have to authorize their computers and devices to your AppleID to allow them all functionality with the music.
    Ideally you would have set them up with their own AppleIDs years ago but...
    Creating an iTunes Store, App Store, iBookstore, and Mac App Store account without a credit card - http://support.apple.com/kb/HT2534 - only works for new accounts!

Maybe you are looking for