Let's Reconnect, thank you for making 2022 our best year yet.

Look Back
Internal Urls Management — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Internal Urls Management

Received Response
8
Views
4
Comments
edited Jul 21, 2018 2:49PM in Oracle Cloud Infrastructure - General 4 comments

Summary

Best practices managing internal urls such as weblogic console url.

Content

Hi

I am new in this OCI world. I was wondering what would happen in an OCI environment with no connection to customer VPN. In case we have products running like weblogic(http://ip:port/console), atg or endeca, with internal urls (only accessible by internal users), how that would be managed?

 

I have found some documentation for the DBs. We can use the sqlDeveloper to connect through the public IP to the database using port forwarding but I don't know the good practices for Weblogic. Should we use the public IP as well?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!