This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
• The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.
• References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.
� Version 5.1 of DB2 Analytics Accelerator opens up a new dimension of analytical processing by introducing accelerator-only tables and in-database analytics .
� Accelerator-only tables can benefit statistics and analytics tools that use temporary data
for reports. The high velocity of execution enables these tools to quickly gather all required data.
� Accelerator-only tables enable acceleration of data transformations implemented via SQL statements. Storing interim results in accelerator-only tables enables subsequent queries or data transformations to process all relevant data on the accelerator with high
speed
� In-database analytics capabilities enable acceleration of predictive analytics
applications. This enables SPSS/Netezza Analytics data mining and in-database modeling to be processed within the Accelerator.
In-database transformation and multi-step processing
� DB2 Analytics Accelerator introduces Accelerator-Only tables to store intermediate or final results of data transformation or multi-step processes
� Accelerator-Only tables enable complex data transformations taking place on DB2 Analytics Accelerator, called “In-database transformation”
� Accelerator-Only tables enable intermediate and final results of reporting or other processes to be generated and stored on DB2 Analytics Accelerator, called “In-database multi-step processing”
� Advantages:
� Accelerate in-database data transformations and data movement processes
� Reduced need of data movement processes to other platforms for data transformation purposes
� Enables multi-step reporting on the Accelerator
� Saves disk space and CPU cost on z Systems currently used for transformations and reporting steps
� Allow data preparation steps for data mining and other advanced analytics to execute on the Accelerator
� Store a set of data in DB2 Analytics Accelerator only, not on DB2 for z/OS, without
using the High Performance Storage Saver functionality
Multi-step reporting applications with DB2 for z/OS BEFORE Accelerator-only tables: Report processing on DB2, source data might reside on the Accelerator already
• Deeper insight into operational status through faster reportingSupport multistep reporting applications. Third party BI reporting suites, QMF, home grown applications, etc.
• Accelerated campaign tuning for IBM Campaign (Unica)Improved performance for iterative campaign tuning.
• Simplifying data-transformation processesDelivering in-database transformation within DB2 Analytics Accelerator
• Data mart consolidation through flexible data infrastructure Host data marts on z Systems, where the data originates
• Deeper insight into customers and marketsData scientist work area
• Simpler data integration with DB2 Analytics Accelerator Loader for z/OS (load non-DB2 for z/OS data)Assimilate more data sources for analytics to shorten development cycles and speed integration efforts
• In-database analytics to accelerate predictive analyticsImproves the quality of models, speeds calculations and delivers real-time, actionable business processes
Without Accelerator: The SPSS source node selects the input data from DB2 z/OS without any acceleration, then all data preparation is done in SPSS Modeler, followed by the modeling algorithm in
SPSS modeler, then the model is scored and scoring results are inserted into a DB2 z/OS result table
Source tables are accelerator-shadow tables and the accelerator processes the (complex)select statement
Step 1
Data preparation is pushed down into the accelerator producing an accelerator-only table for thetype node
Step 2
INZA modeling algorithm is called and executed in the accelerator on an accelerator-onlytable
Step 3
Data Source Access and Preparation Modelling Scoring
Source datasource process process t
(select) (select) Result data
In-database analyticsData preparation (using AOTs) and SPSS modeling in the Accelerator
Temporal Table support in DB2 Analytics Accelerator
� With V4 PTF 5
� Application(Business)-period temporal tables
� With V5.1, but for DB2 11 only
� System-period temporal tables
• Active table
• History table: contains the historical versions of the rows in the active
table
• Uses TIMESTAMP(12) for Begin and End columns
� Bitemporal tables
• Contains both Business Time temporal and System time temporal
definition
Temporal Table Concept: DB2 supports time-based data management that allows you to insert, update, delete, and query data in the past, the present, and future while keeping a complete history of what you knew and when you knew it.
• Implementing IPsec in the z/OS communications server - depending on the prior experience with that setup - can be a lengthy, complex process that requires planning and preparation. The system programmer performing the configuration steps on the
z/OS side should be familiar with z/OS communications server
� Accelerator (only N200x (Striper) and N3001 (Mako) models supported)
• Host management version 5.4.1.0 or higher incl. libreswan (installed by IBM service for
existing systems)
� Network
• For existing firewalls in the private data network: configure IKED port 500 the protocols
1. Generate a key pair and certificate for the z/OS side and activate it in the keyring owned by NSSD
2. Generate a key pair and certificate for the accelerator peer and export it into a PKCS#12 binary file. Store the file in the USS directory used for IDAA software updates
3. Transfer the PKCS#12 certificate file to the accelerator: IDAA Studio Accelerator View -> Transfer Update
4. Import the transferred certificate into the accelerator NSS database: IDAA configuration console -> (8) -(Menu) Manage Encryption of Data in Motion -> (1) - Import PKCS12 file with RSA keys and certificates
5. Restart the IPsec service to activate an imported certificate: IDAA configuration console ->(8) - (Menu) Manage Encryption of Data in Motion -> (7) - Restart the IPsec service
6. z/OS: Prepare the IPsec policy agent configuration for the LPAR
7. Enable an LPAR for IPsec on the accelerator: IDAA configuration console ->(8) - (Menu) Manage
Encryption of Data in Motion -> (3) - Enable encryption of data in motion
8. z/OS: Activate the prepared IPsec policy on the LPAR (Refresh policy agent)
9. Test your connection and diagnose problems
10. Confirm the IPsec configuration: IDAA configuration console -> (8) - (Menu) Manage Encryption of Data in Motion -> (4) - Confirm enablement of encryption
11. Verify that the network traffic is encrypted: IDAA configuration console -> (8) - (Menu) Manage Encryption of Data in Motion -> (6) - Display the status of encrypted connections
Console options for encryption of data and performance implications
Because current RedHat 6 Linux kernel allows only serial de/encryption (single threaded), throughput of Accelerator operations is currently limited to ~700 GB/h
for encrypted traffic. (Compared to 2-4 TB/h for unencrypted traffic)
Because current RedHat 6 Linux kernel allows only serial de/encryption (single threaded), throughput of Accelerator operations is currently limited to ~700 GB/h
for encrypted traffic. (Compared to 2-4 TB/h for unencrypted traffic)
AQT_INSTALL_PREFIX environment variable has been removed. Specify an absolute path in the environment variable AQT_HOST_PACKAGE_DIRECTORY. AQT_INSTALL_PREFIX environment variable has been removed. Specify an absolute path in the environment variable AQT_HOST_PACKAGE_DIRECTORY.
• Software upgrade of server components when stored procedure level > Accelerator server level(starting with 5.1 stored procedures and accelerator server 4.1)