Page Comparison

Your source files can be configured with a Replacement Property, which are then replaced (using Plugin operations) with target deployment environment properties. 
Replacement properties are defined by using following syntax within your artifacts:Various files (source, configuration, test files etc.) can be setup for property replacement. FlexDeploy will perform string replacement with appropriate values based on project and deploy environment properties. You can use propertyReplacementArtifacts operation of File plugin, but in many cases, plugin operations automatically perform property replacement. Refer to the plugin documentation for property replacement support. Replacement properties must be defined using following syntax.

• ${{PROPERTY_NAME}} for project properties or

  current instance

  target properties.

• ${{INSTANCE:PROPERTY_NAME}} for specific

  instance

  target group properties.

Property names can be any property that is defined in this guide.

With this one-time setup, the various plugin operations will utilize the properties that are configured within FlexDeploy and allow deployment to any environment without manual changes to the files each time it is built for a different environment.

...

Or

This url would look like this before replacement properties are added:custom or defined by plugins. For example, to replace 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 like 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 properties are entirely up to your implementation. For example, you can just define some prefix or suffix that changes through environments as a custom property instead of defining entire URL value.

Property replacement allows various plugin operations to perform deployment to many environments using the same artifact files.

For example, if your file contains a string like

http://${{FDSOA_SERVER_HOST}}:${{FDSOA_SERVER_PORT}}/soa-infra/services/default/CalledProcess!1.0/calledprocess_client_ep?WSDL

then during deployment to Development it will be updated as

http://devhost:8001/soa-infra/services/default/CalledProcess!1.0/calledprocess_client_ep?WSDLwould look like this after:

and during deployment to QA it will be updated as

http://

...

qahost:9001/soa-infra/services/default/CalledProcess!1.0/calledprocess_client_ep?WSDL

Above example is based assumption that Development environment values are devhostand 8001whereas QA environment values are qahostand 9001. And you would have defined two properties FDSOA_SERVER_HOST and FDSOA_SERVER_PORT on your workflow as Target scope. Many properties are defined by plugins.