Archive for category: Frontpage Article

Positive Pay File Creation (CB170) produces a flat file containing bank required payment information for issued, voided and stop paid payment transactions that have been processed since the last run of the CB170 for the cash code and transaction code.

NOTE: The first time the CB170 is run for a cash code, it will only report on open transactions.

The positive pay file is then sent to the bank to be used to confirm checks presented for payment have not been altered.

Since there are no standard file layouts, you will need to use an external mapping tool to reformat the file into the specific bank format. Use this procedure to define a positive pay file.

1. Access Positive Pay File Creation (CB170)
   
2. Consider the following fields.

• • Cash Code – Enter or select the cash code for which the report is being run. Enter or select one of Cash Code, Cash Code Group, or Cash Code List.
  • Cash Code Group – Enter or select the cash code group for which the report is being run. Enter or select one of Cash Code, Cash Code Group, or Cash Code List.
  • Cash Code List – Enter or select the cash code list for which the report is being run. Enter or select one of Cash Code, Cash Code Group, or Cash Code List.
  • Transaction Code – Enter or select the transaction code for which the report is being run.
  • Report Option – Select Full Detail or Summary print option.
  • Filename – Enter a name for the positive pay file. If this field is left blank, the report creates a file named CB170POSPAY.

Introduction:

In today’s hybrid IT environments, where organizations operate both on-premises data centers and cloud infrastructure, synchronizing data between these environments is critical. AWS Data Migration Service (DMS) offers a powerful solution for bridging the gap between on-premises data centers and the cloud. In this article, we will explore how you can leverage AWS DMS to synchronize changes between your on-premises data center and the cloud, ensuring data consistency and enabling real-time decision-making.

 

Setting Up the Replication:

To synchronize changes between your on-premises data center and the cloud, you need to set up replication using AWS DMS. Begin by deploying an AWS DMS replication instance in your AWS account, which serves as the migration engine. Configure the source endpoint for your on-premises database and the target endpoint for your cloud-based database service. AWS DMS supports various source databases, such as Oracle, Microsoft SQL Server, MySQL, and PostgreSQL. Ensure that your on-premises database is accessible from the AWS DMS replication instance.

 

Change Data Capture (CDC):

Change Data Capture (CDC) is a crucial feature provided by AWS DMS for real-time data synchronization. By enabling CDC, DMS captures and replicates only the changes made to the source database, ensuring that the target database remains up-to-date with the latest data. CDC can be configured at the table or database level, depending on your requirements. This capability minimizes data transfer and reduces the impact on network bandwidth, allowing near real-time synchronization between the on-premises data center and the cloud.

 

Network Connectivity and Security:

To synchronize changes between the on-premises data center and the cloud, a secure and reliable network connectivity is essential. AWS provides Virtual Private Cloud (VPC) and Direct Connect services to establish secure connections between your on-premises network and AWS cloud infrastructure. It is crucial to configure network security groups, firewalls, and routing rules to allow traffic between the on-premises data center and AWS resources. Follow AWS security best practices and ensure encryption of data in transit to maintain data integrity and confidentiality.

 

Monitoring and Managing Replication:

AWS DMS provides monitoring capabilities that allow you to track the progress of replication and detect any issues or delays. Utilize the AWS DMS console or leverage AWS CloudWatch to set up alarms and notifications for critical events. Monitoring replication latency, throughput, and error rates helps you identify potential bottlenecks and take proactive measures to optimize the synchronization process. Regularly review replication logs and metrics to ensure the health and performance of the replication tasks.

 

Handling Data Conflicts:

During the synchronization process, it’s possible to encounter data conflicts between the on-premises data center and the cloud. Conflicts can occur when the same data is modified in both locations simultaneously. AWS DMS provides conflict detection and resolution mechanisms, allowing you to define conflict resolution rules based on your business logic. By establishing clear conflict resolution strategies, you can ensure that data integrity is maintained and conflicts are resolved according to your defined priorities.

 

Disaster Recovery and High Availability:

Synchronizing data between on-premises and the cloud also enhances disaster recovery and high availability capabilities. By replicating data in near real-time, you can maintain a replica of your on-premises database in the cloud, enabling quick failover in case of a disaster. This replication approach ensures business continuity and minimizes data loss. Additionally, the cloud provides scalable and highly available infrastructure, which enhances the overall reliability and resilience of your data architecture.

 

Scalability and Cost-Effectiveness:

AWS DMS offers scalability and cost-effectiveness for synchronizing changes between on-premises data centers and the cloud. The service allows you to scale the replication instances based on your workload requirements, ensuring optimal performance during peak periods. Moreover, AWS offers a pay-as-you-go model, allowing you to pay only for the resources you use. This cost-effective approach eliminates the need for significant upfront investments in infrastructure and provides flexibility as your data synchronization needs evolve.

 

Conclusion:

AWS Data Migration Service (DMS) provides a robust solution for synchronizing changes between on-premises data centers and the cloud. By leveraging the power of DMS, organizations can achieve real-time data synchronization, enabling faster decision-making, enhancing disaster recovery capabilities, and embracing the scalability and cost-effectiveness of the cloud. With proper planning, network connectivity, and monitoring, AWS DMS empowers organizations to bridge the gap between on-premises and the cloud, unlocking the full potential of a hybrid IT environment.

Problem:

WebSphere Admin Console only shows WAS_HOME directory when browsing WAR/EAR files using “Remote File system”

 

Resolution:

This change is due to following Security Bulletin from IBM:

 

https://www.ibm.com/support/pages/security-bulletin-information-disclosure-websphere-application-server-cve-2017-1743

 

To get access to all directories, please add custom properties “com.ibm.ws.management.fileservice.allAccess” and “com.ibm.ws.console.webserver.anypath” property to “true” on Deployment Manager and the Node Agents.

 

In the WAS admin console,

 

Go to System administration –> Deployment manager –> Java and Process Management –> Process definition –> Java Virtual Machine –> Custom properties

 

Click the New button and enter the following:

Name: com.ibm.ws.management.fileservice.allAccess

Value : true

Click the New button and enter the following:

Name: com.ibm.ws.console.webserver.anypath

Value : true

 

Click Apply, then Save your changes to the master configuration.

 

Go to System administration –> Node Agents –> node_name –> Java and Process Management –> Process definition –> Java Virtual Machine –> Custom properties

 

Click the New button and enter the following:

Name: com.ibm.ws.management.fileservice.allAccess

Value : true

Click the New button and enter the following:

Name: com.ibm.ws.console.webserver.anypath

Value : true

 

Click Apply, then Save your changes to the master configuration.

 

Restart all the WebSphere services after setting the properties.

 

 

Introduction:

Migrating on-premises databases to the cloud can be a complex task, but with the right tools and strategies, it can be streamlined and efficient. One such tool provided by Amazon Web Services (AWS) is the AWS Data Migration Service (DMS). DMS allows you to migrate your on-premises databases to AWS easily and securely, minimizing downtime and ensuring data integrity. In this article, we will explore some top tips to help you make the most of the AWS Data Migration Service and successfully migrate your databases to AWS.

 

Understand Your Database Requirements:

Before diving into the migration process, it’s crucial to have a clear understanding of your database requirements. Take time to evaluate your current on-premises database and identify any specific configurations, performance needs, or dependencies. This understanding will help you plan the migration process effectively and choose the appropriate AWS services for hosting your database in the cloud.

 

Choose the Right AWS Database Service:

AWS offers a range of database services to cater to different workload requirements. Depending on your specific needs, you can choose Amazon RDS for traditional relational databases, Amazon DynamoDB for NoSQL databases, or other specialized services like Amazon Redshift for data warehousing. Understanding the strengths and limitations of each service will help you select the right one for your migrated database.

 

Assess Data Migration Compatibility:

Before proceeding with the migration, it’s essential to assess the compatibility of your on-premises database with AWS services. DMS supports various source databases such as Oracle, Microsoft SQL Server, MySQL, and PostgreSQL. Ensure that your database version is compatible with the DMS service and that any required updates or configurations are in place.

 

Design an Appropriate Migration Strategy:

Developing a well-thought-out migration strategy is crucial for a successful migration. AWS DMS provides different migration types, including full load, ongoing replication, and change data capture (CDC). Evaluate your database size, downtime constraints, and the frequency of data changes to determine the most suitable migration strategy. Consider factors like cost, data volume, and the impact on your production environment when making your decision.

 

Plan for Data Consistency and Validation:

Data consistency and integrity are paramount during the migration process. AWS DMS provides options to enable validation checks and data transformation capabilities. Leverage these features to validate data completeness, correctness, and accuracy before, during, and after the migration. Establish data validation processes and monitor the migration progress closely to ensure a seamless transition.

 

Optimize Network and Resource Utilization:

Migrating large databases can put a strain on your network bandwidth and system resources. To optimize the migration process, consider scheduling the migration during off-peak hours to minimize network congestion. Additionally, allocate appropriate resources to the DMS service to ensure smooth and efficient data transfer. AWS provides guidelines and best practices for resource allocation, which you should follow to avoid any performance bottlenecks.

 

Monitor and Troubleshoot:

During the migration process, it’s crucial to monitor the migration progress and promptly address any issues that may arise. AWS DMS provides detailed logs and metrics that allow you to monitor the migration and identify any potential bottlenecks or errors. Leverage these monitoring capabilities and take advantage of AWS CloudWatch to set up alarms and notifications for critical events. Additionally, refer to the AWS DMS troubleshooting guide and forums for common issues and resolutions.

 

Plan for Post-Migration Tasks:

Once the migration is complete, there are several post-migration tasks to consider. These include redirecting your applications to the new database in AWS, ensuring DNS changes are made if necessary, updating security group configurations, and validating the data in the migrated database. Be sure to have a detailed checklist to guide you through these tasks and ensure a smooth transition for your applications and users.

 

Conclusion:

Migrating on-premises databases to AWS using the AWS Data Migration Service offers numerous benefits, including scalability, reliability, and cost-efficiency. By following the tips outlined in this article, you can ensure a successful migration that minimizes downtime, preserves data integrity, and sets the stage for leveraging the full potential of AWS services. Remember to plan meticulously, validate your data, monitor the migration closely, and take advantage of the extensive documentation and support provided by AWS throughout the process. With the right approach and the power of AWS, you can seamlessly migrate your on-premises databases to the cloud and unlock a world of possibilities for your organization.