Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 16 Oracle Analytics Lounge
- 216 Oracle Analytics News
- 43 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 79 Oracle Analytics Trainings
- 15 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
How to refrain from using IP addresses or Oracle FQDN in the configuration files for OAS
How to refrain from using IP addresses or Oracle FQDN in the various configuration files for Oracle Analytics Server?
Best Answer
-
There is no supported / documented method to change IP/hostname after an installation.
chgiphost script was deprecated.
Therefore, we will not provide a list.
In your case, the best method is to install against an internal loop back VHN/VIP, then use an external VHN/VIP that is available on the joined network, or a VHN/VIP that will be available on the joined network, once connected.
The first option allows you to start/test the software prior to connection.
Other comments, welcomed.0
Answers
-
@Narayanan Subramaniam-Oracle - There is currently no option available for dynamic configuration of hostnames during the setup process even in case of silent installation. The hostnames requested during configuration need to be provided upfront. Could you please share the business requirement and the reason behind this request?
0 -
Just out of curiosity: what would you enter in a place where a hostname or URL is expected? Are you looking at not have any parameter with those values or you look for a kind of "placeholder" that will be replaced with a hostname at some point by some kind of process?
(If your need is to clone an environment and then replace the hostname to make it work with the new URL without having to reconfigure thins, or to have a docker image that automatically does set the hostname/IP when the container started and received one, it is possible with some scripts…)
1 -
+1 to Gianni: What are you actually trying to achieve? What's the end goal? You are talking about a tiny technical detail of something that's probably a larger question / conceptual approach you're looking at nad thinking about.
0 -
I agree, that the question sounds simple, but there is likely some contextual information that needs to be answered. My guess is what Gianni is mentioning that the OP is likely trying to create a VM/container image that can be run or be replicated on multiple servers. In this case, you need to install against the localhost/IP (local loopback adapter for Windows), or virtual IP addresses/virtual hostnames that you define.
1 -
Hi All- thanks for the responses on the discussion. Please find the following details on what I wanted to achieve:
There's a requirement to join the OCI Compute VMs / DB machines to Client's Domain.
Instruction was to ensure and continue to use the Compute Instance hostnames or DB hostnames in the configuration files wherever applicable and refrain from using IP addresses or Oracle FQDN in the configuration files. Also were advised not use any entries in /etc/hosts file, unless absolutely necessary.
So basically I was looking for the list of files in OAS where all occurrences of IP/Oracle FQDN if any ,can be replaced with hostnames.
Regards,
Narayanan
0 -
As Steve said it isn't supported as a "click here to change hostname/ip/FQDN".
If you read through various MOS documents you have the process to change a number of things.
You are free to do a full search in the domain folder for any file containing the original hostname/ip/FQDN, to understand what they do in there, to change things following the various MOS documents, and to see how those files changed.
From there, if you are still motivated, you can write a single script doing all that automatically.
Will it work? Sure, been there, done that.
Is it clean and fully supported? I doubt, because it's difficult (impossible) to exclude side effect on the medium term.
I did it for an automated CI/CD pipeline that was testing OAS developments spinning up OAS instances on the fly with docker: the only way to have a fast starting OAS docker container is to have it pre-configured, because the configuration take a long time. Therefore running a script to adapt the IP/hostname based on the values of the container of a pre-configured OAS, is the only way to have an acceptable start time.
But I wouldn't do it for a real environment that isn't killed after running the various tests in minutes or hours at most.
1
