@@ -2,7 +2,11 @@ Example of docker images with WebLogic server in MSI Mode
2
2
=========================================================
3
3
This Dockerfile extends the Oracle WebLogic image by creating a domain that configures a managed
4
4
server in MSI mode (or Managed Server Independence mode). In this mode, a managed server can run
5
- without the need of an admin server
5
+ without the need of an admin server. Such a managed server is not driven by admin server for
6
+ configuration or deployment changes. However, it can handle all configuration and deploymnets
7
+ already in config.xml like any other managed server. For use cases where the managed server does
8
+ not need to be updated for configuration or deployments, this image can be used by itself without
9
+ running a admin server or node manager
6
10
7
11
How to build and run the base image
8
12
-----------------------------------
@@ -36,15 +40,32 @@ deployed to it yet. When additional images are created by adding application(s)
36
40
the same command (as above) may be used to launch the server and accessed using the URL
37
41
http://localhost:8011/ <relevant-context-root >
38
42
39
- Randomly generated managed server name can both be overridden using environment variable.
40
- For example, the following command may be used to run a managed server with name ms1
43
+ Randomly generated managed server name can be overridden using build arguments or runtime variables.
44
+
45
+ ** Build Argument ms_name_prefix**
46
+ This argument may be used to alter the prefix of managed server name, and a random
47
+ number prefix is appended to it. For example, the following command may be used to
48
+ run a managed with a name managedServer<RandomNumber >
41
49
42
- docker run --name msiserver --env MS_NAME=ms1 12212-msiserver
50
+ docker build -t 12212- msiserver --build-arg ms_name_prefix=managedServer .
43
51
52
+ ** Build Argument number_of_ms**
44
53
By default, this image comes configured with 10 managed servers, ms1 to ms10. However, the image
45
54
can be built with configurable number of managed servers using NUMBER_OF_MS argument
46
55
47
- docker build -t 12212-msiserver --build-arg NUMBER_OF_MS=15 .
56
+ docker build -t 12212-msiserver --build-arg number_of_ms=15 .
57
+
58
+ ** Other build arguments**
59
+ * domain_name may be used to identify the name of generated domain that gets packed into MSI image. Default value msi-sample
60
+ * domains_dir may be used identify the directory under $ORACLE_HOME where the domain home directory is created. Default value wlserver/samples/domains
61
+ * ms_port may be used to configure port of the managed server, default is 8011
62
+ * prod_or_dev may be used to identify whether server is started in production or development mode. Defaults to "dev" for development mode.
63
+
64
+ ** Runtime Argument MS_NAME**
65
+ This argument may be used to completely override the managed server name.
66
+ For example, the following command may be used to run a managed server with name ms1
67
+
68
+ docker run --name msiserver --env MS_NAME=managedServer1 12212-msiserver
48
69
49
70
How to use the base image to add application
50
71
--------------------------------------------
@@ -63,6 +84,12 @@ summercamps app will now be accessible at
63
84
http://localhost:8011/
64
85
65
86
As with the base image, you can still override managed server name and cluster name
87
+ ** Build arguments**
88
+ Three build arguments may be used to customize the image to include an application of user
89
+ choice. By default, the build arguments point to an example application included in this
90
+ sample. The "name" argument helps identify the name of deployment, while the "source"
91
+ argument helps identify the source of the application. The source is copied into the image.
92
+ So "simple_filename" helps identify the name of the file where the source is copied to
66
93
67
94
Using swarm service creation with this image
68
95
--------------------------------------------
0 commit comments