Date: Thu, 28 Mar 2024 10:14:34 +0000 (UTC) Message-ID: <1049566508.19.1711620874989@de34f3ce8cb6> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_18_344782843.1711620874989" ------=_Part_18_344782843.1711620874989 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Various files (source, configuration, test files etc.) can be se= tup for property replacement. FlexDeploy will perform string replacement wi= th appropriate values based on project and deploy environment properties. Y= ou can use propertyReplacementArtifacts<= /a> operation of File plugin, but in many cases specific plugin operation w= ill automatically perform property replacement. Refer plugin documentation = for property replacement support. Replacement properties must be defined us= ing following syntax.
${{PROPERTY_NAME}}
for project properties or current =
instance properties.${{INSTANCE:PROPERTY_NAME}}
for specific instance pro=
perties.Property names can be custom or defined by plugins. For example, to repl=
ace WebLogic installation folder you can use ${{FDWLS_WEBLOGIC_HOME}}=
which is defined by FlexDeploy WebLogic plugin. But if you want to =
replace something like URL to internal service, you can define something li=
ke MYCOMPANY_PAYMENT_SERVICE_URL
on workflow as defined in Creating a Workflow and use it in your file as =
${{MYCOMPANY_PAYMENT_SERVICE_URL}}
. Defining custom property i=
s entirely up to your implementation. For example, you can just define some=
prefix or suffix that changes through environments as a custom property in=
stead of defining entire URL value.
Property replacement allows various plugin operations to perform deploym= ent to many environments using same artifact files.
For example, if your file contains string like
http://${{FDSOA_SERVER_HOST}}
:
then during deployment to Development it will be updated as
http://devhost= :8001/soa-infra/services/default/CalledProcess!1.0/calledprocess_client_ep?WSD= L
and during deployment to QA it will be updated as
http://qahost:9001/=
soa-infra/services/default/CalledProcess!1.0/calledprocess_client_ep?WSDL=
p>
Above example is based assumption that Development environment values ar=
e devhost =
and 8001 w=
hereas QA environment values are qahost9001. And you would have defined two properties FDSOA_SERVER_HOST
and FDSOA_SERVER_PORT
on your workfl=
ow as Environment Instance scope.