-redeploy

Redeploys the orchestrations from the process apps that are deployed to a particular environment. It does this by retrieving the environment's deployed process apps from the environment's Application Engine server, and then retrieving the target server and endpoint configuration from the environment. For each process app, it redeploys the orchestration workflows to the target Orchestration Engine, fixing the various endpoints consumed by those workflows.

You can run this command multiple times against an environment, even if you did not run renew -clear earlier. It will simply redeploy the orchestration definitions deployed to the environment and cached by the Application Engine to the Orchestration Engine, creating a new internal version within the Orchestration Engine. Running renew -redeploy does not affect the deployment records that Application Repository keeps.

Example output with overlapping environments, without the -nowarning option:

java -Dfile.encoding=UTF-8 -jar renew.jar -redeploy -environment "Default Environment" 
-username "admin" -password "password" -arAddress "http://localhost:8085"

WARNING: Target servers shared across environments.  
         Using renew with this configuration requires special care !!!
         DO NOT PROCEED WITHOUT READING THE DOCUMENTATION.

DS, [JBPM_BPEL->http://localhost:8085] used by : [Default Environment][clone1][clone 2]                                       
DS, [ALF->http://localhost:8085] used by : [Default Environment][clone1][clone 2]                                           
AE, [AE->http://localhost:80/gsoap/gsoap_ssl.dll?sbminternalservices72] used by :
[Default Environment][clone1][clone 2] 

WARNING: Are you sure? [Y/N]:y
Redeploying orchestrations ...

AAS_TEST_1 :
    AAS_One : Deployed
    AAS_SYNC_1 : Deployed
AAS_TEST_1 : Deployed

Change Approval Requests :
    CAR : Deployed
Change Approval Requests : Deployed

Incident Management :
    IncidentOrchestration : Deployed
Incident Management : Deployed

Issue Defect Management :
    IDMOrchestrations : Deployed
Issue Defect Management : Deployed

OeOnly:
    OeOnlyOrch : Deloyed
OeOnly : Deployed

OrchestrationTest :
    SynchOrch : Deployed
    TestOrch : Deployed
OrchestrationTest : Deployed
Done.

Example output with the -nowarning option:

java -Dfile.encoding=UTF-8 -jar rewnew.jar -redeploy -environment "Default Environment" 
-nowarning -username "admin" -password "password" -
arAddress "http://localhost:8085"
Redeploying orchestrations ...

AAS_TEST_1 :
    AAS_One : Deployed
    AAS_SYNC_1 : Deployed
AAS_TEST_1 : Deployed
Change Approval Requests :
    CAR : Deployed
Change Approval Requests: Deployed

Incident Management :
    IncidentOrchestration : Deployed
Incident Management : Deployed

Issue Defect Management :
    IDMOrchestrations : Deployed
Issue Defect Management: Deployed

OrchestrationTest :
    SynchOrch : Deployed
    TestOrch : Deployed
OrchestrationTest : Deployed
Done.

You can also run the redeploy command with the following options:

• -redeployInFile
• -failOutputFile
• -eventmap
• -useEnvEndpoints

The -redeployInFile option has an argument which is an input file that contains a list of apps, users, and environments that need to be redeployed.

File example (redeploy.xml):

<RedeployList>
	<User name="admin">
		<Environment name="Dev Environment" />
		<Environment name="QA Environment">
			<ProcessApp>QuickTest</ProcessApp>
		</Environment>
	</User>
</RedeployList>

Example:

java -Dfile.encoding=UTF-8 -jar renew.jar -redeploy -username "admin" 
-password "password" -redeployInFile "redeploy.xml"

In this example, the redeploy is performed for all apps in the Dev Environment and the QuickTest app in the QA Environment.

The -failOutputFile option has an argument that outputs a file for failed apps, users, and environments. This output file has the same structure as -redeployInFile.

Example:

java -Dfile.encoding=UTF-8 -jar renew.jar -redeploy -username "admin"
 -password "password" –failOutputFile "failOutput.xml"

You can include the -eventmap option to redeploy event maps for deployed applications.

Example:

java -Dfile.encoding=UTF-8 -jar renew.jar -redeploy -username "admin" 
-password "password" -eventmap

You can use the -eventmap option in the event that target servers have been changed in an environment in which the Event Manager and BPEL Engine components are hosted on separate machines. When you use the -eventmap option, data for both the Event Manager and BPEL Engine is redeployed.

This is usually not required, but it can be useful in the event that data becomes obsolete. For example, if the host name is changed for either server, the event map must be redeployed.

You can use the -useEnvEndpoints option in the event that endpoints were manually changed in Application Repository after the last deploy.

Example:

java -Dfile.encoding=UTF-8 -jar renew.jar -redeploy -username "admin" 
-password "password" -useEnvEndpoints

This is not required, but it can be useful in the event the endpoints have changed. For example, if the endpoints were changed in Application Repository, this option ensures that after the redeploy, any endpoints for Application Engine Web service calls that are made from an orchestration are current.