locked
Changing the PWA URL RRS feed

  • Question

  • Hi,

    We have a situation with Project Server 2010, where we would like to change the PWA name in the URL, to something else (a customer requirement)

    The environment has some project sites, and some custom reports etc in the Project BI Center (e.g. Content) so we need to keep that happy.

    What is the best way to approach this without breaking anything? The Server name isnt changing or anything.

    Regards

    Rob


    Rob Hardy
    Tuesday, May 31, 2011 9:36 AM

Answers

All replies

  • Hi Rob,

    there is two way to do this,if you want http://technet/pwa  to change  http://myepm.com/pwa than you need to change the alternate access mapping

    internet zone and also  name ,ip resolution from n/w team or if you want to change pwa to something else than you can provide at the time of creating new instance of project server

    Vipin Upadhyay


    Vipin Upadhyay AonHewitt
    • Proposed as answer by Sachin Vashishth Tuesday, May 31, 2011 9:53 AM
    • Unproposed as answer by EPM Tester Tuesday, May 31, 2011 9:57 AM
    Tuesday, May 31, 2011 9:43 AM
  • So from experience, when doing a 5 DB restore you have to use the same site name (e.g. PWA) or things do not work as they should? So for me, I can't really  change PWA this way? There was info on this on Brian Smiths website.
    Rob Hardy
    Tuesday, May 31, 2011 9:57 AM
  • Hi Rob,

    you are doing right thing in wrong way......ones you have provisioned with  /PWA or  /Projectserver  you can't change later on it for for new instance creation.

    FQDN(fully qualified domain name you can change at any moment).

    and it has no relation with restore  you can restore with your default zone URL.

    @Sachin:as We did in many places

    Vipin Upadhyay


    Vipin Upadhyay AonHewitt
    Tuesday, May 31, 2011 10:07 AM
  • So does this mean I have to restore using the same PWA url (kind of what I expected), but I can do something else so users can enter the newer url? Sorry a bit lost,

    Thanks

    Rob


    Rob Hardy
    Tuesday, May 31, 2011 10:18 AM
  • Never tried this before, but if you asking for changing the instance name simply export and import of WSS sites using stsadm will work in this case.

    Like below script.

     

    @SET UTILS_ROOT=C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN

    "%UTILS_ROOT%\stsadm" -o export -url "http://ABC:8080/pwa/Project1" -filename "D:\Temp for WSS extract\backup1.bak" -includeusersecurity  -nologfile -nofilecompression -quiet

    "%UTILS_ROOT%\stsadm" -o import -url "http://ABC:8080/ProjectServer/Project1" -filename "D:\Temp for WSS extract\backup1.bak" -includeusersecurity  -nologfile -nofilecompression –quiet.

    For using above process you need to create new PWA instance with different name but same Project server databases and WSS database.

    And using above script you just import one by one all project site from PWA instance to ProjectServer instance as given above in example.

    Note : You can create the batch file for the same to automate the process.

    Hope this may help you


    Sachin Vashishth MCTS



    Tuesday, May 31, 2011 10:26 AM
  • Hi Rob,

    if you want to modify exsting pwa instance  http://FQDN/pwa   "FQDN"  than it is possible otherwise if you want to modify   http://FQDN/pwa

    "pwa" it is not possible.

     

    Vipin Upadhyay  


    Vipin Upadhyay AonHewitt
    Tuesday, May 31, 2011 10:26 AM
  • Hi Sachin

    I see the 12 BIN directory is mentioned, will this still be okay (using 14 bin) for Project Server 2010, as this is what product I am referring too here

    Regards

    Rob


    Rob Hardy
    Tuesday, May 31, 2011 10:40 AM
  • Yup, sorry my mistake it should be 14 for PS 2010.
    Sachin Vashishth MCTS
    Tuesday, May 31, 2011 10:49 AM
  • Hi sachin,

    export is working fine but at the time of importing you need to provide new URL means new instance of PWA.

    so i think rob is the right fellow to understand requirnment and work accordingly..

    Vipin Upadhyay


    Vipin Upadhyay AonHewitt
    Tuesday, May 31, 2011 12:21 PM
  • Can you explain more Vipin here.

    As I have given the new instance. If you'll notice my my instance name is "PWA" and while inporting it is "ProjectServer", So can explain what I am missing here.


    Sachin Vashishth MCTS
    Tuesday, May 31, 2011 12:43 PM
  • Hi sachin,

    In this case when ur old instance in "pwa" your export will run successfully but when you will try to run import using your "projectsever" it will say that this instance does't exist..........

    So you need to create one new instance "projectserver"  and than import it.

    Its like mapping of one instance to another,and they must exist earlier.

     

    Hope this is detail description...

     

    Vipin Upadhayy


    Vipin Upadhyay AonHewitt
    Tuesday, May 31, 2011 3:18 PM
  • Yes I agree with you vipin there, and I already said above in my post that we need to first create a new PWA instance with different instance name having same project server and wss databases.
    Sachin Vashishth MCTS
    Tuesday, May 31, 2011 6:12 PM
  • Hi Rob

    If i am understanding correctly then this post should work for you : http://epmxperts.wordpress.com/2011/03/05/extend-same-project-web-app-instance-for-different-protocol-authentication-mechanism/

    though this post is targetted for different auth mechanism or protocol but still with same protocol you can extend the pwa on different URL

     

    Let us know if this works


    Thanks | Sunil Kr Singh | http://epmxperts.wordpress.com
    Wednesday, June 1, 2011 8:58 PM
  • HI Rob,

    We would normally BAckup ProjectServer, Delete the curent PWA site, Recreate site based on DB's that already in SQL, and during that process when creating the PWA Site you could give it an alternate name, an as mentioned already use AAM's and DNS records to update the location.

    Have a look at this :http://technet.microsoft.com/en-us/library/cc197480(office.12).aspx

    Andre

    Thursday, June 2, 2011 6:24 AM
  • Hello all,

    I have a similar situation where I need to make change in the name of the Project Name to the FQDN. For example earliert url is http://servername/pwa and I need to make it http://abcd.xyz.com/pwa . I created alternate access mapping and it is working fine. Now I have problem that all the links on the project page still points to the old server name and it have not picked the alternate url. We need to access the Project server from internet and all the links on project server page does not work. Please suggest how can I make change in the links on project page to use the FQDN and not the server name.

    Regards

    Ajay

    Tuesday, March 19, 2013 11:13 AM