« Previous Next »

Thread: Different Physical Path and Name for migrated application

Last post 07-15-2009 11:02 AM by sasikantt_24. 9 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (10 items)

Sort Posts:

Shortcuts

Search | Active Posts | Unanswered Posts | View all users

  • 05-13-2009, 5:54 AM

    Different Physical Path and Name for migrated application

    Reply Contact

    Hi,

    Is it possible to have different application name and physical path for the application that we will migrate using MS Deploy?

    If yes can some one tell me the Providers for the same.

    Thanks in advance

     

  • 05-13-2009, 10:24 AM In reply to

    Re: Different Physical Path and Name for migrated application

    Reply Contact

    yes this can be done. The actual syntax will be based on whether you are migrating from IIS 6 to 7 or its a sync between iis 6 boxes or between iis 7 boxes. The following command syncs MyApp on source to MyNewApp on the destination and changes the physical path from whatever it may be to "C:\NewDir"

    msdeploy -verb:sync -source:iisapp="Default web site/MyApp" -dest:iisapp="Default web site/MyNewApp",computername=servername -setParam:type=DestinationVirtualDirectory,scope="Default Web Site/MyApp",value=C:\NewDir

    You can read more about iisApp here and setParam here

    Let me know if you need more info.

  • 05-20-2009, 10:14 AM In reply to

    Re: Different Physical Path and Name for migrated application

    Reply Contact

    Hi

    I used following ms deploy commands to change my application name and physical path for migrated application on server where IIS 7.0 is installed, but nothing is updated.

    Please find the command and output of the command and kindly correct me, where I am going wrong.

    msdeploy -verb:migrate -source:metaKey=lm\w3svc\1\root\MyApplication -dest:auto,computerName=Servername -setParam:type=DestinationVirtualDirectory,value=D:\DeptName-MyApplication,scope="Defaul
    t Web Site/MyApplication" -setParam:type=ProviderPath,value= DeptName-MyApplication,
    scope="Default Web Site/MyApplication" -enableLink:AppPoolExtension
    Action: Updating metaProperty (/lm/w3svc/1/root/MyApplication/UNCPassword)
    Action: Updating metaProperty (/lm/w3svc/1/root/MyApplication/UNCPassword)
    Action: Updating filePath (D:\DeptName\MyApplication\AppMessages.xml)
    Action: Updating filePath (D:\DeptName\MyApplication\MyApplication.asmx)
    Action: Updating filePath (D:\DeptName\MyApplication\MyApplication.wsdl)
    Action: Updating filePath (D:\DeptName\MyApplication\bin\Some.dll)
    Action: Updating filePath (D:\DeptName\MyApplication\bin\MyApplication.dll)
    Action: Updating filePath (D:\DeptName\MyApplication\bin\MyApplication.pdb)
    Action: Updating filePath (D:\DeptName\MyApplication\Global.asax)
    Action: Updating filePath (D:\DeptName\MyApplication\web.config)
    Action: Updating metaProperty (/lm/w3svc/1/root/MyApplication/UNCPassword)
    Change count: 11

     

    Nothing is updated on server where IIS 7.0 is installed when I migrate Myapplication from server where IIS 6.0 is installed.

    Thanks
    Tags:

  • 05-20-2009, 1:12 PM In reply to

    Re: Different Physical Path and Name for migrated application

    Reply Contact

    :) I am able to change my VirtualDirectory name using DestinationVirtualDirectory provide after migrating the application from IIS 6.0 to IIS 7.0. I change scoupe in my earlier command.

    Thanks a lot moshaikh.

    :p Now I want to change my application name on IIS 7.0 after migrating application, I am using ProviderPath provider to accomplish this. but no luck...

    Can any one help me with this?

  • 05-20-2009, 1:22 PM In reply to

    Re: Different Physical Path and Name for migrated application

    Reply Contact

    For changing application name you dont need setParam. Just specify the new app name during migrate in the command as follows:

    msdeploy -verb:migrate -source:metaKey=lm\w3svc\1\root\MyApplication -dest:metakey=lm\w3svc\1\root\MyNewApplication,computername=ServerName

    Let us know if you need more information.

  • 07-13-2009, 12:03 PM In reply to

    Re: Different Physical Path and Name for migrated application

    Reply Contact

    Thanks moshaikh. I can now change path as well as application name while migrating from IIS 6.0 to IIS 7.0.

    Actually my concern is, I have all applications under Default Web Site in IIS 6.0. But after migration I don’t want these applications under Default Web Site.

    I want separate Web site for each application.

    I tried with following command:

    msdeploy –verb:migrate –source:metakey=lm/w3svc/1/root/MyApplication –dest:metakey=lm/w3svc/2/MyApplication,computername=iis7.0server_name

    It’s giving me an error.

    Error:  Metabase keys /lm/w3svc/1/root/MyApplication and /lm/w3svc/2/MyApplicationn are not compatible for syncing

    Can you please let me know, how can we move application outside Default Web Site while migration using MS Deploy?

    Thanks
    Shashikant

     
    Tags:

  • 07-14-2009, 1:21 AM In reply to

    Re: Different Physical Path and Name for migrated application

    Reply Contact

    Can you clarify  whether you want to move the applications you have under "Default Web Site" on IIs6  under "DifferentSite" on IIS 7

    or you want to create one site in IIS 7.0 for each app that you have in IIS6.

    Based on your needs I can help you further.

    Thanks

     

  • 07-14-2009, 2:26 AM In reply to

    Re: Different Physical Path and Name for migrated application

    Reply Contact

    I want separate web site on IIS 7.0  for each application under "Default Web Site" on IIS 6.0.

    Thanks,
    Shashikant

    Tags:

  • 07-14-2009, 12:10 PM In reply to

    Re: Different Physical Path and Name for migrated application

    Reply Contact

    You can achieve this by migrating each application to an existing site. For e.g if you have "App1", "App2" and "App3" under default web site in IIS 6.

    You would manually create 3 websites App1, App2, App3 on IIS 7 using appcmd. For e.g.:

    C:\Windows\System32\inetsrv>appcmd add site /name:"App1" /id:2 /bindings:http/*
    :84 /physicalPath:"C:\inetpub\App1"

    Once you have these sites in IIS7 you can sync from iis6 as follows

    msdeploy -verb:sync -source:iisApp="Default Web Site/App1" -dest:iisApp="App1",computername=thenewserver

    Let me know if you need more info.

  • 07-15-2009, 11:02 AM In reply to

    Re: Different Physical Path and Name for migrated application

    Reply Contact
    Yes we can do this. But previously I was writing manifest file which was containing 2 metakey elements. One for application pool and one for web site. Application pool was setting properly for web site with that approach after migration. Also I was writing single ms deploy command to achieve this.But now I have to migrate application pool first and then I have to create web site using AppCmd and then I need to synchronize web site using ms deploy command that you have mentioned above.
    With this approach I don’t have application pool set for the web site after synchronization. It’s “DefaultAppPool” and not the application pool that I have migrated.How can I set application pool that I have migrated for the Web site? Should I write AppCmd again to set application pool for the Web site?

    Thanks,
    Shashikant
    Tags:
Page 1 of 1 (10 items)
Microsoft Communities