You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+203Lines changed: 203 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -845,6 +845,209 @@ When creating the archive, the tool will try to gather all binaries, scripts, an
845
845
1. Any binaries referenced from the `ORACLE_HOME` will not be gathered, as they are assumed to exist in any target domain to which model-driven operations will be applied. Doing this is key to allowing the model to be WebLogic Server version independent.
846
846
2. In its current form, the discover domain Tool will only gather binaries and scripts that are accessible from the local machine. Warnings will be generated for any binaries or scripts that cannot be found but the configuration for those binaries will still be collected, where possible. It is the user's responsibility to add those missing files to the archive in the appropriate locations and edit the the model, as needed, to point to those files inside the archive using the relative path inside the archive (for example, `wlsdeploy/applications/myapp.ear`).
847
847
848
+
## The Variable Injector Tool
849
+
850
+
The variable injector tool is used to tokenize a model with variables. The values for these variables are assigned using an external property file. This facilitates using the same domain model to create new domains in different environments. The variable injector tool can be run as an option in the Discover Domain tool, or or from the stand-alone command line interface.
851
+
852
+
To enable the Variable Injector during the Discover Domain, create a variable injector configuration by placing a json file named model_variable_injector.json into the \<WLSDEPLOY\>/lib directory using one or more of the pre-defined keywords and/or a CUSTOM list of files. A keyword points to an injector directive file. The tool applies the directives to the attributes in a model, and if the directive matches an attribute, then a property token with a unique variable name is injected into the model and replaces the attribute value. The variable name and model attribute value are placed into the external variable properties file.
853
+
854
+
NOTE: Variable injection on an attribute is only performed once. The property token is not replaced by any subsequent matches.
855
+
856
+
If variable injection is enabled, the Discover Domain Tool calls the variable injector after the model has been discovered and after all filters run, but before model validation.
857
+
858
+
The supported keywords are as follows:
859
+
860
+
- CREDENTIALS - All MBean credentials attribute values (user and password) are injected with a variable.
861
+
862
+
- HOST - All MBean Host attribute values in the model are injected with a variable.
863
+
864
+
- PORT - All MBean Port attribute values in the model are injected with a variable.
865
+
866
+
- TARGET - All MBean Target attribute values in the model are injected with a variable.
867
+
868
+
- TOPOLOGY - Common environmental MBean attributes found in the topology section of the model are injected with a variable.
869
+
This includes server, machine and node manager ports, credentials and listen addresses, and cluster messaging modes, addresses and ports.
870
+
871
+
- URL - All MBean URL attribute values in the model are injected with a variable.
872
+
873
+
NOTE: The directives used by each pre-defined keyword are defined in an injector json file that is located in the \<WLSDEPLOY\>/lib/injectors folder. These files should not be changed, but could be used as .
874
+
875
+
Here is an example of a model_variable_injector.json file using the PORT keyword.
876
+
877
+
```json
878
+
{
879
+
"PORT": {}
880
+
}
881
+
```
882
+
883
+
Below is a model snippet that shows injected variables in the port attributes.
To specify the name and location of the variable properties file for the Discover Tool, use the argument `-variable_properties_file` on the command line. Usage of the variable_properties_file argument without the presence of the model variable injector file in the \<WLSDEPLOY\>/lib directory will cause an error condition and the tool will exit. If the model variable injector file exists in the directory, but the command line argument is not used, the variable properties file is created with the following defaults: If the model_file command line argument is used on the Discover Domain run, the properties file name and location will be the same as the model file, with the file extension `.properties`. If only the archive file argument is present, the archive file name and location will be used.
931
+
932
+
As with the archive and model file, each run of the discover domain tool will overwrite the contents of an existing variable property file with the values from the current run.
933
+
934
+
### Custom Variable Injector
935
+
936
+
To designate custom injector directives, use the CUSTOM keyword in the model_variable_injector.json. The CUSTOM keyword requires a a list of one or more custom injector directive json files.
937
+
938
+
An injector directive contains a key that identifies an attribute to be tokenized, and an optional set of directive properties. The key is a period separated MBean hierarchy and attribute name as they are defined in the model. Always exclude the name of the model section from the injector key.
939
+
940
+
For example, an injector key for the Server SSL Listen Port is as below. This directive contains no additional properties.
941
+
942
+
```json
943
+
{
944
+
"Server.SSL.ListenPort": {}
945
+
}
946
+
```
947
+
948
+
NOTE: The hierarchy of MBeans in the model for the ListenPort attribute and note that the MBean name of AdminServer is NOT included in the directive:
949
+
950
+
```yaml
951
+
topology:
952
+
Server:
953
+
AdminServer:
954
+
ListenAddress: myadmin.example.com
955
+
ListenPort: 7001
956
+
Machine: machine1
957
+
SSL:
958
+
Enabled: true
959
+
ListenPort: 7002
960
+
```
961
+
962
+
These custom injector json files will be processed by the Variable Injector tool before keywords, each file processed in list order. A property injected into an attribute will not be replaced by any subsequent matches.
963
+
964
+
#### Custom directive properties
965
+
966
+
Include the following properties to refine the directive as specified.
967
+
968
+
- force:<attribute>
969
+
If the MBean hierarchy exists in the model, but the attribute does not, then the attribute will be added and persisted to the discovered model. The value stored in the
970
+
model is the weblogic default value.
971
+
972
+
- variable_value:
973
+
Replace the model value with the specified value in the variable properties. This may be used in conjunction with the force directive, replacing the default value with the indicated value.
974
+
975
+
- regexp:
976
+
A list of regexp patterns that will be applied to either the string values or map values of an attribute in the model. If the pattern matches, then the matching part of the
977
+
string or dictionary will be injected with a property token and a unique variable name .
978
+
-- pattern:
979
+
the regular expression pattern to apply to the string value or map values of an attribute
980
+
-- suffix:
981
+
The suffix name to append to each resulting variable name in order to create a unique variable name
982
+
983
+
The regexp list is useful when only a segment of a string value or map needs to be tokenized (giving you a clean list of property values in the variable properties file). You can inject more than one token into a string or map with multiple patterns. However, when you have more than one pattern, you must provide a suffix for each. This allows the tool to generate a unique variable name for each token in the string or map.
984
+
985
+
The following is an example of how to effectively use the regexp directive list to search for a segment in a string value. In this example, we want to search for the host and port in each Oracle JDBC URL that uses the special Oracle URL notation, and create an entry for the host and port in the variable properties file.
986
+
987
+
In the model, we expect to find a URL like the following:
#### Selecting specific MBean names for variable injection
1029
+
1030
+
This final custom directive allows you to explicitly define which named entries for an MBean in the model you wish to inject properties. For instance, you might wish to tokenize an attribute just for a specific server. To define a list of one or more names for a specific MBean in the injector directive hierarchy, format the list as follows:
1031
+
```
1032
+
MBean[comma separated list of names]
1033
+
``
1034
+
To select only the admin server named AdminServer for a Server directive, use the format Server[AdminServer]. To select servers soa_server1 and soa_server2, format the key as Server[soa_server1,soa_server2]
1035
+
1036
+
The injector tool recognizes two KEYWORDS for a user list, MANAGED_SERVERS (all the managed servers in the model) and ADMIN_SERVER (The admin server in the model).
1037
+
1038
+
A custom injector for the admin server SSL listen port is:
1039
+
1040
+
```json
1041
+
{
1042
+
"Server[ADMIN_SERVER].SSL.ListenPort": {},
1043
+
}
1044
+
```
1045
+
1046
+
## Samples
1047
+
1048
+
A sample of a model_variable_injector.json file and a custom injector json file are installed in the WLSDEPLOY/samples directory.
1049
+
1050
+
848
1051
## Downloading and Installing the Software
849
1052
850
1053
The Oracle WebLogic Server Deploy Tooling project repository is located at [`https://github.com/oracle/weblogic-deploy-tooling`](https://github.com/oracle/weblogic-deploy-tooling). Binary distributions of the `weblogic-deploy.zip` installer can be downloaded from the [GitHub Releases page](https://github.com/oracle/weblogic-deploy-tooling/releases). To install the software, simply unzip the `weblogic-deploy.zip` installer on a machine that has the desired versions of WebLogic Server installed. After being unzipped, the software is ready to use, just set the `JAVA_HOME` environment variable to point to a Java 7 or higher JDK and the shell scripts are ready to run.
0 commit comments