...
This scenario is appropriate for cases in which there is no organizational restrictions on providing users with direct access to DPOD’s IP address.
todo: change diagram to new-name
Scenario 2 : All-In-One with two network interfaces
...
Note: It is the System Administrator’s responsibility to define the second interface and make the proper static route definitions and additional network configuration. TODO: See Chapter X.X
todo: change diagram to new-name
Scenario 3 : All-In-One with External Self Service Console
...
An organization should consider using this deployment scenario when DPOD users are members of a different network to DPOD itself, or when a separation is required between the user interface and the data stored in the system.
TODO: in prod, for extra security - MESS is a second The DPOD External Self Service Console is an additional installation of DPOD. The This second one installation connects to the Regular primary DPOD. This way - developers can have access to the the external DPOD, and do not need to access through into the more-secure network, and this way we can prevent access to DataPower. The investigate+configuration is available - because this is db only.
TODO: For detailed setup instructions and requirements for the External Self Service Console deployment see Chapter X.X ALSO: Diagram Diagram is unclear. Which is the user? What is “DPOD console?” an additional login point? Need to write about this a few more lines)
todo: change diagram to new-name
...