Externalize Secure Agent configurations so that those can be persisted and re-use

• Add instructions on how to mount various configurations for Secure Agent so those can be re-used.
• Updated README.md with descriptions on how to mount volumes.
• Documented various ports in Secure Agents.
• Fixed punctuations.

@ERIC.SCHOVILLE @JARED.KOSANOVIC

README.md

 # IICS Secure Agent Docker Image
 
 ## Description
-
 This project was forked from [jbrazda/ic-sagent-docker|https://github.com/jbrazda/ic-sagent-docker] with the intention of containerizing the IICS Secure Agent to run in Amazon Web Services.  As of early January 2019, there is no official Docker image for IICS Secure Agent.
 
 ## Requirements
-
 * Docker.
 * An IICS user account and password for your organization that has appropriate rights to create and manage secure agents.  This user will be used to login to the Informatica APIs to register the agent.
 * Your Informatica POD and REGION, which can be inferred from https://${POD}.${REGION}.informaticacloud.com/.  Defaults are set to POD=usw3 and REGION=dm-us, but can be overriden with Docker environment variables.
 
-## The image
-
+## The Image
 The image is based on Ubuntu 18.04.  It downloads and installs necessary dependencies, and then downloads the installer file from the correct Informatica URL based on your POD and REGION.
 
 1. Clone this repository.
-2. `docker build . -t secure-agent` - optionally pass --build-arg parameters for POD and REGION if the defaults are not correct.  POD and REGION are also set as environment variables, because containers will use these values for communicating with the Informatica API.
+2. `docker build . -t iics_secure_agent:latest` - optionally pass --build-arg parameters for POD and REGION if the defaults are not correct.  POD and REGION are also set as environment variables, because containers will use these values for communicating with the Informatica API.
 
 ## Containers
-
 The container executes a bash script called run_agent.sh upon start.  It needs INFORMATICA_USER and INFORMATICA_PASSWORD environment variables set during runtime in order to communicate with the Informatica API to check and register the Secure Agent.
 
-### Environment variables
-
+### Environment Variables
 * INFORMATICA_USER (required) - User that can run the agent and access Informatica APIs
 * INFORMATICA_PASSWORD (required) - Password for above credential.  Used for API access only.
 * JSON_LOG (optional) - If this is set, then the log output will be in JSON format.
 
 ### Externalized Configurations
-Secure Agent's configurations can be externalized using Docker [volumes](https://docs.docker.com/storage/volumes/). 
+Secure Agent's configurations can be externalized using Docker [volumes](https://docs.docker.com/storage/volumes/). Following 
 Secure Agent's directories and files can be externalized for containers. Note that after initial 
 container startup, these configurations can be used to start subsequent containers.  
 
@@ -86,13 +81,13 @@ $ docker run -d \
 ```  
 
 ### Monitoring
-If volume mapping is not used use `docker exec` to attach to the running container.
+If volume mapping is not used use `docke exec` to attach to the running container.
 
 ```shell
 docker exec -it <container_name> less agentCore.log
 ```
 
-## Hardware requirements
+## Hardware Requirements
 Minimum Hardware Specs ([reference](https://network.informatica.com/servlet/JiveServlet/download/189174-25674/Informatica%20Cloud%20Secure%20Agent%20Minimum%20Requirements.pdf)):
 * Windows version 7 (32-bit or 64-bit) or Windows XP Pro SP2/SP3 (32-bit).
 * Linux (32-bit or 64-bit).
@@ -104,9 +99,17 @@ Minimum Hardware Specs ([reference](https://network.informatica.com/servlet/Jive
 * 1 GB Network connectivity (faster the better as this will most likely the bottleneck).
 
 ## Known Issues
-
 * Doesn't seem to be able to run in host network mode because it won't be able to talk to internal ports.  It would probably work if you expose those ports.
 
+## Enterprise Integration Secure Agent
+Secure Agent containers are deployed in following tiers in interop/AWS account. This deployment is automated through Terraform (see below section on Terraform).
+
+| environment| tier        |
+| -----------|-------------|
+| test      | us-east-1(N. Virginia)|
+| prod      | us-east-2(Ohio)|
+
+
 ## Terraform
 * Infrastructure is available as code in terraform. 
 * Before disposing and create a new instance of Informatica Secure Agent, existing live connections to various targets(for e.g. databases)