Widgets in a space communicate with each other using wires.
When you add widgets to a page in a space, they are automatically
wired to each other in certain situations. If you prefer to determine
how widgets interact with one another, you can disable automatic wiring.
About this task
When you add widgets to a page, they are automatically
wired to one another when the following conditions apply:
- Automatic wiring is enabled. This setting is the default wiring
configuration.
- The definitions for the two widgets allow them to be automatically
wired.
- Event names sent by one widget match event names received by the
other widget.
- One of the two widgets is already on the page and the user adds
the other widget to the page.
You can disable this automatic wiring by changing a setting
in a configuration file.
Procedure
- Change the
autoWiringDefaultEnabled setting
to false in the configuration file.
- For a stand-alone server:
profile_root\BusinessSpace\node_name\server_name\mm.runtime.prof\config\ConfigService.properties
- For a cluster:
deployment_manager_profile_root\BusinessSpace\cluster_name\mm.runtime.prof\config\ConfigService.properties
- Run the updatePropertyConfig command
in the
wsadmin environment of the profile. Important: For Windows, the value for the
propertyFileName parameter
must be the full path to the file, and all backslashes must be double,
for example:
AdminTask.updatePropertyConfig('[-serverName server_name -nodeName node_name -propertyFileName "profile_root\\BusinessSpace\\node_name\\server_name\\mm.runtime.prof\\config\\ConfigService.properties" -prefix "Mashups_"]')
- For a stand-alone server:
The following example uses Jython:
AdminTask.updatePropertyConfig('[-serverName server_name -nodeName node_name
-propertyFileName "profile_root\BusinessSpace\node_name\server_name
\mm.runtime.prof\config\ConfigService.properties" -prefix "Mashups_"]')
AdminConfig.save()
The following example uses Jacl:
$AdminTask updatePropertyConfig {-serverName server_name -nodeName node_name
-propertyFileName "profile_root\BusinessSpace\node_name\server_name
\mm.runtime.prof\config\ConfigService.properties" -prefix "Mashups_"}
$AdminConfig save
- For a cluster:
The following example uses Jython:
AdminTask.updatePropertyConfig('[-clusterName cluster_name -propertyFileName
"deployment_manager_profile_root\BusinessSpace\cluster_name\mm.runtime.prof\
config\ConfigService.properties" -prefix "Mashups_"]')
AdminConfig.save()
The following example uses Jacl:
$AdminTask updatePropertyConfig {-clusterName cluster_name -propertyFileName
"deployment_manager_profile_root\BusinessSpace\cluster_name\mm.runtime.prof\
config\ConfigService.properties" -prefix "Mashups_"}
$AdminConfig save
- Run $AdminConfig save.