CD microservices installation for LIVE and STAGING targets
I want to set up CD instance for two targets in Tridion Topology Manager - Live & Staging.
As I understand I need to install CD services both for Live & Staging (as a result I will have pairs at least of the following microservices: discovery context, deployer). I will also have Session Preview and Session Content for Stagindg and Content microservice for Live target.
The question is how to set up with powershell different port numbers for pairs of services (discovery context, deployer)? Should I edit the scripts for installation of each target or there are parameters that allow to install without editing scripts?
content-delivery powershell microservices
add a comment |
I want to set up CD instance for two targets in Tridion Topology Manager - Live & Staging.
As I understand I need to install CD services both for Live & Staging (as a result I will have pairs at least of the following microservices: discovery context, deployer). I will also have Session Preview and Session Content for Stagindg and Content microservice for Live target.
The question is how to set up with powershell different port numbers for pairs of services (discovery context, deployer)? Should I edit the scripts for installation of each target or there are parameters that allow to install without editing scripts?
content-delivery powershell microservices
add a comment |
I want to set up CD instance for two targets in Tridion Topology Manager - Live & Staging.
As I understand I need to install CD services both for Live & Staging (as a result I will have pairs at least of the following microservices: discovery context, deployer). I will also have Session Preview and Session Content for Stagindg and Content microservice for Live target.
The question is how to set up with powershell different port numbers for pairs of services (discovery context, deployer)? Should I edit the scripts for installation of each target or there are parameters that allow to install without editing scripts?
content-delivery powershell microservices
I want to set up CD instance for two targets in Tridion Topology Manager - Live & Staging.
As I understand I need to install CD services both for Live & Staging (as a result I will have pairs at least of the following microservices: discovery context, deployer). I will also have Session Preview and Session Content for Stagindg and Content microservice for Live target.
The question is how to set up with powershell different port numbers for pairs of services (discovery context, deployer)? Should I edit the scripts for installation of each target or there are parameters that allow to install without editing scripts?
content-delivery powershell microservices
content-delivery powershell microservices
asked Aug 27 '18 at 9:19
Vitali S.Vitali S.
536
536
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Yes, You need to edit the scripts for all services and update the following variables $name, $displayName, $description, $serverPort.
We also need to update $dependsOn variable while registering services with Discovery Service.
While update Port number ensure that assign only Unused port numbers, it should not conflict with other services.
So, am I right that I should edit the following installation script e.g. discovery: SDL Web 8.5Content DeliveryrolesdeployerdeployerstandalonebininstallService.ps1
– Vitali S.
Aug 27 '18 at 9:42
Yes, You are right
– Prasanna K Gollamudi
Aug 27 '18 at 9:43
So is it a possible way to change needed installation scripts for needed services and then install with 'quickinstall.ps1' for Live target. Then repeat these steps for Staging target. Should this work?
– Vitali S.
Aug 27 '18 at 10:12
add a comment |
Avoid editing the scripts unless you really run into something that cannot be set with a parameter. You should be able to pass in parameters for everything, though.
Some common parameters:
--Name lets you set the short name of the service.
--DisplayName lets you set the user-friendly name (visible in the Services list)
--Description lets you set the description of the service
--DependsOn will have the service depend on another service (most commonly the Discovery Service for that instance). Note that this only makes sense if both services are running on the same machine.
--server.port lets you set the port the service will run on.
-Dprop=value lets you specify any number of JVM options and variables used within configuration files (e.g. -Ddbname=UDP_Broker_Staging will change the database name to UDP_Broker_Staging)
For example:
.installService.ps1 --DisplayName="UDP Content Service (Staging)" --Name="UDPContentServiceStaging" --DependsOn="UDPDiscoveryServiceStaging" --server.port="9081"
1
I usually create a separate script that calls installService.ps1 with parameters. For an example of powershell code that generates such a script see: github.com/TridionPractice/autoInstall/blob/master/…
– Dominic Cronin
Aug 28 '18 at 13:53
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "485"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftridion.stackexchange.com%2fquestions%2f19241%2fcd-microservices-installation-for-live-and-staging-targets%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Yes, You need to edit the scripts for all services and update the following variables $name, $displayName, $description, $serverPort.
We also need to update $dependsOn variable while registering services with Discovery Service.
While update Port number ensure that assign only Unused port numbers, it should not conflict with other services.
So, am I right that I should edit the following installation script e.g. discovery: SDL Web 8.5Content DeliveryrolesdeployerdeployerstandalonebininstallService.ps1
– Vitali S.
Aug 27 '18 at 9:42
Yes, You are right
– Prasanna K Gollamudi
Aug 27 '18 at 9:43
So is it a possible way to change needed installation scripts for needed services and then install with 'quickinstall.ps1' for Live target. Then repeat these steps for Staging target. Should this work?
– Vitali S.
Aug 27 '18 at 10:12
add a comment |
Yes, You need to edit the scripts for all services and update the following variables $name, $displayName, $description, $serverPort.
We also need to update $dependsOn variable while registering services with Discovery Service.
While update Port number ensure that assign only Unused port numbers, it should not conflict with other services.
So, am I right that I should edit the following installation script e.g. discovery: SDL Web 8.5Content DeliveryrolesdeployerdeployerstandalonebininstallService.ps1
– Vitali S.
Aug 27 '18 at 9:42
Yes, You are right
– Prasanna K Gollamudi
Aug 27 '18 at 9:43
So is it a possible way to change needed installation scripts for needed services and then install with 'quickinstall.ps1' for Live target. Then repeat these steps for Staging target. Should this work?
– Vitali S.
Aug 27 '18 at 10:12
add a comment |
Yes, You need to edit the scripts for all services and update the following variables $name, $displayName, $description, $serverPort.
We also need to update $dependsOn variable while registering services with Discovery Service.
While update Port number ensure that assign only Unused port numbers, it should not conflict with other services.
Yes, You need to edit the scripts for all services and update the following variables $name, $displayName, $description, $serverPort.
We also need to update $dependsOn variable while registering services with Discovery Service.
While update Port number ensure that assign only Unused port numbers, it should not conflict with other services.
answered Aug 27 '18 at 9:38
Prasanna K GollamudiPrasanna K Gollamudi
411313
411313
So, am I right that I should edit the following installation script e.g. discovery: SDL Web 8.5Content DeliveryrolesdeployerdeployerstandalonebininstallService.ps1
– Vitali S.
Aug 27 '18 at 9:42
Yes, You are right
– Prasanna K Gollamudi
Aug 27 '18 at 9:43
So is it a possible way to change needed installation scripts for needed services and then install with 'quickinstall.ps1' for Live target. Then repeat these steps for Staging target. Should this work?
– Vitali S.
Aug 27 '18 at 10:12
add a comment |
So, am I right that I should edit the following installation script e.g. discovery: SDL Web 8.5Content DeliveryrolesdeployerdeployerstandalonebininstallService.ps1
– Vitali S.
Aug 27 '18 at 9:42
Yes, You are right
– Prasanna K Gollamudi
Aug 27 '18 at 9:43
So is it a possible way to change needed installation scripts for needed services and then install with 'quickinstall.ps1' for Live target. Then repeat these steps for Staging target. Should this work?
– Vitali S.
Aug 27 '18 at 10:12
So, am I right that I should edit the following installation script e.g. discovery: SDL Web 8.5Content DeliveryrolesdeployerdeployerstandalonebininstallService.ps1
– Vitali S.
Aug 27 '18 at 9:42
So, am I right that I should edit the following installation script e.g. discovery: SDL Web 8.5Content DeliveryrolesdeployerdeployerstandalonebininstallService.ps1
– Vitali S.
Aug 27 '18 at 9:42
Yes, You are right
– Prasanna K Gollamudi
Aug 27 '18 at 9:43
Yes, You are right
– Prasanna K Gollamudi
Aug 27 '18 at 9:43
So is it a possible way to change needed installation scripts for needed services and then install with 'quickinstall.ps1' for Live target. Then repeat these steps for Staging target. Should this work?
– Vitali S.
Aug 27 '18 at 10:12
So is it a possible way to change needed installation scripts for needed services and then install with 'quickinstall.ps1' for Live target. Then repeat these steps for Staging target. Should this work?
– Vitali S.
Aug 27 '18 at 10:12
add a comment |
Avoid editing the scripts unless you really run into something that cannot be set with a parameter. You should be able to pass in parameters for everything, though.
Some common parameters:
--Name lets you set the short name of the service.
--DisplayName lets you set the user-friendly name (visible in the Services list)
--Description lets you set the description of the service
--DependsOn will have the service depend on another service (most commonly the Discovery Service for that instance). Note that this only makes sense if both services are running on the same machine.
--server.port lets you set the port the service will run on.
-Dprop=value lets you specify any number of JVM options and variables used within configuration files (e.g. -Ddbname=UDP_Broker_Staging will change the database name to UDP_Broker_Staging)
For example:
.installService.ps1 --DisplayName="UDP Content Service (Staging)" --Name="UDPContentServiceStaging" --DependsOn="UDPDiscoveryServiceStaging" --server.port="9081"
1
I usually create a separate script that calls installService.ps1 with parameters. For an example of powershell code that generates such a script see: github.com/TridionPractice/autoInstall/blob/master/…
– Dominic Cronin
Aug 28 '18 at 13:53
add a comment |
Avoid editing the scripts unless you really run into something that cannot be set with a parameter. You should be able to pass in parameters for everything, though.
Some common parameters:
--Name lets you set the short name of the service.
--DisplayName lets you set the user-friendly name (visible in the Services list)
--Description lets you set the description of the service
--DependsOn will have the service depend on another service (most commonly the Discovery Service for that instance). Note that this only makes sense if both services are running on the same machine.
--server.port lets you set the port the service will run on.
-Dprop=value lets you specify any number of JVM options and variables used within configuration files (e.g. -Ddbname=UDP_Broker_Staging will change the database name to UDP_Broker_Staging)
For example:
.installService.ps1 --DisplayName="UDP Content Service (Staging)" --Name="UDPContentServiceStaging" --DependsOn="UDPDiscoveryServiceStaging" --server.port="9081"
1
I usually create a separate script that calls installService.ps1 with parameters. For an example of powershell code that generates such a script see: github.com/TridionPractice/autoInstall/blob/master/…
– Dominic Cronin
Aug 28 '18 at 13:53
add a comment |
Avoid editing the scripts unless you really run into something that cannot be set with a parameter. You should be able to pass in parameters for everything, though.
Some common parameters:
--Name lets you set the short name of the service.
--DisplayName lets you set the user-friendly name (visible in the Services list)
--Description lets you set the description of the service
--DependsOn will have the service depend on another service (most commonly the Discovery Service for that instance). Note that this only makes sense if both services are running on the same machine.
--server.port lets you set the port the service will run on.
-Dprop=value lets you specify any number of JVM options and variables used within configuration files (e.g. -Ddbname=UDP_Broker_Staging will change the database name to UDP_Broker_Staging)
For example:
.installService.ps1 --DisplayName="UDP Content Service (Staging)" --Name="UDPContentServiceStaging" --DependsOn="UDPDiscoveryServiceStaging" --server.port="9081"
Avoid editing the scripts unless you really run into something that cannot be set with a parameter. You should be able to pass in parameters for everything, though.
Some common parameters:
--Name lets you set the short name of the service.
--DisplayName lets you set the user-friendly name (visible in the Services list)
--Description lets you set the description of the service
--DependsOn will have the service depend on another service (most commonly the Discovery Service for that instance). Note that this only makes sense if both services are running on the same machine.
--server.port lets you set the port the service will run on.
-Dprop=value lets you specify any number of JVM options and variables used within configuration files (e.g. -Ddbname=UDP_Broker_Staging will change the database name to UDP_Broker_Staging)
For example:
.installService.ps1 --DisplayName="UDP Content Service (Staging)" --Name="UDPContentServiceStaging" --DependsOn="UDPDiscoveryServiceStaging" --server.port="9081"
edited Aug 27 '18 at 14:46
answered Aug 27 '18 at 14:38
Peter KjaerPeter Kjaer
19.4k11753
19.4k11753
1
I usually create a separate script that calls installService.ps1 with parameters. For an example of powershell code that generates such a script see: github.com/TridionPractice/autoInstall/blob/master/…
– Dominic Cronin
Aug 28 '18 at 13:53
add a comment |
1
I usually create a separate script that calls installService.ps1 with parameters. For an example of powershell code that generates such a script see: github.com/TridionPractice/autoInstall/blob/master/…
– Dominic Cronin
Aug 28 '18 at 13:53
1
1
I usually create a separate script that calls installService.ps1 with parameters. For an example of powershell code that generates such a script see: github.com/TridionPractice/autoInstall/blob/master/…
– Dominic Cronin
Aug 28 '18 at 13:53
I usually create a separate script that calls installService.ps1 with parameters. For an example of powershell code that generates such a script see: github.com/TridionPractice/autoInstall/blob/master/…
– Dominic Cronin
Aug 28 '18 at 13:53
add a comment |
Thanks for contributing an answer to Tridion Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftridion.stackexchange.com%2fquestions%2f19241%2fcd-microservices-installation-for-live-and-staging-targets%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown