The installer created the "SDLWebTridioncm_MAN01SQL05" CM environment for you (it asks you for the name in one of the screens). Since then, apparently someone decided to clear or recreate your Topology Manager database -- so it lost the information again. The Topology Manager website hasn't been restarted either, so it thinks it still exists.
Anyway, since ...
It is an Environment variable called TRIDION_TTM_SERVICEURL
You can also add -TtmServiceUrl parameter to all your commands (but this is mostly used if you want to run Powershell script from another machine), for example
Add-TtmCdTopologyType -Id StagingTopologyType -Name StagingToplogyType -EnvironmentPurposes "Staging" -TtmServiceUrl http://host:port/...
Adding a CD Topology Type in Topology Manager doesn't result in any communication with CD or CM, so the Authorization error is coming from Topology Manager itself.
Only users in the Windows Group "SDL Topology Manager Administrators" are allowed to change things in Topology Manager. By default, this includes all Windows Administrators, but the catch here is ...
It is (surprisingly) Topology Manager website which hosts odata service inside.
The proper endpoint is http://host:port/ttm201501.
There you can browse/add/remove Topology Manager entities using GET/POST requests (if you do not want to use powershell for some reason, which does it behind the scenes).
Note that your example URL paths may or may not be Web Applications in Topology Manager. For example: a DXA Web Application can resolve such URL paths to different Publications; there is only one physical Web Application (root level), but it can serve several Publications distinguished by the first part of the URL path. In this scenario, there is one ...
Indeed, the installer should not force you to create a new CM Environment in Topology Manager. If it does, that should be reported as a defect.
As a work-around, you could create a dummy CM Environment (like you did), then change the TRIDION_CM_ENVIRONMENT_ID environment variable and use Remove-TtmCmEnvironment cmdlet to get rid of the dummy thing again.
We have been working on the following simple diagram of the Topology Manager structure, to clarify a couple a things.
It is not shown, but you can have multiple CD environments per Topology (for example, you see "Staging", but you probably also have "Live").
A TopologyType can have multiple Topologies. Multiple topologies may use the same TopologyType.
The Discovery Service also acts a a centralized configuration repository for some of the other microservices (hence the term ConfigRepository in the configuration). As such, the Discovery service acts as the hub between Topology Manager and all the CD microservices.
In particular, the Content Service gets Publication URL mapping information out of the ...
I ran into this today and the solution is a little obscure:
I had to shift+right-click on my PowerShell console and choose "Run as different user" and then enter my credentials again. Yes, I logged in as myself again.
So even though I used the exact same user as when I ran it before (and who I have used successfully in the past without issues), it only ...
You should either make sure you put it all on one line - or use the backtick (`) character to continue the command on the second line. It looks like you pasted the two lines from somewhere and PowerShell intepreted them as two separate commands. The first one then failed because you didn't pass in the right credentials - and the second line failed because it ...
The only thing that really matters is that all CM Servers that are part of a logical CM Environment use the same CM Environment ID (makes sense, right?).
That is why by default the CM Environment ID is derived from the CM DB name/server (which is common for all CM servers in the same logical environment). Peter's suggestion to use the CM server name is ...
Server-relative URL is a combination of WebApplication ContextUrl and Mapping RelativeUrl properties, so if you use default root web application for you mapping you can specify
in Add-TtmMapping cmdlet
I believe this is a known defect on 8.1.1 installer, which got fixed in 8.5.
The work around involves using a different Topology Manager database for the 2nd install, then change the 2nd server to use the first one (and delete the second one).
One has to wonder though... why aren't you deploying 8.5 rather than 8.1.1?
To run the following PowerShell command to Update an existing Content Manager Environment in the Topology Manager:
Set-TtmCmEnvironment -Id <String> [-WebsiteRootUrl <String>] [-CoreServiceRootUrl <String>] [-AuthenticationType <Nullable`1[AuthenticationType]>] [-ExtensionProperties <Hashtable>] [-...
The easiest way to find out the endpoint URL is to check the Windows environment variable on the CM server using the following PowerShell command: get-item env:tridion_ttm_serviceurl
This should give a value such as: http://localhost:81/ttm201601
Here's some code that I used recently on my Tridion Sites 8.5 environment for getting the Client:
Item of type 'WebApplicationData' with id 'VisitorWeb_RootWebApp' does not exist.
Is trying to tell you there is no web application with the ID VisitorWeb_RootWebApp in the Topology Manager, so you might want to check the results of Get-TtmWebApplication and see if you didn't misspell it (case sensitivity etc.)
I found 2 very useful links one from the documentation and the other from Dominic's blog. Both of these provide details on all available cmdlets (commandlets). Dominic's blog goes a step further and explains how to get this information from available Modules. Also providing the way to look for parameters and help on these modules.
There are a few more ...
Note that publish state is not stored in Topology Manager, but in Content Manager. So, publish state is automatically copied if you restore the CM DB across environments.
As Bart mentions, this can be considered "cheating", though, because it's likely that the publish state won't reflect reality after such an action.
You should not use Topology Manager ...
Just set the Publication URL (in CM) to empty. That makes it "context-relative" instead of server-relative, meaning that there is no longer an overlap between the part of the URL managed in Topology Manager and in Content Manager.
Likewise, the "Multimedia URL" should be changed to be context-relative by ensuring it does not start with a slash (and it does ...
Please re-point the topology manager database to another database [Setup#2].
Navigate to server 2 %Tridion_Home%\TopologyManager\web
Decrypt server 2 database section in web.config
Change database settings in node in web.config
Encrypt the config file
Restart IIS [Server #2]
For more information click here and see below - How to Decrypt a web.config File
If you have multiple CM Servers in a (logical) CM Environment, you should have only one CmEnvironment entity in Topology Manager, not multiple.
In such a scaled out Environment, it is essential that all CM Servers use the same CM Environment ID. That is why you can specify a CM Environment ID in the installer and why the default value is derived from the CM ...
A Publication (or, more generically, a Repository) can act as a Site Type by setting its Publication Type to “Site Type” and setting its Key to some symbolic name.
When creating a new Site using the Site Wizard, the user has to choose a Site Type. The Site Wizard will create a new Publication for the Site and that Publication will be a child Publication of ...
If the URL of your Discovery Service changes, you can use the Set-TtmCdEnvironment cmdlet to update the URL in Topology Manager.
No need to destroy things. :-)
BTW: publish state is still stored in the CM DB, so if you would recreate the Topology Manager DB, there would not be a need to republish anything.
If you want to use OAuth authentication on your Discovery service, you firstly need to register TokenServiceCapability there. It can be done using discovery-registration.jar tool described here: link or link
This suggests an issue with the authentication between the Topology Manager and the Discovery Service. Are your -ClientID and -ClientSecret values aligned with the cmuser account within your discovery\config\cd_ambient_conf.xml file?
See the responses to SDL web8 - Issue with adding a website as well.
Your understanding seems to be quite OK.
If you want to minimize the number of DBs, you could combine the Discovery and Content Broker DBs, but I wouldn't recommend that; it's more convenient to keep your content and infrastructure info separate.
It is essential that each CD Environment has its own Discovery Service (DB).
With Topology Manager, the ...
Your problem is you cannot have two Windows Service with the same name.
You should change the $name="SDLWebDeployer" and $displayName="SDL Web Deployer" in your powershell script before installing the second Content Deployer.
You can use in Deployer2\bin folder installService.ps1.
If you have to delete some service you can use UninstallService.ps1 this ...