Resolution:
Description:
============
After deploying an application with AppManage, the user is presented with the following exception:

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2011 Oct 25 16:16:19:626 GMT -5 Error [com.tibco.administrator.command.data.application.Application] AESDKJ-0000 [main] com.tibco.pof.entity.EntityInvalidSyntaxException: Container with name &ltSERVICE_INSTANCE> already exists or has illegal characters. Please choose another name for the container that is unique and only uses alphanumeric characters, _ and -.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Environment:
===========
Operating System(s): All
TIBCO Software: TIBCO Runtime Agent

Symptoms:
========
-The application must have multiple services instances -you will be forcing a redeployment without first undeploying the application.

Example:

./appmanage -deploy -deployconfig &ltCONFIG_FILE> -ear &ltEAR_FILE> -app &ltAPP_NAME> -domain &ltDOMAIN> -user &ltUSER> -pw &ltPASSWORD> -force -serialize


Cause:
=====
All service instances in an application must be unique. This exception indicates there is a naming conflict with an existing service container.

Example:

Current deployed Application
Application
--&gtProcess Level
-----&gtHost_A Service_Instance-1
-----&gtHost_B Service_Instance-2

Attempted redeployment
Application
--&gtProcess Level
-----&gtHost_B Service_Instance-1 (Host_A is already bound to Service_Instance-1)
-----&gtHost_B Service_Instance-2

If you attempt to force a redeployment (without first undeploying) that binds Host_B to Service_instance-1  when it is already bound to Host_A, then you will receive this exception.

Resolution:
==========
Undeploy the application before running the appmanage command.

AppManage Exception - com.tibco.pof.entity.EntityInvalidSyntaxException: Container with name SERVICE_INSTANCE already exists or has illegal characters.