DEV Community: sindhu cynixit

Integration In PEGA-PRPC

sindhu cynixit — Fri, 09 Oct 2020 07:22:07 +0000

Pega/PRPC is a popular rules engine and BPM tool from Pega systems that is gaining a good market share among large corporations. Architects and developers build the Pega/PRPC instance while administrators and even select business analysts have the option of changing workflow rules during runtime. In fact, their motto itself is "Build for change".

The goal is to "eliminate software coding" and "automate manual work" to the minimum and build complex systems at the enterprise level with features right out-of-the-box.

That's how it works in the utopian world. But in the real world, you need good developer support. So the lesser the code, the closer you are to the goal of a true BPM tool. Software coding might be reduced drastically.

But you still need people with a development background using inputs from Business Analysts to make changes or add functionality. Pega/PRPC is pretty expensive so they primarily target any corporation that can afford such a luxury.

To get in-Depth knowledge on Pega CSA you can enroll for a live demo on pega cssa certification.

Most applications require access to data that is provided by another system, or they need to respond to requests from other systems for data or computations. Process Commander provides integration facilities that support interactions between its applications and external systems, databases, Web sites, e-mail servers, and so on.

In Integration situations, a Process Commander application can act as either the client or the server, communicating with both back-end and front-end applications.

By using these features, Process Commander can exchange information with many kinds of external systems like

Take your career to new heights of success with pega cssa training

Relational databases
Enterprise Information Systems (EIS)
e-mail servers
Excel spreadsheets
Text files

Process Commander interfaces support a wide range of technologies and standards, including

HTML
Simple Object Access Protocol (SOAP)
Microsoft .NET
Sun Microsystems Enterprise JavaBeans (EJB)
IBM WebSphere MQ® messaging
Java Message Service (JMS)
J2EE Connector Architecture (JCA)
Business Process Execution Language (BPEL)
JSR 94
JSR 168

These interfaces are called integration services

TYPES OF INTEGRATIONS IN PEGA-PRPC

Process Commander offers many approaches, technologies, and facilities collectively known as Integration. They include:

• Connector

• Service

Internally, these facilities are in the Pega-IntSvcs RuleSet

DATA MAPPING IN PEGA-PRPC

When you configure a service or a connector you also match or correlate the properties in the process commander application to the corresponding data fields or properties in the external system. This is called Data mapping.

To learn more about Pega CSA and other great features of Pega, you can visit our website Pega cssa certification training

Advantages of Pega RULES Process Commander

BPM products that focus primarily on workflow or integration capabilities, Process Commander leverages the PegaRULES engine to enable organizations to manage complex business processes -- including those with a large number of exceptions, or those where tasks, sub-tasks, or decisions have to be delegated to many individuals across (and beyond) the enterprise.

In addition, since changes to business processes can be made by modifying or adding business rules (either via a Microsoft-Visio-based editor or browser-based HTML forms), Process Commander makes it possible for business analysts and power users to customize a business process.

For example, business analysts can diagram a business process using Microsoft Visio. Visio serves as the graphical front end to Process Commander's rulebase and dynamically communicates with the rulebase to select, validate, and save processes.

By placing Process Commander SmartShapes on a Visio worksheet, business analysts can link activities together to create an automated process. Visio then presents the visual form of the flow and, based on the SmartShape that is utilized, the PegaRULES Engine automatically presents the correct rule form.

As a result, Visio diagrams utilized in Process Commander are "live" diagrams -- empowering business managers to evolve and define how processing applications work in real-time as they modify these diagrams on-the-fly. Versioning capabilities also enable business users to adjust to changing business requirements and quickly implement required processes.

The Process Commander server runs on multiple operating systems, including Windows, Solaris and AIX, and utilizes leading applications servers including IBM WebSphere, BEA WebLogic and Apache Tomcat.

Process and business rules reside in a common rulebase, which may run on Oracle, Microsoft SQL and IBM DB2 relational databases. This combination of a distributed server architecture and centralized rulebase running in heterogeneous environments provides a range of scalability and deployment options.

Additional features of Process Commander include:Browser Interface: Used for all development and application functions.Support of Complex Processes: Includes a wide variety of assignment, worklist, process and reporting functions to improve work efficiency.Service Level Agreements: Enable users to manage actions and prioritize work.

In addition to these capabilities, Process Commander supports Directed Web Access, which enables customers or users outside of an organization's firewall to contribute to a process. For example, a customer could be directed to a one-time secure Web URL where they could fill out a request for service or similar form. All rules and processes within the system can also be exposed as Web services, enabling other applications to access or invoke them as appropriate.

Node.js vs Java

sindhu cynixit — Tue, 31 Mar 2020 09:55:32 +0000

Used by millions of developers all over the globe, Java has remained one of the most popular programming languages for the last 22 years. Still, JavaScript holds the title of the most widely deployed language in the world, and its surrounding environments such as runtime like Node.js are gaining traction as well.

In fact, industry giants like eBay, LinkedIn, Groupon, Uber, and Netflix have been choosing Node.js over other solutions for building web applications.

So how does this newbie on the developer scene compare to a strong language like Java? Read on to find out.

To get in-Depth knowledge on Nodejs you can enroll for a live demo on Nodejs online training

Java and Node.js: the basics

Java is a general-purpose, object-oriented, platform-independent, portable, and robust interpreted programming language, which was designed to be used in the distributed environment of the Internet. Java code can run on any Java Virtual Machine, which offers developers a lot of flexibility. Today, you will find Java in web and mobile enterprise applications – but also in smart cards, games, embedded systems, and even robotics.

Node.js is a JavaScript runtime built on Chrome's V8 JavaScript engine, appreciated for its amazing performance and scalability. According to the 2017 survey by the Node.js Foundation, today Node.js is primarily used in web applications, enterprise applications, Big Data & analytics solutions, and embedded systems.

Take your career to new heights of success with Nodejs Course

If you're choosing between Java and Node.js, here are the key pros and cons you should take into account.

Java: pros and cons

Pros

A rock-solid foundation thanks to over 20 years of engineering;
A vast ecosystem of libraries developers can use to increase the speed of development;
Java Virtual Machine, which offers excellent stability thanks to its large number of unit tests;
Quality IDEs (Integrated Development Environments) and a collection of monitoring and debugging tools that are mature and ready for deployment, making developers' lives easier and their apps bug-free;
Proven tools such as Eclipse, NetBeans, or IntelliJ, which are integrated with servers, debuggers, and decompilers (plus a solid ecosystem of plug-ins), all of which make the development process faster;
With the right framework or thread-models that are part of the latest Java frameworks, it's possible to boost the speed of development to match the one of Node.js’s;
Incredible computation efficiency;
Great code maintainability.

Cons

The slow development process;
Works best if the code is clean and straightforward – if it deadlocks, your risk that the entire server locks up;
Configuring tools can take a lot of time;
Code migration might become an issue if you decide to move your business logic written in Java to the browser (in that case, you'll need to rewrite your code in JavaScript).

Get More Info Regarding NodeJS Certification

When to choose Java?

Applications that are CPU intensive or CPU bound will benefit from Java. The same goes for applications with a vast code base – since Java provides strongly typed sources, refactoring it and bug fixing will be more straightforward during its maintenance. If your application uses RDBMS (Relational Database Management System), Java will be a great pick – it includes tools that provide multi-database support for object-relational mapping to make configuration easier when you switch to another database.

Node.js: pros and cons

Pros

A gentle learning curve for those who already know JavaScript;
Fast development – since frameworks and libraries do plenty of work, developers can build software much faster in JavaScript, and Node.js projects generally compile very quickly;
Offers a reactive style out of the box (something that's far more complicated in Java);
Includes a code re-use feature – that’s what makes Node.js so popular among developers, as it seriously boosts their productivity;
Provides developers with an opportunity to use JavaScript on server and client side – developers don’t need to learn a new syntax.

Cons

Lack of IDEs – Node.js developers type code in text editors equipped with plugins, which is great, but a far cry from Java’s IDEs that make developers’ job easier;
The JavaScript ecosystem isn't as mature and reliable as the Java ecosystem.

When to choose it

Node.js is perfect for web apps, mobile apps, real-time applications (instant messaging, live chat), online gaming apps, e-commerce transaction software, and much more. It's also a good choice if you're dealing with microservice architecture, which can lay the foundation for advanced systems – bear in mind that apps like Netflix or Uber were built using Node.js.

Java or Node.js?

Theoretically, it's possible to avoid making that choice. For example, you can develop an application in Java and link it with JavaScript through an engine like Rhinorun.

However, in a real-world scenario, picking Node.js for your web application makes more sense.

It's just faster and more scalable than Java when it comes to web apps. It also offers top performance. The growth of Node.js among the industry giants indicates its versatility too. Node.js is far more than an application framework – it's also used in corporate data software, rapid application modernization projects, and IoT solutions.
To get in-Depth knowledge on Java you can enroll for a live demo on Java Online Training

How to Build a Search Bar in React with React Hooks

sindhu cynixit — Sat, 21 Mar 2020 06:00:33 +0000

Below is a small gif of what we will be building. A simple search box that allows us to search through a contact list. We would be using functional components rather than class-based components to achieve this.

Let’s start!
Create a new react app using

npx create-react-app contacts-list

Then navigate into the contacts-list directory. Open the directory in your favourite code editor. In my case, I’m using vscode, so all I need to do from the command line is used:

code .

In your src directory, create a new folder called components and within that create a Numbers.js file.

Head over to your App.js file and import your Numbers.js component.

Next, we need to create a few persons that we would then pass down as props for our Numbers.js component to render.

To get in-Depth knowledge on Reactjs you can enroll for a live demo on Reactjs Online Training

Now, in our Numbers component, we would receive the props being passed down from App and use that to display the contacts list.

See the code below with explanations for each step added as comments.

Take your career to new heights of success with Reactjs Training

Finally, we return the updated information from FilterDisplay each time it’s updated.

If you’re like me and would like to break out your Search bar into a separate component, then read on. Let’s refactor this baby! Breaking out our search into a separate component would allow us use the same search bar in other components within our application.

First, we will create a Filter component, let’s call this Filter.js inside our components folder. it’ll take 2 props. Props for the input value and for an onChange event.

Next, we need to refactor our Numbers.js component so that all it does is to render the filtered persons list. It’ll accept one prop — the list/array.

Recall that all our state is being managed within our App component and being passed down to our components as props.

Finally, in our App component, we will pass a stateful value to the input field in the Filter component, we would also pass a handleChange method that gets called when there is a change within the input field.

Within our return, our Numbers component will always check if the input field is blank. If it’s, we render the original Persons array else we render the list based on what’s entered in the input field.

To learn more about the Features of React.js, you can enroll for a live demo on Reactjs Certification Course

Node.js Process Model

sindhu cynixit — Wed, 18 Mar 2020 10:35:54 +0000

In this article, we will learn about the Node.js process model and understand why we should use Node.js.

Traditional Web Server Model
In the traditional web server model, each request is handled by a dedicated thread from the thread pool. If no thread is available in the thread pool at any point of time then the request waits till the next available thread. The dedicated thread executes a particular request and does not return to thread pool until it completes the execution and returns a response

To get in-Depth knowledge on Nodejs you can Enroll for a live demo on Nodejs online training

Node.js Process Model

Node.js processes user requests differently when compared to a traditional web server model. Node.js runs in a single process and the application code runs in a single thread and thereby needs fewer resources than other platforms. All the user requests to your web application will be handled by a single thread and all the I/O work or long-running job is performed asynchronously for a particular request. So, this single thread doesn't have to wait for the request to complete and is free to handle the next request. When asynchronous I/O work completes then it processes the request further and sends the response.

An event loop is constantly watching for the events to be raised for an asynchronous job and executing callback function when the job completes. Internally, Node.js uses libev for the event loop which in turn uses an internal C++ thread pool to provide asynchronous I/O.

To learn more about Node.js Process Model and other great features of Nodejs, you can Enroll for a live demo on Nodejs Course

The following figure illustrates the asynchronous web server model using Node.js.

Node.js process model increases the performance and scalability with a few caveats. Node.js is not fit for an application which performs CPU-intensive operations like image processing or other heavy computation work because it takes time to process a request and thereby blocks the single thread.

Take your career to new heights of success with Nodejs Certification

What is a Kubernetes Pod?

sindhu cynixit — Sat, 15 Feb 2020 07:13:58 +0000

In this article, I’m going to provide an explanation for Kubernetes pods, use cases, and lifecycle, and how to use it to deploy an application. This article assumes you recognize the purpose of the Kubernetes and you’ve got minikube and kubectl installed.

What is a pod in K8S?

Of object models in Kubernetes, the pod is the smallest building block. inside a cluster, a pod represents a system that’s running. The inside of a pod may have one or greater containers. Those within a single pod share:

A unique network IP
Network
Storage
Any additional specifications you’ve applied to the pod

To get in-Depth knowledge on Kubernetes you can enroll for a live demo on
kubernetes online training

Another way to think of a pod — a “logical host” that is specific to your application and holds one or more tightly-coupled containers. For example, say we've got an app-container and a logging-container during a pod.

The only job of the logging-container is to tug logs from the app-container. Locating your containers in a pod eliminates extra communication setup because they are co-located, so everything is local and they share all the resources. This is an equivalent thing as execution on an equivalent physical server during a pre-container world.

There are other things to do with pods, of course. You might have an init container that initializes a second container. Once the second container is up and serving, the first container stops — its job is done.

Pod model types

There are two model types of pod you can create:

One-container-per-pod: This model is the most popular. The post is that the “wrapper” for one container. Since pod is that the smallest object that K8S recognizes, it manages the pods rather than directly managing the containers.
Multi-container-pod: during this model, a pod can hold multiple co-located containers that are tightly coupled to share resources. These containers work as a single, cohesive unit of service. The pod then wraps these multi containers with storage resources into one unit. Example use cases include sidecars, proxies, logging.

Take your career to new heights of success with kubernetes training

Each pod runs one instance of your application. If you would like to scale the app horizontally (such as running several replicas), you’ll use a pod per instance. this is often different from running multiple containers of an equivalent app within one pod.

It is worth mentioning that pods aren’t intended as durable entities. If a node fails or if you’re maintaining nodes, the pods won’t survive. to unravel this issue, K8S has controllers — typically, a pod is often created with a type of controller.

Pod lifecycle phases

A pod status tells us where the pod is in its lifecycle. it’s meant to offer you thought not surely, therefore it’s good practice to debug if pod doesn’t come up cleanly. The five phases of a pod lifecycle are:

Pending: The pod is accepted, but a minimum of one container image has not been created.
Running: The pod is sure to a node, and every one container is created. One container is running or in the process of starting or restarting.
Succeeded: All containers within the pod successfully terminated and can not restart.
Failed: All containers are terminated, with at least one container failing. The failed container exited with a non-zero status.
Unknown: The state of the pod couldn’t be obtained.