Skip to content

Commit 3a74049

Browse files
s1saurabhpsaini79
andauthored
cman README files (#2963)
Co-authored-by: Param Saini <[email protected]>
1 parent 73fc6a2 commit 3a74049

File tree

1 file changed

+10
-5
lines changed
  • OracleDatabase/OracleConnectionManager

1 file changed

+10
-5
lines changed

OracleDatabase/OracleConnectionManager/README.md

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -36,8 +36,8 @@ You can also deploy Oracle Connection Manager on Podman using the pre-built imag
3636

3737
Example of pulling an Oracle Connection Manager Image from the Oracle Container Registry:
3838
```bash
39-
podman pull container-registry.oracle.com/database/cman:23.5.0.0
40-
podman tag container-registry.oracle.com/database/cman:23.5.0.0 localhost/oracle/client-cman:23.5.0
39+
podman pull container-registry.oracle.com/database/cman:23.7.0.0
40+
podman tag container-registry.oracle.com/database/cman:23.7.0.0 localhost/oracle/client-cman:latest
4141
```
4242

4343
If you are using pre-built Oracle Connection Manager from [the Oracle Container Registry](https://container-registry.oracle.com), then you can skip the section [Create Oracle Connection Manager Image](#create-oracle-connection-manager-image) to build the Oracle Connection Manager Image.
@@ -66,6 +66,12 @@ Note:
6666
-o: passes on container build option (e.g., --build-arg ARGUMENT=value).
6767
```
6868
- If you are behind a proxy wall, then you must set the `https_proxy` or `http_proxy` environment variable based on your environment before building the image.
69+
70+
Once image is built, retag it to latest as we are going to refer latest image in podman run command-
71+
```bash
72+
podman tag localhost/oracle/client-cman:23.5.0 localhost/oracle/client-cman:latest
73+
```
74+
6975
## Create Network Bridge
7076
**Note:** You can change subnet according to your environment.
7177

@@ -106,11 +112,10 @@ To create the connection manager container, run the following command as the roo
106112
-e PUBLIC_IP=10.0.20.166 \
107113
-e DNS_SERVER=10.0.20.25 \
108114
-e PUBLIC_HOSTNAME=racnodepc1-cman \
109-
-e DB_HOSTDETAILS="HOST=racnodepc1-scan:RULE_ACT=accept,HOST=racnodep1:IP=10.0.20.170" \
110115
--privileged=false \
111116
-p 1521:1521 \
112117
--name racnodepc1-cman \
113-
oracle/client-cman:23.5.0
118+
oracle/client-cman:latest
114119
```
115120

116121
### Create Oracle Connection Manager Container using `cman.ora`
@@ -178,7 +183,7 @@ Run this command inside the OracleConnectionManager container.
178183
| DOMAIN | The domain name associated with the container environment. |
179184
| PUBLIC_IP | The public IP address assigned to the Oracle Connection Manager container. |
180185
| PUBLIC_HOSTNAME | The public hostname assigned to the Oracle Connection Manager container. |
181-
| DB_HOSTDETAILS | Details regarding the database host configuration, including host names, rules, and IP addresses to be registered with Connection manager in a command separated format, indicating different hosts and their associated details such as rules and IP addresses. Example: `HOST=racnodepc1-scan:RULE_ACT=accept,HOST=racnodep1:IP=10.0.20.170`. |
186+
| DB_HOSTDETAILS | This is optional field. Details regarding the database host configuration, including host names, rules, and IP addresses to be registered with Connection manager in a command separated format, indicating different hosts and their associated details such as rules and IP addresses. Example: `HOST=racnodepc1-scan:RULE_ACT=accept,HOST=racnodep1:IP=10.0.20.170`. |
182187
| DNS_SERVER | The default is set to `10.0.20.25`, which is the DNS container resolving the Connection Manager and Oracle Database containers. Replace this with your DNS server IP if needed. |
183188
| USER_CMAN_FILE | (Optional) If you want to provide your own pre-created `cman.ora` file, set this environment variable and attach the file as a Podman volume in the `podman run` command. |
184189

0 commit comments

Comments
 (0)