Not logged in | Login
Using Application Configuration With Connectivity Parameters
From the Application Configuration property, you can specify values for a Composite Application's external connectivity parameters, which are normally defined in the WSDL service extensibility elements. You can then apply these values to a user-named endpoint ConfigExtension Property. The Application Configuration property editor includes fields for all of the connectivity parameters that apply to that component's binding protocol. When you enter the name of a saved ConfigExtension and define the connectivity parameters in the Application Configuration editor, these values override the WSDL defined connectivity attributes when your project is deployed. To change these connectivity parameters again, you simply change the values in the Application Configuration editor, then shutdown and start your Service Assembly to apply the new values.
The Application Configuration property editor allows you to create several application configurations referenced by their own user-defined names. Note that different binding component protocols will have different attributes. The HTTP binding attributes are not the same as the JMS binding attributes, and therefore, the Application Configuration property editors for each of these binding components will contain different attributes.
To change a property when the application is running, change your Application Configuration property value, then right-click your application in the Services window under Servers > GlassFish > JBI > Service Assemblies, and click Stop in the popup menu. When you restart your project, your new settings will take effect.
The HTTP Binding Component's Application Configuration property contains one parameter only: HTTP URL Location.