Skip navigation.
Downloads | Product Documentation | Support

Installation and Configuration Release Notes

# BEA Products Installation and Configuration Release Notes

### BEA AquaLogic Service BusTM Release: 2.1
BEA WebLogic Server® Release: 9.1
Document Revised: December 16, 2005

This document provides information about new capabilities, usage notes, and known limitations related to the installation and configuration of BEA AquaLogic Service Bus 2.1 and BEA WebLogic Server 9.1. This document also provides information about WebLogic Server upgrade tools and the new capabilities provided for Independent Software Vendor (ISV) partners.

The following topics are included:

- What's New in Installation and Configuration
- Supported Configurations and Special Installation Instructions
- Licensing
- Switching JDKs
- Customer Support
- Known Limitations
- Problems Fixed

For the latest release note information for BEA Products, go to the BEA documentation Web site at the following URL:

>     http://e-docs.bea.com

For detailed information about the BEA products encompassed by the AquaLogic Service Bus 2.1 and WebLogic Server 9.1 releases, including BEA JRockit J2SE 5.0 (R26.0) JDK, which is contained in the installation of these products, see the corresponding Release Notes document as follows:

For detailed release information about . . . | See the following Release Notes document . . .
--- | ---
AquaLogic Service Bus 2.1 | BEA AquaLogic Service Bus Release Notes
WebLogic Server 9.1 | For information about new features, see BEA WebLogic Server and WebLogic Express Release Notes. For information about known limitations and problems fixed, see BEA WebLogic Server Known and Resolved Issues.
BEA JRockit J2SE 5.0 JDK | BEA JRockit 5.0 (R26.0) JDK Release Notes

# What's New in Installation and Configuration

The following list summarizes new features and changes in the installation and configuration tools used with AquaLogic Service Bus 2.1 and WebLogic Server 9.1:

- Smart Update is a standalone Java application that you can run independently of BEA software, which has been enhanced in this release to include a new patch management capability. In addition to downloading and installing service pack updates, you can now use Smart Update to download and apply maintenance patches that have been made available from BEA Customer Support. For more information, see Installing Maintenance Updates and Service Packs.
- WebLogic domains created using WebLogic Server 9.1 include the new XACML security providers by default, including the XACML Authorization provider and the XACML Role Mapping provider.

The new XACML providers are fully compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). Existing WebLogic domains that you upgrade to 9.1 will continue to use the authorization and role mapping providers currently specified, such as third-party partner providers or the original WebLogic Authorization and Role Mapping providers. If you wish, you can migrate existing domains from using WebLogic Server proprietary providers to the XACML providers, including performing bulk imports of existing policies. For more information, see Security for BEA WebLogic Server 9.1.

- WLST has been enhanced as follows:

- You can now run WLST commands from Ant.

The `wlst` Ant task is predefined in the version of Ant shipped with WebLogic Server 9.1.

- The `createDomain` command has been added enabling you to create a domain quickly and easily using the specified domain template.
- The `nmGenBootStartupProps` command has been added enabling you to generate the Node Manager property files, `boot.properties` and `startup.properties`, for the specified server.

For more information, see WebLogic Scripting Tool.

- A new document, Using Offline Configuration Tools, describes best practices for using the offline configuration tools, including the Configuration Wizard, Template Builder, WLST offline, and pack and unpack commands.
- Upgrade documentation has been enhanced to cover upgrade procedures for the following product upgrades:

- WebLogic Server 9.0 to 9.1
- AquaLogic Service Bus 2.0 to 2.1

For more information, see Roadmap for Upgrading Application Environments.

- For licensing enhancements, see Licensing.

# Supported Configurations and Special Installation Instructions

Information about configurations supported by AquaLogic Service Bus and WebLogic Server, including hardware and software requirements, is provided from the Supported Configurations page at the following URL:

`http://e-docs.bea.com/platform/suppconfigs/index.html`

The documents available from the preceding page also include special installation and usage instructions, which are required for some operating systems.

# Licensing

To use the AquaLogic Service Bus and WebLogic Server software, you must have a valid license file installed on your system. When you install AquaLogic Service Bus 2.1 or WebLogic Server 9.1, the installation program installs a non-expiring development license to enable you to start using the software immediately. The development license is a full license, enabling use of all component features of the product software available from the installer.

To add a license for additional functionality, you need to update the `license.bea` file in your BEA Home directory. Please refer to Installing and Updating License Files in the BEA Products Installation Guide for more information.

In this release, the following BEA JRockit licenses are available:

- The BEA JRockit JDK installed with your software includes the BEA JRockit Mission Control tools suite. A separate license is required to use these tools. For more information about the JRockit Mission Control license types, see Licensing.
- BEA JRockit also includes the Mercury Profiling Tools. Installation of these tools is optional. If you choose to install them, you are prompted to accept the Mercury Tools license agreement. You must accept the license agreement to install the tools. For more information about these tools, see `http://www.mercury.com/us/products/diagnostics`.

For more information about the license packages available, see Licensing.

# Switching JDKs

The following instructions are provided for users who have already installed either AquaLogic Service Bus or WebLogic Server and want to switch from Sun Java 2 to BEA JRockit, or vice-versa:

1. Examine the WebLogic Server start script. This script is located in the `bin` subdirectory of your domain's root directory and, by default, is named `startWebLogic.cmd` (Windows) or `startWebLogic`.`sh` (UNIX).
2. Locate the settings for the following two variables:

- `JAVA_VENDOR`
- `JAVA_HOME`

3. If these variables are set within the script, change them as appropriate.

The following `set JAVA_VENDOR` and `set JAVA_HOME` commands specify the BEA JRockit J2SE 5.0 JDK, where `c:\bea` is the BEA home directory:

`set JAVA_VENDOR=BEA
set JAVA_HOME=c:\bea\jrockit90_150_04`

For Sun, the equivalent commands are as follows:

`set JAVA_VENDOR=Sun
set JAVA_HOME=c:\bea\jdk150_04`

4. If the `JAVA_VENDOR` variable is not set in the WebLogic Server start script, then you need to set the default JDK in the `setDomainEnv`.`cmd` (Windows) or `setDomainEnv.sh` (UNIX) script as described in this step. The `setDomainEnv` script is also located in the `bin` subdirectory of the domain's root directory.

The following two code snippets show the switching of the default JDK from Sun Java 2 JDK 5.0 to BEA JRockit J2SE 5.0 (R26.0) JDK in `commEnv.cmd` on Windows. In these snippets, the BEA home directory is `c:\bea`.

The first code snippet shows the initial settings that establish Sun Java 2 JDK 5.0 as the default:

>     if "%JAVA_VENDOR%"=="BEA" (
>            set JAVA_HOME=C:\bea\jrockit90_150_04
>     ) else (
>            if "%JAVA_VENDOR%"=="Sun" (
>                  set JAVA_HOME=C:\bea\jdk150_04
>            ) else (
>                  set JAVA_VENDOR=Sun
>                  set JAVA_HOME=C:\bea\jdk150_04
>            )
>     )

The second code snippet shows the changes, in bold, made to switch to JRockit as the default:

>     if "%JAVA_VENDOR%"=="BEA" (
>            set JAVA_HOME=C:\bea\jrockit90_150_04
>     ) else (
>            if "%JAVA_VENDOR%"=="Sun" (
>                  set JAVA_HOME=C:\bea\jdk150_04
>            ) else (
>                  set JAVA_VENDOR=BEA
>                  set JAVA_HOME=C:\bea\jrockit90_150_04

For more information about BEA support for BEA JRockit and the Sun Java 2 JDK, see the following documents:

- For AquaLogic Service Bus 2.1, see AquaLogic Service Bus 2.1 Supported Configurations in Supported Configurations for AquaLogic Service Bus 2.1.
- For WebLogic Server 9.1, see WebLogic Server 9.1 Supported Configurations in Supported Configurations for WebLogic Server 9. 1.

# Customer Support

If you have any questions about this version of AquaLogic Service Bus or WebLogic Server, or if you have problems installing and running the product, contact BEA Customer Support through BEA eSupport at:

>     http://support.bea.com

You can also contact Customer Support by using the contact information provided on the BEA Customer Support card, which is included in the product package.

When contacting Customer Support, be prepared to provide the following information:

- Your name, e-mail address, phone number, and fax number
- Your company name and company address
- Your machine type and authorization codes
- The name and version of the product you are using
- A description of the problem and the content of pertinent error messages

# Known Limitations

This section describes problems that have been identified in the installation and configuration software delivered with AquaLogic Service Bus 2.1 and WebLogic Server 9.1. Whenever possible, workarounds are provided.

For each problem described, a tracking number is specified. These numbers enable BEA and users to monitor the status of issues while solutions are being developed.

Table 1 Known Problems

Problem ID | Description
--- | ---
CR214849 | Thread dump occurs when Ctrl+C is used to stop server Using Ctrl+C to stop a WebLogic Server instance results in a thread dump in the command window from which the server was started. This problem occurs because the RDBMS configured for the domain halts before the WebLogic Server shutdown procedure is completed. This problem can happen in either the WebLogic Server Examples domain or Avitek Medical Records domain when configured with the default PointBase RDBMS, but potentially can happen in any domain in which the RDBMS is configured to start and stop with WebLogic Server. Operating System: Windows Workaround: The recommended way to shut down a WebLogic Server instance is via the WebLogic Server Administration Console. For details, see Starting and Stopping Servers in Managing Server Startup and Shutdown.
CR220653 | WebLogic Server fails to start and displays the message that the server is not found in the WL_HOME directory A message similar to the following is displayed when you try to start WebLogic Server: `The WebLogic Server wasn't found in directory` `directory-name``. Please edit the setWLSEnv.cmd script so that the WL_HOME variable points to the WebLogic installation directory. Your environment has not been set.` This problem is caused by a Windows bug that limits the length of the directory name you can use for the BEA Home directory. Operating System: All Workaround: Do not choose a BEA Home directory name that contains more than 12 characters.
CR224184 | PointBase is not disabled after a domain is extended using two or more extension templates, and an extension template other than the first is used to change the database from PointBase to a production RDBMS If you extend a domain using two or more extension templates, and switch the database from PointBase to a production RDBMS when applying the second template or a subsequent one, PointBase is not disabled for the domain. Operating System: All Workaround: Two workarounds can be used to avoid this problem, as follows: When extending the domain using the first extension template, specify the production RDBMS. This step ensures that subsequent extension templates do not re-enable PointBase. When starting the domain, run the WebLogic Server start script specifying the `nopointbase` option. For example: UNIX: `startWebLogic.sh nopointbase` Windows: `startWebLogic nopointbase`
CR224337 | Server fails to start when domain name includes a dot and the dot is preceded and followed by strings of a certain length If you create a domain and assign a name that has all the following characteristics, the domain will not start: The name includes the period character (.). Two alphanumeric characters precede the period. Five or more alphanumeric characters follow the dot. For example, a domain created with the name `bs.domain` will not start. Operating System: All Workaround: When choosing a domain name, do one of the following: Do not use a name that contains a dot character. If you use a dot character, make sure that you provide more than two characters preceding the dot.
CR227881 | Limited support in Template Builder for compatibility-mode security When using the Domain Template Builder to create a template from a domain that contains a Compatibility security configuration, you cannot create or assign additional users, groups, and global roles. Operating System: All Workaround: After you create a domain based on a template that contains a Compatibility security configuration, boot the domain and add users, groups, and roles via the WebLogic Server Administration Console.
CR228401 | A single-server domain cannot be configured correctly by deleting all but one server from a clustered domain template Neither the Configuration Wizard nor WLST offline support the creation of a single-server domain based on a template of a clustered domain from which all but one server are removed. The reason for this restriction is that a clustered domain template contains no initial single-server targeting state, which is needed when you attempt to make this type of customization. Operating System: All Workaround: If you are creating a single-server domain, choose a template that is not created from, or based on, a domain that is clustered.
CR229655 | Exception java.lang.UnsupportedOperationException thrown from domain configured using WLST offline When operating in offline mode, WLST does not support the creation of security roles. If a WLST offline script includes statements that define security roles, WLST terminates abnormally when executing the script, throwing the `java.lang.UnsupportedOperationException` exception. Operating System: All Workaround: Use WLST in online mode to specify security roles.
CR229700 | QuickStart is not displayed correctly after installation When installing AquaLogic Service Bus or WebLogic Server, if you specify a directory for either the BEA Home directory or WebLogic Server Home directory that contains a multibyte character set in the directory name, QuickStart is not displayed correctly after the installation is complete. Operating System: Any system in which the Sun Java 2 J2SE 5.0 is used. Workaround: During installation, choose directories for BEA Home and WebLogic Server Home with names that include only the ASCII character set.
CR230483 | Configuration of application-scoped resources cannot be changed in domain template If you create a template or extension template of a domain that contains application-scoped resources, and then create or extend a clustered domain on the basis of that template or extension, the Configuration Wizard may not properly retarget the application-scoped resources. If the template on which a clustered domain is based contains application-scoped JMS or JDBC resources, the domain may fail to start. Operating System: All Workaround: Note the following best practices for creating domains and templates: When creating a domain or extension template, include only JMS and JDBC resources that are global to the domain and that can be customized during the domain creation process; for example, JDBC data source and JMS file store settings for the domain, or cluster configuration settings. Rely on the application and on the application deployment process to create the required application-scoped resources in the target environment. If you are migrating an application from a nonclustered to a clustered domain, and the application includes packaged JMS resources for which you want to have scalability and load balancing, you can do the following: — In place of each JMS queue in the packaged JMS module, create a uniform distributed JMS queue. — Configure a JMS server for each Managed Server in the cluster. — Include the connection factory and the uniform distributed queues in the same subdeployment group, and deploy them to the cluster. When the application is deployed, each Managed Server in the cluster has a connection factory and a member for each distributed queue. For information about configuring JMS for a clustered environment, see Configuring Clustered WebLogic JMS Resources in Configuring and Managing WebLogic JMS. After you create or extend the domain, you may need to perform additional steps to make sure that the application and its application-scoped resources are targeted and deployed properly for a clustered environment. For more information on the targeting and deployment of application-scoped modules, see Deploying Applications and Modules in Deploying Applications to WebLogic Server.
CR231843 | Service Bus domain templates cannot be created because of database dependency If you create a template of a Service Bus domain, and then create a new Service Bus domain based on that template, the new domain cannot be started. This problem is caused by a dependency that is created between the domain RDBMS and the domain name, which results in a restriction upon the usage of templates that you create from Service Bus domains. This problem occurs because the new domain attempts to use the same database, schema, and Logging Last Resources (LLR) table name (for storing LLR transaction records) that are used by the initial domain. LLR checks for this to prevent one domain from corrupting the LLR tables of another domain. Operating System: All Workaround: Two workarounds are available for this problem: When creating a new Service Bus domain that is based upon a template of an existing Service Bus domain, you must use the same database, schema, and Logging Last Resources (LLR) table name (for storing LLR transaction records) for the domain that were used for the existing domain. To learn more about the LLR feature, see Configuring JDBC Data Sources in Configuring and Managing WebLogic JDBC. After you create the new domain, use WLST offline to change the name of the LLR table used by each server in the new domain. The LLR table name can be specified via the `JDBCLLRTableName` attribute on the `ServerMBean`.
CR234354 | In a base WebLogic domain that has been extended with the WebLogic Server Default Domain and WebLogic Server Examples extension templates, the server cannot be started After you extend a base WebLogic domain with the WebLogic Server Default Domain and WebLogic Server Examples extension templates, the resulting domain will not boot. This problem occurs if, after creating a domain in the Configuration Wizard, you navigate backward in the Configuration Wizard to the initial window and extend the newly created domain without having first exited from that tool. Operating System: All Workaround: After you use the Configuration Wizard to create a domain, restart the Configuration Wizard before extending that domain.
CR234871 | Installer hangs on Windows XP during Node Manager configuration If you choose to install Node Manager as a Windows service, which is an option available via a custom installation, the installation program may hang after you specify a listen port for Node Manager. This problem may occur if Windows Firewall is running, and the listen port chosen for Node Manager has not been specified as a Windows Firewall exception. Operating System: Windows XP Professional with Service Pack 2 Workaround: Before you run the installation program, do either of the following: Turn off Windows Firewall (recommended) Add the port you want to use for the Node Manager listen port as a Windows Firewall exception If you choose to turn off Windows Firewall prior to installation, you can turn it back on after the installation procedure is complete.
CR234973 | Managed Server template should not include applications A Managed Server template created using the `pack` command includes all the end-user applications, including application files, for the domain from which the template was created. This results in a template JAR file that is potentially very large. Operating System: All Workaround: After you create a domain based on a Managed Server template, you can safely remove directories that contain user-created applications. This will not prevent you from being able to start the domain. If the user-created applications in the Managed Server template do not use a great deal of disk space, this problem is not an issue for creating or starting the domain. Note that AquaLogic Service Bus domains contain a large number of system-level applications and files that must not be removed.
CR244593 | Servers for both WebLogic examples and Avitek Medical Records sample cannot be started at the same time due to database conflicts You cannot start or run the servers in the domains for the WebLogic examples and Avitek Medical Records (MedRec) sample at the same time because both servers reference the same database files. Operating System: All Workaround: Do not attempt to run both sample servers simultaneously. Stop one server before starting the other one.
CR251454 | GUI cannot refresh patches installed from command line without restart If you use the Smart Update graphical and command-line interfaces simultaneously, patches that you apply via the command-line interface are not visible from the GUI when you refresh the view. Operating System: All Workaround: Exit and restart the Smart Update GUI to view the new patch.
CR253610 | Mercury profiling tools are not installed if not initially selected During product installation, if you deselect the Mercury profiling tools on the Optional Tools screen, select Next, and then subsequently return to the Optional Tools screen using the Previous button and select to install the Mercury profiling tools, the tools will not be installed. Operating System: All Workaround: If you wish to install the Mercury profiling tools, make sure that you select the Mercury profiling tools on the Optional Tools screen when you are prompted inititally.
CR254744 | Smart Update graphical interface displays java.util.ConcurrentModificationException in rare cases In rare cases, when using the Smart Update graphical interface, the following exception may be displayed: `java.util.ConcurrentModificationException at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1031) at java.util.TreeMap$KeyIterator.next(TreeMap.java:1058) at com.bea.plateng.patch.gui.PatchStoreTableModel.getRowCount(PatchStoreTableModel.java:199)` Operating System: All Workaround: This exception can be ignored.
CR255640 | Smart Update's patch profile maintenance snapshot text file is poorly formatted when viewed in Notepad The patch profile maintenance snapshot file produced by Smart Update cannot be easily viewed in common text editors, such as Notepad. The snapshot file does not contain conventional line breaks, which results in poorly formatted columns that cannot be easily read. Operating System: All Workaround: Use a text editor such as WordPad or TextPad to view this file. You do not need to reformat this file when sending it to BEA Customer Support.
CR255650 | Invalidated patches should not list other invalidated patches as their replacement When you display details about an invalidated patch, the ID of the replacement patch may be provided. But if the replacement patch is subsequently invalidated by BEA Customer Support, this ID will not be updated and will refer to an invalidated patch. Operating System: All Workaround: Contact BEA Customer Support.
CR255916 | Exception is generated when reapplying the last of multiple patches After having applied multiple patches that contain patch JAR files with the same name, if you remove and then attempt to reapply any of those patches, you may see an exception similar to the following: `java.lang.IllegalArgumentException: JarEntry must not be null.` `at com.bea.plateng.common.util.JarHelper.extract(JarHelper.java:646)` `at com.bea.plateng.common.util.JarHelper.extract(JarHelper.java:605)` `at com.bea.plateng.common.util.JarHelper.extract(JarHelper.java:563)` `at` `com.bea.plateng.patch.ClasspathPatchInstaller.install(ClasspathPatchInstaller.java:118)` `at` `com.bea.plateng.patch.PatchInstallationHelper.install(PatchInstallationHelper.java:258)` Operating System: All Workaround: Exit and restart Smart Update, and reapply the patch that previously caused the exception.
CR256067 | Cannot create a domain using a template that was created from the out-of-the box AquaLogic Service Bus Examples domain If you create a domain using a template that was generated from the out-of-the box AquaLogic Service Bus Examples domain, the server may not start. Operating System: All Workaround: There is no workaround. Creating a domain using a template that was generated from the out-of-the box AquaLogic Service Bus Examples domain is not supported.

# Problems Fixed

Table 2 describes problems that have been fixed in the installation and configuration software delivered with AquaLogic Service Bus 2.1 and WebLogic Server 9.1.

Table 2 Problems Fixed

Problem ID | Description
--- | ---
CR231028 | Servers for both WebLogic examples and Service Bus samples cannot be started at the same time You cannot start or run the servers in the domains for WebLogic examples and Service Bus samples at the same time. This problem is caused by the fact that both servers are configured to use the same default port number. Operating System: All Workaround: Do not attempt to run both sample servers simultaneously. Stop one server before starting the other one. Fix Information: The default port numbers for the Service Bus samples have been updated as follows so that they no longer conflict with the default ports for the WebLogic examples: `http server: 7021` `ssl: 7022` `PointBase: 9073`
CR232132 | Server does not start if name of domain root directory contains a space If you use the Configuration Wizard to create a domain, and specify a name for the domain root directory that contains a space, the domain server cannot be started. When you attempt to boot the domain, a message similar to the following is generated: `starting weblogic with Java version: ./startWebLogic.sh: line 171: /bin/java: No such file or directory Starting WLS with line: /bin/java -Dweblogic.Name= -Djava.security.policy=/server/lib/weblogic.policy ./startWebLogic.sh: line 176: /bin/java: No such file or directory ./startWebLogic.sh: line 184: popd: directory stack empty` Operating System: UNIX and Linux Workaround: When specifying the name of the domain's root directory, do not use spaces. Fix Information: When the Configuration Wizard is run on a UNIX or Linux machine, the tool will not allow you to include spaces in the name of the domain root directory.
CR234126 | Newly configured PKI credential mapper is available via the run-time tree without reboot When security providers are added to or removed from the list of security providers in the run-time MBean tree, a reboot should be required before the revised list is displayed. Currently, however, WebLogic Server displays the changed set of security providers in the run-time MBean tree immediately, and the listed security providers are immediately available for management operations. Even though the providers become available for management operations immediately, the server continues to use the set of providers that was present at boot time for security run-time operations (such as authentication, authorization, auditing, and so on). Operating System: All Workaround: A reboot of the server is required for these changes to the security framework to affect the run-time security operations. This requirement applies to all security providers. Fix Information: On a UNIX or Linux machine, the Configuration Wizard does not allow you to include space characters in the name of the domain root directory.
CR234353 | Help button in Configuration Wizard opens Template Builder Help When using the Configuration Wizard to extend a domain, clicking Help in the Review WebLogic Domain window invokes the Template Builder online help. Operating System: All Workaround: Two workarounds are available to display help for the Review WebLogic Domain window while extending a domain: See "Review the Domain Settings" in Customizing Existing JDBC and JMS Settings in Creating WebLogic Domains Using the Configuration Wizard. Paste the following URL into the location bar of the online help viewer for the Configuration Wizard, where `WL_HOME` represents the absolute path to the WebLogic Server home directory; for example, `C:\bea\weblogic90`: `file:///``WL_HOME``/common/help/cwhelp/doc/en/cfgwizhelp/ServiceReview.html` Fix Information: The Help button displays the correct help information.
CR234458 | Oracle 10g database does not allow insertion of a character string larger than 1000 bytes using the latest 10g driver You cannot insert a variable-length character string that is larger than 1000 bytes into an Oracle 10g database (Oracle 10.1.0.2) using the latest Oracle 10g driver. This limitation extends to `CHAR`, `VARCHAR`, and `VARCHAR2` datatypes containing strings that use any of the following Japanese character sets: JA16SJIS JA16EUC JA16SJISTILDE JA16SJISYEN Operating System: All Workaround: You can use either of the following two workarounds: Upgrade the Oracle 10g database to Oracle 10.1.0.4, in which this problem is fixed. Use the latest Oracle 10g driver to insert larger character strings into an Oracle 9i database. (However, this problem still exists when attempting to insert these strings into an Oracle 10g database earlier than 10.1.0.4.) Fix Information: This limitation no longer exists.
CR235341 | Missing updates to WLST online help The online help for the WebLogic Server Scripting Tool does not include the following updates: 1. The `suspend` command description includes the following note, which should be removed: NOTE: The domain administration port must be enabled to invoke the suspend command. 2. The note that appears with the `startNodeManager` command description should be updated as follows: NOTE: The WebLogic Server custom installation process optionally installs Node Manager as a Windows service on Windows systems, so that it starts automatically when you boot the computer. For more information, see About Installing Node Manager as a Windows Service in the BEA Products Installation Guide. In this case, you do not need to start Node Manager manually. Operating System: Windows Workaround: The topic WLST Command and Variable Reference in WebLogic Scripting Tool contains the preceding updates. Fix Information: The WLST online help has been updated.
CR235344 | Administration Server name and listen port changes specified in Template Builder do not take effect for Service Bus domains When using the Domain Template Builder to create a template of a Service Bus domain, if you change the host name and listen port of the Administration Server, those changes do not take effect in the resulting template. The resulting template retains the host name and listen port of the Administration Server for the Service Bus domain from which the template was created. Operating System: Windows Workaround: After you create a domain based on this template, edit the domain `config.xml` file and enter the correct host name and listen port. Fix Information: The host name and listen port changes are now saved to the domain template.