Index Changes
Page Difference

Difference between version and version     

Back to Sun Data Mashup Engine Application Configuration, or Sun Data Mashup Engine Application Configuration Info


At line 1 changed 2 lines.
!!Sun Data Mashup Engine Application Configuration
This topic provides information about the Sun Data Mashup Engine application configuration feature, which enables the dependencies to be externalized and configured. When projects are moved from Development->Staging->Production, this feature can be used to migrate by configuration through the Sun GlassFish Enterprise Server Admin Console or the AppConfig Editor available through the JBI Manager. Using this feature, datasource connectivity configuration at Design–time can be overridden by associating the connection identifiers with {{jndi}} resources.
!!!Data Mashup Service Engine Application Configurations
At line 4 changed 18 lines.
!To Configure the Data Mashup Application Engine
# To correlate the connections with the Sun Java System Application Server (Sun GlassFish Enterprise Server) Admin Console Configurations screen, see the Edit Database Properties window in the EDM Editor.\\The source connections, for example {{SourceConnection1}} and {{SourceConnection2}}, listed in this window are the connections you need to overwrite. Configure the Connection Pools using the Sun Java System Application Server (Sun GlassFish Enterprise Server) Admin Console for the connections identified in step 1.
# Start the Sun GlassFish Enterprise Server and open the Admin Console.\\You are going to use Sun Java System Application Server Admin Console window to configure the connection pools you identified in step 1.
# In the Admin Console use the Configurations tab to create configuration entries.
## Under Common Tasks, select JBI->Components, and then highlight the component you want to configure.\\For example, {{sun-edm-engine}}.
## Under the Configurations tab, set the {{SourceConnection1}} and {{SourceConnection2}}.\\For example, {{SourceConnection1}} might equal {{__jdbc/derbypool__}} and {{SourceConnection2}} might equal {{__jdbc/mysqlpool__}}.
# Associate the Service Unit Endpoint in the EDM Editor canvas to a particular {{Config Extension}}.\\For example, here you are connecting a port, such as {{port1}}, to the (EDM) project, such as {{(EDM)yourProject}}.
# Deploy the project.\\After you have deployed the project, your changes to the configuration are applied, providing you with a runtime switch of connections.
! Related Topics
* [Sun Data Mashup Engine Overview|SunDataMashupEngineOverview]
* [Configuring and Starting the Sun GlassFish Enterprise Server|ConfiguringAndStartingTheSunGlassFishEnterpriseServer]
* [Designing Data Mashup Projects|DesigningDataMashupProjects]
* [Configuring Data Mashup Projects Using Joins|ConfiguringDataMashupProjectsUsingJoins]
* [Creating and Deploying a Composite Application to Complete a Data Mashup Project|CreatingAndDeployingACompositeApplicationToCompleteADataMashupProject]
* [Testing the Deployment of a JBI Composite Application|TestingTheDeploymentOfAJBICompositeApplication]
* [Viewing the Data|ViewingTheData]
* [Sun Data Mashup Engine REST Support|SunDataMashupEngineRESTSupport]
* [Known Data Mashup Issues|KnownDataMashupIssues]
This topic provides information about creating an application configuration for the Data Mashup Service Engine. When you design a Data Mashup application, you will likely use development or test data sources rather than production sources. When you move a Data Mashup project to staging and later to production, you might need to change the connection information and other properties for the new environment. Application configurations allow you to do this without having to reconfigure the design-time project.
At line 23 changed 1 line.
[Previous|ViewingTheData] [Next|SunDataMashupEngineRESTSupport]
Application configurations enable these dependencies to be externalized and configured. If you use application configurations to define different data sources, you need to create a connection pool and JDBC resource for each source database. Then you can specify the JNDI name of the resource in the application configuration.
You can create a configuration using either the GlassFish Enterprise Server Admin Console or the Application Configuration Editor, which is accessed through the NetBeans JBI Manager on the Service window. This topic provides instructions for both methods.
To create an application configuration, perform the following steps in the order given:
* [To View Design-Time Connection Information for Source Tables|SunDataMashupEngineApplicationConfiguration#ToViewDesignTimeConnectionInformationForSourceTables]\\
* [To Create Connection Pools and JDBC Resources|SunDataMashupEngineApplicationConfiguration#ToCreateConnectionPoolsAndJDBCResources]\\
* [To Create a Data Mashup Application Configuration (From the Admin Console)|SunDataMashupEngineApplicationConfiguration#ToCreateADataMashupApplicationConfigurationFromTheAdminConsole]\\
* [To Create a Data Mashup Application Configuration (From NetBeans)|SunDataMashupEngineApplicationConfiguration#ToCreateADataMashupApplicationConfigurationFromNetBeans]\\
* [To Associate the Application Configuration With an Endpoint|SunDataMashupEngineApplicationConfiguration#ToAssociateTheApplicationConfigurationWithAnEndpoint]\\
\\
\\
!To View Design-Time Connection Information for Source Tables
You can view a list of source connections and their database properties from the EDM file in a Data Mashup project. This can help you determine whether you need to create an application configuration to define different source databases. An Application configuration can overwrite these values at runtime.
# On the NetBeans IDE Project window, expand the Data Mashup project and double-click the EDM file to open it.
# Right-click on the EDM Editor canvas, and then select Database Properties.
# For each source connection listed, select the source connection and view the connection URL and login information.
\\
\\
!To Create Connection Pools and JDBC Resources
For an application configuration, you need to create one connection pool and one JDBC resource for each source database. You can use up to five source connections in an application configuration.
For more information about creating connection pools and JDBC resources, see [http://docs.sun.com/doc/820-4335/ablih?a=view].
# Launch the GlassFish Admin Console.
# For each source database used in the Data Mashup project, create one connection pool.\\__Note -__ The URL property is mandator for Derby connection pools. Make sure to add that property in the connection pool and enter the URL in the correct format.\\
# For each connection pool you created, create a corresponding JDBC resource.
\\
\\
!To Create a Data Mashup Application Configuration (From the Admin Console)
# Launch the GlassFish Admin Console.
# Under Common Tasks, expand JBI→Components, and then select sun-edm-engine.\\
The Service Engine General Properties page appears.
# Click the Application tab, and then click Add Configuration.
# In the Identification section, enter a name for the application configuration.
# In the General Properties section, enter the following information:
** __DataDir__ – The path to the source data files.\\
** __DynamicFlatFile__ – An indicator of whether the Data mashup SE uses the file name passed in the input query (in the URL or SOAP request, for example). When set to "true", the Data Mashup SE uses the file name in the input query. When set to "false", the Data Mashup SE constructs the file path using he value of the {{DataDir}} property plus the fle name passed in. When this property is not set, it defaults to {{user.home}}.\\
** __SourceConnection#__– The JNDI names of the JDBC resources you created above.\\
** __WorkingDir__ – The directory where temporary virtual database instances are created. If not set, this defaults to {{user.home}}.\\
# Click Save.
!To Create a Data Mashup Application Configuration (From NetBeans)
# On the NetBeans IDE, click the Services tab.
# Start the GlassFish server.
# Expand Servers > GlassFish V2 > JIB > Service Engines.
# Right–click sun-edm-engine and select Properties.
# Click the Ellipses button next to the Application Configuration property.\\
The Application Configuration Editor appears.
# Click Add.\\
An empty row appears.
# Enter the following information (click in the blank cell under a column name to add a value):
** __Configuration__ – A unique name for the application configuration.\\
** __DataDir__ – The path to the source data files.\\
** __DynamicFlatFile__ – An indicator of whether the Data mashup SE uses the file name passed in the input query (in the URL or SOAP request, for example). When set to "true", the Data Mashup SE uses the file name in the input query. When set to "false", the Data Mashup SE constructs the file path using he value of the {{DataDir}} property plus the fle name passed in. When this property is not set, it defaults to {{user.home}}.\\
** __SourceConnection#__– The JNDI names of the JDBC resources you created above.\\
** __WorkingDir__ – The directory where temporary virtual database instances are created. If not set, this defaults to {{user.home}}.\\
# Click Save.
\\
\\
!To Associate the Application Configuration With an Endpoint
Once you create the application configuration, you need to associate it with a composite application service unit endpoint. Then you can deploy the application and the new configuration is applied.
# In NetBeans, open the Service Assembly file that contains the Data Mashup project to configure. If the Service Assembly file does not exist, do the following:
** Create the composite application project.\\
** Add the Data Mashup project to the composite application.\\
** Build the composite application project.\\
** Expand the composite application node, and then double-click on the Service Assembly node to open the CASA Editor.\\
# On the CASA Editor, right-click the endpoint with which you want to associate the application configuration, and then click Properties.
# In the Config Extension section of the Properties window, enter the name of the application configuration you created earlier.
# Save the Service Assembly.
# Deploy the project.\\
After you have deployed the project, your changes to the configuration are applied, providing you with a runtime switch of connections.
\\
[Previous|ViewingTheData] [Next|SunDataMashupEngineRESTSupport]
------
[Return to GlassFish ESB Documentation Home|GlassFishESBDocs]
G'day, Anonymous Guest

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-13) was last changed on 16-Jun-09 16:27 PM, -0700 by CarolT