Wednesday, November 9, 2022

ADABAS NATURAL CE Docker Version essential commands

1) PULL IMAGE

1.1) ADABAS V7.0.1: docker pull softwareag/adabas-ce:7.0.1

1.2) NATURAL V9.1.4: docker pull softwareag/natural-ce:9.1.4

1.3) ADABAS MANAGER V9.0.0.4 : docker pull softwareag/adabasmanager-ce:9.0.0.4

2) SAVE IMAGE

2.1) ADABAS: docker save softwareag/adabas-ce:7.0.1 -o adabas-ce.7.0.1.tar

2.2) NATURAL: docker save softwareag/natural-ce:9.1.4 -o natural-ce.9.1.4.tar

2.3) ADABAS MANAGER: docker save softwareag/adabasmanager-ce:9.0.0.4 -o adabasmanager-ce.9.0.0.4.tar

3) LOAD IMAGE TO DOCKER

3.1) ADABAS: docker load -i adabas-ce.7.0.1.tar

3.2) NATURAL: docker load -i natural-ce.9.1.4.tar

3.3) ADABAS MANAGER: docker load -i adabasmanager-ce.9.0.0.4.tar

4) RUN IMAGE AS CONTAINER

4.1) ADABAS: docker run -d -p 60001:60001 -p 8190:8190 -e ACCEPT_EULA=Y -e ADADBID=12 -e ADA_DB_CREATION=demodb --name adabas-db softwareag/adabas-ce:7.0.1

4.2) NATURAL: docker run -it -p 2700:2700 -e ACCEPT_EULA=Y --add-host adabas-db:172.17.0.2 --name natural-ce softwareag/natural-ce:9.1.4

Note: Replace the ip no. 172.17.0.2 with your actual ip no.

4.3) ADABAS MANAGER: docker run -it -p 4990:4990 -e ACCEPT_EULA=Y --name adabas-manager softwareag/adabasmanager-ce:9.0.0.4

REFERENCE:

https://hub.docker.com/r/softwareag/adabas-ce

Saturday, November 5, 2022

How-To: Fix ADABAS NATURAL ONE ERROR "Connection to Natural server failed"

Error description:

When a Natural AJAX page is launched from Natural ONE IDE, the page displays Connection to Natural server <ip number> failed. (The server runs from a Docker container).

Possible explanation:

It could be due to incorrect ip number assign to Natural CE container in the docker run command.

Try running ipconfig command in the terminal and look for ip number for WSL

Thursday, November 3, 2022

How To Setup the Adabas and Natural Community Edition (Docker Version)

Setting up the Adabas and Natural Community Edition packages

Adabas is a non-relational database package that was developed by Software AG initially to run on IBM mainframes in 1971 (Wikipedia 2005). Recently Software AG claimed that Adabas and, its associated programming language, Natural, can run virtually anywhere including the cloud (Software AG 2020). They even announced that Adabas will reach far beyond the year 2050 (Software AG 2022). This series of blogs is a personal exploration on the Adabas and Natural Community Editions aiming to experience and appreciate the softwares.

Adabas=Database
Natural=Programming Language

Adabas and Natural Community Editions are available as Docker images (read here for those who are new to Docker). The community edition consists of three software bundles which must be installed altogether. The steps are as follows. Read the instructions on the respective web sites in order to set them up successfully.

(1) Pull and Run Adabas CE (refer https://hub.docker.com/r/softwareag/adabas-ce version 7.0.1),

(2) Pull and Run Natural CE (refer https://hub.docker.com/r/softwareag/natural-ce version 9.1.4),

and

(3) Download, Unzip and Run Natural ONE IDE (refer https://softwareag-usa.s3.amazonaws.com/Adanat_Docker/ONE.9.1.4.CE.zip version 9.1.4). Be cautioned that the default Windows unzip application may not be able to extract the contents correctly due to long file path name errors and therefore alternative unzip applications such as 7Zip is recommended.

The overview of the software roles are as follows.

Overview of the roles of the softwares (Software AG)

The Adabas Community Edition for Docker image contains Adabas with all its Adabas utilities. For communication between Adabas server and other Adabas client Docker containers, Adabas provides a Adabas TCP/IP based communication link ADATCP. The Natural Community Edition Docker image contains the corresponding Adabas Client components and configuration option to use the Adabas TCP/IP link. (https://hub.docker.com/r/softwareag/adabas-ce)

Upon the successful setup of Adabas-CE version 7.0.1, the users would be able to view the Adabas REST web application login page via the URL http://localhost:8190 . The default login credential is provided on the page itself.

Adabas REST web application login page (Software AG)

The first page that users are recommended to visit is the databases page (i.e. http://localhost:8190/#/databases). This page provides the list of databases that the Adabas REST web application is connected to. Users can create new databases by clicking the button Create Adabas database (but, perhaps due to limited functionality of this Community Edition package, new databases could not be started. Read more about this by clicking the Nucleus Log button). The Name Field contains the name of the database i.e. GENERAL_DATABASE. The Show Details Field contains grouped information by the labels Parameters, Containers, Nucleus Log, Files, Statistics and Queues.

Click on the name i.e. GENERAL_DATABASE to view the database information. The displayed information is as follows.

Adabas Database Information for database no. 12

The last three rows contains the information for (1) Security File, (2) Checkpoint File and (3) ETData File.

(1) The Adabas Security File contains the Adabas security definitions. For more information on Adabas security, refer to the documentation of the ADASCR utility, which is used to maintain the Adabas security definitions.
(2) The Adabas Checkpoint File is used to log some important events, the Adabas checkpoints; these checkpoints are written for: (a) Adabas utility execution, (b) Nucleus starts and stops, (c) Adabas user sessions with exclusive access to Adabas files, (d) User-defined checkpoints. The checkpoints are especially important for the database recovery.
(3) The ETData File is used to store information about the last transaction for all User IDs (ETIDs) specified in the Additions1 field for an OP command. The idea of specifying ETIDs is to enable the implementation of restart processing for programs using Adabas, following a crash.
(https://documentation.softwareag.com/adabas/ada701luw/basics/dbdesign.htm)

Click on the Database List button to get back to the Databases page.

Click n the Database List to get back to the Databases page.

More about Adabas database file information can be found in the Show Details field under the label Containers and Files.

The Containers and Files buttons in the Show Details field provides access to more information on Adabas database files.

The Containers page is as follows.

Container files are disk files created by Adabas utilities. They are managed by the Adabas nucleus and Adabas utilities. The internal structure of these files is organized and maintained by Adabas, thus permitting the use of very efficient disk usage algorithms. The required container files of an Adabas database are called ASSO, DATA and WORK. For some utilities, additional container files called SORT and TEMP are required. (https://documentation.softwareag.com/adabas/ada701luw/basics/contain.htm)

Click on the Database List button to get back to the Databases page and then from there, click the Files button to view the Adabas File list page as shown below.

Click the EMPLOYEES label in the Name field, and then click the Field definition tab located under the File list table as shown below.

The above screenshot shows that the EMPLOYEE table is made up of two-lettered field names such as A0, AA, AB, AC and so on. This is Adabas style of field name conventions. Some of the fields have specified format such as A, F, B, and W.

The standard format of the field (expressed as a one-character code):
(A) Alphanumeric (left-justified),
(B) Binary (right-justified, unsigned),
(F) Fixed point (right-justified, signed),
(G) Floating (floating, double precision),
(P) Packed decimal (right-justified, signed),
(U) Unpacked decimal (right-justified, signed), and
(W) Unicode.
(https://documentation.softwareag.com/adabas/ada701luw/basics/fdtrec.htm)

Scroll further down to the bottom of the Field definition table. Observe that there are SUPER fields (H1, S2, S3) and SUB fields (S1) records. These fields group the other fields according to the information in the Sub Fields field.

The Flags field contains further information for each fields as listed below.

(DE) Field is to be a descriptor (key).
(FI) Field is to have a fixed storage length; values are stored without an internal length byte, are not compressed, and cannot be longer than the defined field length.
(LA) An alphanumeric or wide-character, variable-length field may contain a value up to 16,381 bytes long.
(MU) Field may contain up to 191 values in a single record.
(NC) Field may contain a null value that satisfies the SQL interpretation of a field having no value; that is, the field’s value is not defined (not counted).
(NN) Field defined with NC option must always have a value defined; it cannot contain an SQL null (not null).
(NU) Null values occurring in the field are to be suppressed.
(NV) An alphanumeric or wide-character field is to be processed in the record buffer without being converted.
(PE) This group field is to define consecutive fields (which may include one or more MU fields) in the FDT that repeat together (up to 191 times) in a record.
(UQ) Field is to be a unique descriptor; that is, for each record in the file, the descriptor must have a different value.
(XI) For this field, the occurrence (index) number is to be excluded from the unique descriptor (UQ)
(https://documentation.softwareag.com/adabas/ada701luw/basics/fdtrec.htm)

Since Adabas classic field names are short (i.e. two-lettered names), it is often useful to define long field names for referencing and programming works, i.e. mapping.

The Adabas REST application mapping page provides more information on the table mapping. It provides a form-based interface for the user to select query parameters. There are four types of views/actions available:

(1) Adabas Map access (http://localhost:8190/#/map),
(2) Adabas classic access (http://localhost:8190/#/database),
(3) Adabas Map Metadata (http://localhost:8190/#/metadata), and
(4) Modify record (http://localhost:8190/#/modify).

A sample of REST requests and responses are provided at the bottom of the pages for reference. Users are recommended to try all these actions in order to understand the features of Adabas Databas mapping.

To be continued in the next part.

— — — —

This post is a part of the series “Getting Started With Adabas & Natural”:
Part 1: Setting up Adabas & Natural Community Edition Docker Version.
Part 2: Accessing Adabas Database via Adabas REST Web app.
Part 3: Adabas “Periodic Groups” and “Multiple Values” representation in JSON data format.
Part 4: Accessing Adabas Database using Adabas TCP-IP Node Package.
Part 5: Creating Natural Project using Natural ONE IDE.
Part 6: Accessing Adabas Database using Natural Programming and Natural ONE IDE.

— — — — —

Sunday, October 23, 2022

What is Node, NodeJS, NPM and NVM?

Node.js is an open-source, cross-platform, back-end JavaScript runtime environment that runs on a JavaScript Engine and executes JavaScript code outside a web browser, which was designed to build scalable network applications. (https://en.wikipedia.org/wiki/Node.js)

Node and NodeJS refers to the same thing.

NPM (originally short for Node Package Manager) is a package manager for the JavaScript programming language maintained by npm, Inc. npm is the default package manager for the JavaScript runtime environment Node.js. (https://en.wikipedia.org/wiki/Npm_(software))

Nvm is a nodejs version manager. It let's you easily install and switch between versions. It retains globally installed packages for each version

Friday, October 14, 2022

Solution To Knime Error (ERROR BERT Model Selector 3:15 Execute failed)

Error Message:

ERROR BERT Model Selector 3:15 Execute failed: An error occurred while trying to launch Python: Could not start Python. There are problems with your Python environment: Library bert is missing.

Solution:

This could be due to certain required libraries missing/not-installed-yet.

Refer the guide in (https://www.knime.com/blog/bert-text-classification-for-everyone#Installation) that says that the following libraries need to be installed into the related Python environment.

For example, if your Python environment is managed by Anaconda/Conda, run Cmd/Terminal window from Anaconda/Conda navigator window as follows:

The full list of required modules are as follows:

bert==2.2.0

bert-for-tf2==0.14.4

Keras-Preprocessing==1.1.2

numpy==1.19.1

pandas==0.23.4

pyarrow==0.11.1

tensorboard==2.2.2

tensorboard-plugin-wit==1.7.0

tensorflow==2.2.0

tensorflow-estimator==2.2.0

tensorflow-hub==0.8.0

tokenizers==0.7.0

tqdm==4.48.0

transformers==3.0.2

Saturday, July 23, 2022

Solutions to Anaconda Jupyter Notebook Kernel Error "No module named 'win32api'"

Error:

(Anaconda Jupyter Notebook Kernel Error )

No module named 'win32api'

Solution:

1) In Anaconda Navigator, install Powershell Prompt

2) Run Powershell Prompt

conda install pywin32

Friday, June 24, 2022

Download Visual Studio 2015 (ISO / Offline Installer + Web Installer)

Download Visual Studio 2015 (Professional and Enterprise)

Visual Studio Enterprise 2015 and Visual Studio Professional 2015 is an integrated, end-to-end solution for teams of any size with demanding quality and scale needs that require comprehensive tools and services for defining, building, and managing complex enterprise applications and solutions targeting Microsoft’s full Enterprise platform as well as cross-platform technologies.

Visual Studio 2015 Professional - Web Installer | ISO Image (Offline Installer)

Visual Studio 2015 Enterprise - Web Installer | ISO Image (Offline Installer)

Download Visual Studio 2015 Community Edition (FREE)

Visual Studio Community 2015 is a free, full-featured IDE with powerful coding productivity features, cross-platform mobile development tools for Windows, iOS, and Android, tools for web and cloud development, and access to thousands of extensions. This edition of Visual Studio is available for free for individual developers, open-source development, academic research, education, and small professional teams.

Visual Studio Community 2015 - Web Installer | ISO Image (Offline Installer)

Microsoft .NET Framework 4.6

The Microsoft .NET Framework 4.6 is a highly compatible, in-place update to the Microsoft .NET Framework 4, Microsoft .NET Framework 4.5, Microsoft .NET Framework 4.5.1, and Microsoft .NET Framework 4.5.2. The web installer is a small package that automatically determines and downloads only the components applicable for a particular platform.

Microsoft .NET Framework 4.6 - Web Installer | .NET Framework (EXE)

https://www.kunal-chowdhury.com/2015/07/download-visualstudio-2015.html

ALTERNATIVE:

Download SQL Server Data Tools (SSDT) for Visual Studio

SSDT for Visual Studio 2022

SSDT for Visual Studio 2019

SSDT for Visual Studio 2017

SSDT for Visual Studio (VS) 2015

SSDT for Visual Studio (VS) 2013

SSDT for Visual Studio (VS) 2012

Applies to: yes SQL Server (all supported versions) Yes Azure SQL Database yes Azure Synapse Analytics

SQL Server Data Tools (SSDT) is a modern development tool for building SQL Server relational databases, databases in Azure SQL, Analysis Services (AS) data models, Integration Services (IS) packages, and Reporting Services (RS) reports. With SSDT, you can design and deploy any SQL Server content type with the same ease as you would develop an application in Visual Studio.

SSDT for Visual Studio 2022

Changes in SSDT for Visual Studio 2022

The core SSDT functionality to create database projects has remained integral to Visual Studio.

Note

There's no SSDT standalone installer for Visual Studio 2022.

Install SSDT with Visual Studio 2022

If Visual Studio 2022 is already installed, you can edit the list of workloads to include SSDT. If you don’t have Visual Studio 2022 installed, then you can download and install Visual Studio 2022.

To modify the installed Visual Studio workloads to include SSDT, use the Visual Studio Installer.

Launch the Visual Studio Installer. In the Windows Start menu, you can search for "installer".
In the installer, select for the edition of Visual Studio that you want to add SSDT to, and then choose Modify.
Select SQL Server Data Tools under Data storage and processing in the list of workloads.

For Analysis Services or Reporting Services projects, you can install the appropriate extensions from within Visual Studio with Extensions > Manage Extensions or from the Marketplace.

The extension for Integration Services projects is not available for Visual Studio 2022 at this time.

Supported SQL versions

Project Templates

SQL Platforms Supported

Relational databases

SQL Server 2016 - SQL Server 2022

Azure SQL Database, Managed Instance

Azure Synapse Analytics (dedicated pools only)

Analysis Services models

Reporting Services reports

SQL Server 2016 - SQL Server 2019

SSDT for Visual Studio 2019

Changes in SSDT for Visual Studio 2019

The core SSDT functionality to create database projects has remained integral to Visual Studio.

With Visual Studio 2019, the required functionality to enable Analysis Services, Integration Services, and Reporting Services projects has moved into the respective Visual Studio (VSIX) extensions only.

Note

There's no SSDT standalone installer for Visual Studio 2019.

Install SSDT with Visual Studio 2019

If Visual Studio 2019 is already installed, you can edit the list of workloads to include SSDT. If you don’t have Visual Studio 2019 installed, then you can download and install Visual Studio 2019 Community.

To modify the installed Visual Studio workloads to include SSDT, use the Visual Studio Installer.

Launch the Visual Studio Installer. In the Windows Start menu, you can search for "installer".
In the installer, select for the edition of Visual Studio that you want to add SSDT to, and then choose Modify.
Select SQL Server Data Tools under Data storage and processing in the list of workloads.

For Analysis Services, Integration Services, or Reporting Services projects, you can install the appropriate extensions from within Visual Studio with Extensions > Manage Extensions or from the Marketplace.

Supported SQL versions

Project Templates	SQL Platforms Supported
Relational databases	SQL Server 2012 - SQL Server 2019 Azure SQL Database, Managed Instance Azure Synapse Analytics (dedicated pools only)
Analysis Services models Reporting Services reports	SQL Server 2008 - SQL Server 2019
Integration Services packages	SQL Server 2012 - SQL Server 2019

Previous versions

To download and install SSDT for Visual Studio 2017, or an older version of SSDT, see Previous releases of SQL Server Data Tools (SSDT and SSDT-BI).

Next steps

After installing SSDT, work through these tutorials to learn how to create databases, packages, data models, and reports using SSDT.

Previous releases of SQL Server Data Tools (SSDT and SSDT-BI)

Applies to: yes SQL Server (all supported versions) Yes Azure SQL Database Yes Azure SQL Managed Instance yes Azure Synapse Analytics yes Analytics Platform System (PDW)

SQL Server Data Tools (SSDT) provides project templates and design surfaces for building SQL Server content types - relational databases, Analysis Services models, Reporting Services reports, and Integration Services packages.

SSDT is backwards compatible, so you can always use the newest SSDT to design and deploy databases, models, reports, and packages that run on older versions of SQL Server.

Historically, the Visual Studio shell used to create SQL Server content types has been released under various names, including SQL Server Data Tools, SQL Server Data Tools - Business Intelligence, and Business Intelligence Development Studio. Previous versions came with distinct sets of project templates. To get all of the project templates together in one SSDT, you need the newest version. Otherwise, you probably need to install multiple previous versions to get all of the templates used in SQL Server. Only one shell is installed per version of Visual Studio; installing a second SSDT just adds the missing templates.

SSDT for Visual Studio 2017

Changes in SSDT for Visual Studio 2017

Starting with Visual Studio 2017, the functionality of creating Database Projects has been integrated into the Visual Studio installation. There's no need to install the SSDT standalone installer for the core SSDT experience.

Now to create Analysis Services, Integration Services, or Reporting Services projects, you still need the SSDT standalone installer.

Install SSDT with Visual Studio 2017

To install SSDT during Visual Studio installation, select the Data storage and processing workload, and then select SQL Server Data Tools.

If Visual Studio is already installed, use the Visual Studio Installer to modify the installed workloads to include SSDT.

Launch the Visual Studio Installer. In the Windows Start menu, you can search for "installer".
In the installer, select for the edition of Visual Studio that you want to add SSDT to, and then choose Modify.
Select SQL Server Data Tools under Data storage and processing in the list of workloads.

Install Analysis Services, Integration Services, and Reporting Services tools

To install Analysis Services, Integration Services, and Reporting Services project support, run the SSDT standalone installer.

The installer lists available Visual Studio instances to add SSDT tools. If Visual Studio isn't already installed, selecting Install a new SQL Server Data Tools instance installs SSDT with a minimal version of Visual Studio, but for the best experience, we recommend using SSDT with the latest version of Visual Studio.

Select AS, IS, RS

Supported SQL versions

Project Templates	SQL Platforms Supported
Relational databases	SQL Server 2005* - SQL Server 2017 Azure SQL Database Azure Synapse Analytics (supports queries only; database projects aren't yet supported) * SQL Server 2005 support is deprecated, move to an officially supported SQL version
Analysis Services models Reporting Services reports	SQL Server 2008 - SQL Server 2017
Integration Services packages	SQL Server 2012 - SQL Server 2019

SSDT for VS 2017 (standalone installer)

Download SSDT for Visual Studio 2017 (15.9.10)

Important

Before installing SSDT for Visual Studio 2017 (15.9.10), uninstall Analysis Services Projects and Reporting Services Projects extensions if they are already installed, and close all VS instances.
Removed the inbox component Power Query Source for SQL Server 2017. Now we have announced Power Query Source for SQL Server 2017 & 2019 as out-of-box component, which can be downloaded here.
To design packages using Oracle and Teradata connectors and targeting an earlier version of SQL Server prior to SQL 2019, in addition to the Microsoft Oracle Connector for SQL 2019 and Microsoft Teradata Connector for SQL 2019, you need to also install the corresponding version of Microsoft Connector for Oracle and Teradata by Attunity.

Release Notes

For a complete list of changes, see Release notes for SQL Server Data Tools (SSDT).

System requirements

SSDT for Visual Studio 2017 has the same system requirements as Visual Studio.

Available Languages - SSDT for VS 2017

This release of SSDT for VS 2017 can be installed in the following languages:

Considerations and limitations

You can’t install the community version offline
To upgrade SSDT, you need to follow the same path used to install SSDT. For example, if you added SSDT using the VSIX extensions, then you must upgrade via the VSIX extensions. If you installed SSDT via a separate install, then you need to upgrade using that method.

Offline install

To install SSDT when you’re not connected to the internet, follow the steps in this section. For more information, see Create a network installation of Visual Studio 2017.

First, complete the following steps while online:

Download the SSDT standalone installer.
Download vs_sql.exe.
While still online, execute one of the following commands to download all the files required for installing offline. Using the --layout option is the key, it downloads the actual files for the offline installation. Replace <filepath> with the actual layouts path to save the files.
a. For a specific language, pass the locale: --lang. A single language is ~1 GB in size.
dos
Copy

vs_sql.exe --layout c:\<filepath> --lang en-us

b. For all languages, omit the --lang argument. All languages are ~3.9 GB.
dos
Copy

vs_sql.exe --layout c:\<filepath>

After completing the previous steps, the following steps below can be done offline:

Run this command to install the VS2017 Shell and SQL Server Data Project.
dos
Copy

vs_setup.exe --NoWeb

Run this command to install SSDT
a. For an interactive installation, from the layouts folder, run this command and select SSIS/SSRS/SSAS
dos
Copy

SSDT-Setup-ENU.exe /install

b. For an unattended installation, run this command
dos
Copy

SSDT-Setup-ENU.exe /INSTALLALL[:vsinstances] /passive

c. For an unattended installation to a specific VS Instance that you may have previously installed, you can query the instance ID of the desired VS instance
dos
Copy

cd C:\Program Files (x86)\Microsoft Visual Studio\Installer

C:\Program Files (x86)\Microsoft Visual Studio\Installer> vswhere.exe -all

Then run this command by replacing the VS_INSTANCE_ID_HERE with your instanceID (it will look something like this: 49cf420b)
dos
Copy

SSDT-Setup-ENU.exe /INSTALLALL[:VS_INSTANCE_ID_HERE] /passive

For available options, run SSDT-Setup-ENU.exe /help

Note

If using a full version of Visual Studio 2017, create an offline folder for SSDT only, and run SSDT-Setup-ENU.exe from this newly created folder (don’t add SSDT to another Visual Studio 2017 offline layout). If you add the SSDT layout to an existing Visual Studio offline layout, the necessary runtime (.exe) components are not created there.

Previous SSDT releases

Download previous SSDT versions by selecting the download link in the related section.

SSDT version	Visual Studio version
15.8	2017
17.4	2015
16.5	2013
11.1.50727.1	2012