Sun Microsystems 5.1.3 manual Building and Deploying the Project, Running the Sample Project

Page 91

Chapter 7

Section 7.5

Implementing the VSAM eWay Sample Projects

Building and Deploying the prjVSAM_BPEL Sample Project

5Make any necessary changes to the Create Domain dialog box and click Create. The new domain is added to the Domain Manager. Select the domain and click the Start an Existing Domain button. Once your domain is started, a green check mark indicates that the domain is running.

Note: For more information about creating and managing domains see the eGate Integrator System Administration Guide.

7.5.9Building and Deploying the Project

The Build process compiles and validates the Project’s Java files and creates the Project EAR file.

Build the Project

1From the Deployment Editor toolbar, click the Build icon.

2If there are any validation errors, a Validation Errors pane will appear at the bottom of the Deployment Editor and displays information regarding the errors. Make any necessary corrections and click Build again.

3After the Build has succeeded you are ready to deploy your Project.

Deploy the Project

1From the Deployment Editor toolbar, click the Deploy icon. Click Yes when the Deploy prompt appears.

2A message appears when the project is successfully deployed. You can now test your sample.

7.5.10Running the Sample Project

Additional steps are required to run the deployed sample Project.

Steps required to run the sample Project:

1Rename one of the trigger files included in the sample Project from <filename>.in.~in to <filename>.in to run the corresponding operation.

The File eWay polls the directory every five seconds for the input file name (as defined in the Inbound File eWay Properties window). The Business Process then transforms the data, and the File eWay sends the output to an Output file name (as defined in the outbound File eWay Properties window).

The Where Clause defined in the business rule recognizes the trigger as a placeholder for input, allowing a set condition, such as EMPID = 100, to determine the type of output data.

You can modify the following input files to view different output.

ŠTriggerTableSelect.in

ŠTriggerDelete.in

ŠTriggerUpdate.in

VSAM eWay Adapter User’s Guide

91

Sun Microsystems, Inc.

Image 91
Contents EWAY Adapter for Vsam USER’S Guide Part Number Version Contents Transaction Support Levels Between Different Versions Setting Properties of the Vsam eWayPrepared Statement Batch Operations Creating an Environment Configuring the eWaysDelete Operations Activity Input and OutputCreate the Collaboration Business Rules Creating the Collaboration Definitions JavaWhat’s in This Chapter About VsamNew for Version About the Vsam eWayWhat’s New in This Release EWay OperationVsam eWay Javadoc About This DocumentText Conventions Related DocumentsScope Intended AudienceDocumentation Feedback Sun Microsystems, Inc. Web SiteInstalling the Vsam eWay Installing the Vsam eWayInstalling the Vsam eWay on an eGate supported system Copying JAR files to the eDesigner Library Installing Third-Party ProductsAfter Installation Extracting the Sample Projects and JavadocsExport the Project Ican 5.0 Project Migration ProceduresInstall Java Caps Steps to extract the Sample Projects includeDeploy the Project Installing Enterprise Manager eWay Plug-InsTo add plug-ins from the Enterprise Manager Viewing Alert CodesTo View the eWay Alert Codes Alert Code\Description Description Details User Actions Alert Codes for the Vsam eWayAduncommitted Configuring the eWay Connectivity Map Properties Creating and Configuring a Vsam eWayConnectivity Map with Components To configure the eWay propertiesOutbound eWay Properties Transaction Support Levels Between Different VersionsTo Configure the Environment Properties Configuring the eWay Environment PropertiesEWay Connectivity Map Properties Vsam eWay Environment ConfigurationConnectivity Map Outbound CP eWay Properties Outbound eWay-JDBC Connector SettingsConnectivity Map Outbound non-Transactional eWay Properties Outbound Vsam CP eWay Properties Inbound Vsam eWay-Parameter SettingsEWay Environment Properties Inbound Vsam eWay PropertiesVsam CP eWay-JDBC Connector Settings Jdbc Connector SettingsIs Vsam Connection Pool Datasource #param-2#........param Method-name-1#param#param-2#.........param ##method-name-2#paramVsam CP eWay-Connection Retry Settings Connection Retry SettingsConnection Pool Datasource Vsam non-Transactional eWay-JDBC Connector SettingsOutbound Vsam non-Transactional eWay Properties Is Vsam non-TransactionalMethod-name-1#param Vsam non-Transactional eWay-Connection Retry Settings Vsam non-Transactional eWay-Connection Retry Settings Creating a New Vsam OTD About the Database OTD WizardConnect To Database Select Wizard TypeRequired Database Connection Fields include Select Database ObjectsSteps Required to Select Database Objects Include Steps Required to Select Table and Views Include Select Tables/Views/AliasesSelect Tables/Views/Aliases Database Wizard All Schemes Selected Tables/Views/Aliases window with a table selected Table/View Columns Add Prepared StatementPrepared Statement Steps Required to Add Prepared Statements IncludePrepared SQL Statement Steps Required to Specify the OTD Name Specify the OTD NameSteps Required to Review Your OTD Selections Review SelectionsDatabase Wizard Summary Resulting OTDSteps to Edit the OTD from the Enterprise Designer Include Steps to Edit an Existing Vsam OTDVsam eWay Adapter User’s Guide Sun Microsystems, Inc Overview Using TablesUser-defined OTD To call a method in the Collaboration Editor Java Using the select MethodDelete Operations Update OperationsSelect Operations Insert OperationsUsing Prepared Statements Using ViewsTo use a prepared statement in a Collaboration Java Activity Input and Output Vsam eWay Database Operations BpelEInsight Operation Activity Input Activity Output Vsam OperationsVsam eWay Database Operations JCD To perform a query operation on a table Query Select OperationOtdVSAM1.getCICSEMP.insertRow Insert OperationDelete Operation Update OperationBatch Operations Prepared StatementChapter Section Using Vsam Operations About the Vsam eWay Sample Projects Implementing the Vsam eWay Sample ProjectsSample output Bpel files include Operations Used in the Vsam Sample ProjectsSample input files include Sample output JCD files includeAssigning Operations in JCD About the eInsight Engine and eGate ComponentsAssigning Operations in Bpel Running the SQL Script Running the Sample ProjectsBuilding and Deploying the prjVSAMBPEL Sample Project Importing a Sample ProjectCreating the OTDs Creating a ProjectSteps required to create a Vsam Database OTD include Steps to create a business process flow include Creating the Business ProcessCreating the Business Process Flow Steps required to create inbound and outbound DTD OTDsBusiness Process Activities Configuring the bpInsert Modeling ElementsBusiness Process Activity Steps required to configure the bpInsert business process BpInsert Business ProcessBpInsert Business Rule # BpInsert Business Rule # Configuring the bpUpdate Modeling Elements Steps required to configure the bpUpdate business process BpUpdate Business ProcessConfiguring the bpDelete Modeling Elements BpDelete Business Process Steps required to configure the bpDelete business processBpTableSelect Business Process Configuring the bpTableSelect Modeling ElementsBpTableSelect Business Rule # BpSelectTable Business Rule # Steps required to configure the bpPsSelect business process Configuring the bpPsSelect Modeling ElementsBpPsSelect Business Rule # Case 1 Scope Business Rule # Activities within Case 2 Scope Populating the Connectivity Map Creating the Connectivity MapSteps required to create the Connectivity Map Steps required to bind eWay components together Binding the eWay ComponentsTo Select a Vsam External System To Select a Vsam Business ProcessSteps required to create an Environment Creating an EnvironmentEnvironment Editor envVSAMProj Configuring the eWaysFileClientOUT eWay Property Settings Configuring the eWay PropertiesSteps required to configure the eWay properties FileClientIN eWay Property SettingsFile eWay Environment Properties Configuring the Environment Explorer PropertiesSection Property Name Required Values Creating the Deployment Profile Configuring the Integration ServerSteps required to create the Deployment Profile Steps required to create and start the domain Creating and Starting the DomainSteps required to run the sample Project Building and Deploying the ProjectRunning the Sample Project Build the ProjectBuilding and Deploying the prjVSAMJCD Sample Project Steps required to create a Vsam Database OTD Steps required to create a new Connectivity Map Creating a Connectivity MapSteps required to select a Vsam External System Creating the Collaboration Definitions JavaSteps required to create the jcdInsert Collaboration JcdDelete CollaborationJcdInsert Collaboration Steps required to create the jcdDelete CollaborationSteps required to create the jcdTableSelect Collaboration JcdPsSelect CollaborationJcdTableSelect Collaboration Steps required to create the jcdPsSelect CollaborationCreating the jcdDelete Business Rules JcdUpdate CollaborationSteps required to create the jcdUpdate Collaboration Create the Collaboration Business RulesSample code from the jcdInsert Includes Creating the jcdInsert Business RulesCreating the jcdPsSelect Business Rules Sample code from the jcdPsSelect Includes JcdPsSelectCreating the jcdTableSelect Business Rules Sample code from the jcdTableSelect Includes JcdTableSelectCreating the jcdUpdate Business Rules Binding the eWay Components JcdUpdate106 107 108 109 110 111 Running the Sample 113 Index 115

5.1.3 specifications

Sun Microsystems 5.1.3 represents a significant version in the evolution of Sun's software products, particularly in the area of network operating systems and development tools. Released during a time when Sun was a leading enterprise in the field of computing, 5.1.3 brought a host of new features, enhancements, and technologies that catered to the demands of users looking for robust and reliable IT infrastructure.

One of the defining characteristics of Sun Microsystems 5.1.3 was its enhanced scalability. The operating system was designed to handle large amounts of data processing and support numerous simultaneous users. This feature made it particularly attractive for businesses operating in resource-intensive environments such as finance, telecommunications, and large-scale enterprise applications.

A significant focus for 5.1.3 was its improved networking capabilities. The release integrated advanced networking protocols, allowing for better interoperability between systems. This feature enabled seamless communication across diverse hardware platforms, thus enhancing productivity and collaboration among users.

In terms of software development, Sun Microsystems 5.1.3 included an updated toolset that made application development more accessible. Its support for various programming languages, including C, C++, and Java, facilitated a versatile development environment. The included Sun C/C++ Compiler was particularly noteworthy, providing developers with optimized performance and debugging features.

Security features were also a priority in 5.1.3, addressing growing concerns over data protection and system vulnerabilities. The system implemented advanced user authentication, role-based access controls, and encrypted communications, thereby bolstering the integrity of user data and enhancing overall system security.

Additionally, Sun Microsystems 5.1.3 incorporated reliable file system technologies like the Sun File System (UFS), which offered improved performance and data integrity. This file system was particularly effective for enterprises that required high availability and data protection due to its robust recovery options.

Overall, Sun Microsystems 5.1.3 showcased a blend of advanced technologies, user-oriented features, and robust performance characteristics that positioned it as a compelling choice for enterprises seeking reliable and efficient computing solutions. It illustrated Sun's continuous commitment to innovation, ensuring users were equipped with the cutting-edge tools necessary to thrive in an increasingly digital world.