移除OBIEE的HTTPS并切换为HTTP,需调整Oracle Traffic Director吗?
Absolutely, you do need to adjust configurations in Oracle Traffic Director (OTD) since it's your front-end load balancer handling all incoming traffic to OBIEE. Here's a step-by-step guide tailored for someone new to OTD:
1. Modify OTD's Listener Configuration
OTD uses listeners to accept incoming traffic. You'll need to either update your existing HTTPS listener to HTTP or create a new HTTP listener, then disable/remove the HTTPS one:
- Option 1: Use OTD Admin Console
- Log into the OTD management console (usually at
http://otd-host:8989by default) - Navigate to your OTD configuration, go to Listeners
- Delete the existing HTTPS listener (e.g., named
https-listener-1) - Click New to create an HTTP listener: set port to
80(or your preferred HTTP port), enter your server/domain name, and leave SSL options unchecked
- Log into the OTD management console (usually at
- Option 2: Edit Configuration Files Directly
- Locate your OTD config file (typically at
OTD_INSTANCE/config/server.xml) - Remove or comment out the HTTPS listener block that looks like this:
<listener> <name>https-listener-1</name> <port>443</port> <server-name>your-obiee-domain.com</server-name> <ssl>true</ssl> <cert-nickname>your-ssl-cert</cert-nickname> </listener> - Add a new HTTP listener block:
<listener> <name>http-listener-1</name> <port>80</port> <server-name>your-obiee-domain.com</server-name> </listener>
- Locate your OTD config file (typically at
2. Update OTD Routing Rules
Make sure OTD routes incoming HTTP traffic to your OBIEE backend servers over HTTP (not HTTPS):
- In the OTD console, go to Routes
- Find the route pointing to OBIEE (usually named something like
obiee-route) - Update the Target URLs to use
http://instead ofhttps://(e.g.,http://obiee-server-1:9704,http://obiee-server-2:9704) - If editing config files directly, check the
<route>node inserver.xmlto ensure the<target>uses HTTP
3. Adjust OBIEE's Frontend URL
OBIEE might still reference the old HTTPS URL in its UI components, so you need to update this:
- Log into the OBIEE Enterprise Manager (EM) console
- Navigate to your WebLogic Domain > OBIEE Instance > Configuration > General
- Update the Frontend URL to your new HTTP address (e.g.,
http://your-otd-host:80/analytics) - Restart OBIEE services (Presentation Services, Analytics Server) for changes to take effect
4. Clean Up and Validate
- Remove HTTPS redirects: If OTD had any rules forcing HTTP to HTTPS (check
<redirect>blocks inserver.xml), delete them to avoid unexpected redirects - Restart OTD: Use the command
tadm restart-config --config=your-config-name(or restart via the console) - Test access: Visit
http://your-otd-host/analyticsand verify the page loads correctly, with all resources (images, scripts) loading over HTTP (check browser dev tools for mixed content errors) - Check logs: Review OTD's access logs (in
OTD_INSTANCE/logs/access.log) to confirm all incoming requests are using HTTP
Key Notes
- Ensure your firewall allows traffic on OTD's HTTP port (80) and blocks the old HTTPS port (443) if it's no longer needed
- If your OBIEE backend (WebLogic) was configured to require HTTPS, you'll need to adjust WebLogic's security settings to allow HTTP connections
内容的提问来源于stack exchange,提问作者Shiva Laveti
相关产品推荐
相关产品推荐

