File Connector Guide > File Event Sources > Event Source Endpoints
  

Event Source Endpoints

Each event source you define must have an endpoint that is unique both within the connection and among all published connections in the organization. You can view the endpoints for a connection in the Details area of the Design Home page. When you define connections, the Process Designer validates that these endpoints are unique to avoid a URI conflict. A URI conflict might otherwise occur, even for different event source types. A delimited content parser and file monitor, for example, could both use the same URI to monitor files (file:*) or to write content (ftp:*).
If a conflict is detected when you attempt to publish an event source, you can change the value for a single attribute to make the URIs unique and resolve the conflict. For example, the different poll interval delay shown in these URIs is sufficient:
file://D:%5Ccamel_test%5Cfile%5Csource?copyAndDeleteOnRenameFail=false&delay=1000&delete=false&initialDelay=1000&maxMessagesPerPoll=0&move=.done&moveFailed
file://D:%5Ccamel_test%5Cfile%5Csource?copyAndDeleteOnRenameFail=false&delay=2000&delete=false&initialDelay=1000&maxMessagesPerPoll=0&move=.done&moveFailed