ServiceNow connector deployment guide 1.0.0.0

ServiceNow LDAP Integration

ServiceNow LDAP Integration:

Step 1: Login using admin account and Search For LDAP in search filter left side of panel and Click on Create new Server.

Step 2:

  • Select Type of LDAP server as Active Directory
  • Give any server Name (eg. Company_name LDAP)
  • Give Your Server URL of Your Active Directory.
  • Click on Submit

Step 3:

-In Next screen it will ask you to enter Login Distinguish Name (DN) and Password ( LDAP service account credentials ).

– Starting search directory: is the path in where you are going to search users .

– Once done with all these fields click on test connection to check it is connecting successfully or not. (It will show message at top)

 

  • Once Connection is Successful the right click on top and save it.

Step 4:

Next Step is to set LDAP OU Definitions for Users and Groups:

For that scroll down on same screen you will see the section for LDAP OU Definitions having pre-define definitions for user and groups.

  • Click on Users
  • This below screen will be open in that RDN and Query field you have to keep it empty and only you have to give filter to isolate users here I am giving uid=* it will take all users from user id.

After that test connection for OU definition:

  • You can click on brows to see records:

All records which are present in AD are fetched here

 

 

Step 5:

After Setting LDAP OU Definitions next is Data Sources

  • In data sources we load our AD records in ldap table and transfer that records in particular Service now tables.

For this configuration scroll down on same OU definition screen:

Click on this generated Data Source then following screen will appear.

  • You have to give any name to Import set table name field in this table we are first going to load our AD records. ( eg. Import set table name = Mytable_ldap_import)it will automatically generate name by prefix “u_ Mytable_ldap_import”

  • Then by clicking test load 20 records you can test records are loading or not. You will get this success message and how much records are inserted or updated and error logs also.

  • Click on Return to data source to get back to our configurations on data sources. And click on load all records it will load all AD records in our ldap table which we have created (u_Mytable_ldap_import) we have create above.

 

  • You will get this import success message it means All the records from AD are loaded in our ldap table.

  • You can check those records are inserted or not in table . On top left side there is search filter put your table name (eg.u_ Mytable_ldap_import.list)

 

Step 6:

Next step is to create transform map to navigate that again navigate to data sources select our data source and there is section Transforms click on New

  • Transform Maps are for transferring data from Source table to destination table.
  • Here source table is our ldap table which we have created and stored records from AD and target table is ServiceNow table in which we want to store our data.

 

 

  • Fields we have to fill:
    • Name: give any name for you transform map.
    • Source table: is automatically selected.
    • Enforce mandatory: options like which fields you want to transfer All fields, only mapped. You can select as per requirement.
    • On right side there is field target table: here you have to select target table in which you are going to transfer records as we are transferring users then it must go in users table of ServiceNow so select sys_users as target table.

 

  • If you are selecting only mapped Fields option in Enforce Mandatory Fields the you have to map fields of source table with target table by clicking Mapping Assist.
  • You will see following screen left side source table fields and right side target table fields.
  • You have to just add fields from source table and target table from which to field data should be transfer.(eg. Here I am Mapping 3 fields as shown in following screenshot)
  • After mapping click on save.
  • You will be able to see those fields .

 

Step 7:

Next step is To transform Source table records in target table(ServiceNow users table). For that click on transform  link is available on table transform map screen.

  • After that following screen will appear. You have to just click on transform

 

 

-It Will Show success Message for transformation. It means all records are transferd from source table to targeted table. There is link transform history you can check whether it is successful with errors or not. And how many records are inserted, updated all status.

  • You can check in ServiceNow users table. Top left side in search filter search for users.
  • You can see 3 records which were available in AD are inserted here in user table of ServiceNow

 

Finally all Steps are done you have successfully imported all records from you AD to ServiceNow.

LDAP integration is done with ServiceNow.

 

ServiceNow connector deployment guide 1.0.0.0

Difference Between the Liferay 6.2 and Liferay 7/DXP

  1. Basic Difference Between the Liferay 6.2 and Liferay 7/DXP

Sr.No

Parameters

Liferay 6.2

Liferay 7/DXP

1.

Modularity Development

Liferay 6.2 partially support and it’s an experiment and it need more effort to achieve the modularity.

Liferay 7 support modularity development using OSGi framework.

2.

Bootstrap Version

Support Bootstrap 2 UI framework.

Liferay 7 support Bootstrap 3 UI framework.

3.

AUI Version

AUI 2.x components are used.

AUI 3.x components are used.

4.

Application Development

Liferay Application Development based on Plugins.

Liferay Application Development based on OSGi bundles.

5.

Enterprises Editions name

We simply call Liferay 6.2 EE or CE

Liferay 7 EE called Liferay DXP

6.

Application Packaged method

Liferay Applications packaged as war files and deployed in traditional application server.

Liferay Applications packaged as OSGi bundle jar files and deployed in OSGi container. It support WAR deployment as well.

7.

Isolation

Liferay 6.2 core portal and its default portlets all available in ROOT directory and deployed in Application Server.

Liferay 7 separate core portal and its default portlets. Core portal only have core features rest of features made it as portlets and packaged as bundles. Core portal files in ROOT directory deployed in Application Server. All portlet bundles available in data/OSGI directory. It means bundles deployed in OSGi container.

8.

Search Engine

Liferay 6.2 in built search engine is Apache Lucene. Liferay 6.2 have SOLR web to enable SOLR search.

Liferay 7 inbuilt search engine Elastic Search. It support SOLR search as well.

9.

Single Page Application

Liferay 6.2 does not have inbuilt Single Page Application support but we can integrate SPA framework to achieve it.

Liferay 7 have Single Page Application inbuilt support using Senna.js

10.

Build tools Support

Liferay 6.2 support MAVEN, ANT.

Liferay 7 support MAVEN, GRADLE build tools.

11.

Application development tools.

Liferay 6.2 have Plugins SDK Command Line Interface to create portlet, hook, theme and layout.

Liferay 7 introduce new tool called BLADE CLI to develop Liferay 7 Application as bundles. Internally its uses the Build tools GRADLE flavor.

12.

Activate/Deactivate Application

Liferay 6.2 it is not possible. We should un-deploy the plugins from the server so that we can remove the unused features.

We can activate/deactivate Liferay Application Bundles simply using Apache Gogo shell Command Line Interface without un-deploy the bundle from the container.

13.

Languages For UI

Liferay 6.2 does not have design languages like Clay and Lexicon. But it supports all necessary UI Languages like HTML, CSS, Bootstrap, JQuery, Alloy-UI etc

Liferay 7 have introduced Clay and Lexicon language to design UI. Lexicon is a design language that provides a common framework for building interfaces. Clay is web implementation of Lexicon.It’s built with HTML, CSS, and Javascript with Bootstrap as a foundation

14.

Flexibility

Not So flexible environment, we need to perform code changes for any single change. like We cannot deactivate default portlets without change in the code.

Provide more flexible environment like We can easily deactivate default portlets if we are not using. We simply deactivate portlet bundle.

 

 

 

ServiceNow connector deployment guide 1.0.0.0

Why ServiceNow Leading ITSM from past 4 years as per granter Magic Quadrant.

The main aim of ServiceNow is to make work easier and in fastest way.

It helps to reduce manual IT work like unstructured work, eliminating the back and forth emails, phone calls and the processes that waste time, money, and sap productivity. It brings automation in every process of organization i.e. entire enterprise—HR, customer service, security, and beyond—can tap into the power of the Now Platform to create a better experience for employees, users, customers, and transform the way work is done.

 

  1. ServiceNow has Intelligent Automation Engine at Knowledge17 to bring machine learning to everyday work.
  2. It has used DxContinuum as a core technology for that engine.
  3. Also it applying artificial intelligence to routine service desk conversations with Qlue’s virtual agent messaging capabilities will enhance customer experiences.

Below are the features of ServiceNow to recognize as a Leader in ITSM.

Automation:

Automation/Orchestration is about aligning the business request with the applications, data, and infrastructure in fastest way and reduce manual dependency. Task associates with workflow to trigger and response in scheduler manner.

Business transformation

It fulfil the requirement of each audience. It became one of the leading business advisor.

It has create its own value with the design thinking power. Turn digitalization to its opportunity. I has goal for enterprise with business strategists.

Change management

So many enhance and new features added in change management such as Email notification, Auto Add Agenda Decisions in change Adversary board (CAB), meeting notes, checking features of workbench.

Cloud Architecture

Ø  The ServiceNow cloud is built on an advanced architecture called multi-instance.

  • A multi-instance architecture gives every customer its own unique database, which reduce Data cloning with other user. The multi-instance architecture is not built on large centralized database software and infrastructure. Instead, everything deploy on instances on a per-customer basis, allowing the multi-instance cloud to scale horizontally and infinitely. For multi-instance cloud, data deploy separate application logic (Apache Tomcat Java Virtual Machines) and database processes (MySQL) for every customer.
  • Each customer instance is a unique software stack and this means that, unlike some competing platforms, there is no 70-page document of restrictions and limitations. User instances in SNOW cloud are for individual enterprise and individual business needs. With this architecture and deployment model comes a wealth of benefits; true data isolation, advanced high availability and customer-driven upgrade schedules.
  • Unique customer instances far easier to perform and issues can be resolved on a customer-by-customer basis, which is called true data isolation.
  • Also individual instance can upgrade so fastly as no dependency and data collaborated with other instance which is very fastest process.

Cloud Operations

Ø  As the demand for cloud services grows. It becomes a big challenges in maintaining service level standards as well as controlling the risks and costs to the organization. So, Today’s IT leaders must have a way to meet these needs, while at the same time get to the cloud faster. To achieve success, they must have a standard operating approach to both their hybrid and public clouds without slowing down service innovation.

Ø  ServiceNow Cloud Management solution gets you to the cloud faster by allowing you to deliver enterprise‑class services faster, without runaway costs, user complexity or increased risks. Virtual Provisioning Cloud Administrator, Virtual Provisioning Cloud Approver, Virtual Provisioning Cloud Operator, Virtual Provisioning Cloud User

Cloud security

  • As a customer, your instance is hosted in the SaaS environment. Which has “Private” environment only hosting subscription service. Also same time the instance is logically separated from all other tenants in our cloud environment because of multi‑instance architecture.

Enterprise cloud

Ø  Enterprise Cloud Computing refers to a computing environment residing behind a firewall that delivers software, infrastructure and platform services to an enterprise. The unique, multi‑instance architecture ensures that, as a customer, you can fully customize cloud services and perform upgrades on your own schedule. Highly secure, the Nonstop Cloud conforms to the highest levels of compliance and global regulations.

HR service management

Ø  ServiceNow HR Service Management improves HR service delivery by offering a consumer‑like self‑service portal to employees along with out‑of‑the‑box request and fulfill process automation. An HR service catalog presents employees with pre‑defined services such as benefits or employee relations items. Once requests are submitted through the HR service catalog, cases are automatically assigned to a designated human resources specialist or team for fulfilment. Integrated reporting provides insight into volume, types of requests, and individual workloads which improve both services and HR operations.

Innovation

Ø  Now, IT is expected to align with the business and become an equal partner in business success—increasing productivity, unlocking new revenues, and powering competitive advantage. Based upon growing demand the SNOW has its innovative idea to fulfill user’s demand.

IT Integration

Ø  ServiceNow integrates with many third party applications and data sources.

Ø  The most common integrations are with CMDB, Incident Management, Problem Management, Change Management, User Administration, and Single Sign-on. A variety of techniques can be used, most notably Web Services, JDBC, LDAP, Excel, CSV, and Email, as well as any industry standard technologies that use SOAP, REST, or WSDL. Additionally, API and command-line integrations can be done using a MID Server. ServiceNow has performed the following integrations with enterprise systems and platforms, which means it extends integration scope with almost all the third party.

IT service management

Ø  Deliver IT Service Management on a single, cloud-based platform. Asset management, contract management,Procurement,Product Catalog,Benchmarks,Change management, Expense Line, Incident Management,ITSM Guided Setup, on-call scheduling, Problem Management, Request Management, Service Catalog, Service Desk, Service Level Management, Service Portfolio Management,ITSM Performance Analytics Solutions, HR Service Management, Field Service Management, Legal Service Management, Finance Service Management, Marketing Service Management, Security Operations, Customer Service Management, Application Development.

Ø  Using our ServiceNow Developer Suite helps you meet the demand for custom business applications that enable you to provide business services. With a rich set of pre‑built services and templates, you can quickly build, test and publish applications that can span from a single department to your entire enterprise. And because minimal to no coding is required, almost anyone can build business applications for every line of business and department.

Service management

Ø  Create a modern work environment by placing a service‑oriented lens on the activities, tasks and processes that make up day‑to‑day work life. This service model enables enterprise service domains to define services, provide an intuitive service experience, deliver service, assure service availability and analyse critical service metrics. It replace legacy mailing chain and spreadsheet.

Ø  With ServiceNow Service Management, you can refine, structure and automate the flow of work to streamline service delivery. It connects provider and requestor.

Ø  Our customers have standardized on ServiceNow for enterprise‑wide service management — applying the service model to many different use cases outside of IT, into the broader enterprise and beyond. IT, HR, facilities, field service and other service domains use our model to manage all of the service relationships that make up the contemporary workplace.

 

Human Resources Management

ServiceNow HR Service Management streamlines and improves HR service delivery by offering a consumer‑like self‑service portal to employees along with out‑of‑the‑box request and fulfill process automation. An HR service catalog presents employees with pre‑defined services such as benefits or employee relations items. Once requests are submitted through the HR service catalog, cases are automatically assigned to a designated human resources specialist or team for fulfilment. Integrated reporting provides insight into volume, types of requests, and individual workloads so that HR management can align services and resources, and identify opportunities to improve both services and HR operations.

IT operations management

IT Operations Management (ITOM) encompasses a set of capabilities for ensuring that enterprise infrastructure and applications are optimized and always available for the business. ServiceNow ITOM enables infrastructure, applications, and processes to be managed in a highly automated – and service‑centric – manner.

Governance

Continuous monitoring and real time dashboard provide actionable information about high impact risks, vendor status, noncompliance and significant audit finding.

Employees Service Experience

  • PROVIDE INSTANT ANSWERS TO QUESTIONS
  • ALLOW EMPLOYEES TO REQUEST ANY HR SERVICE
  • AUTOMATICALLY ROUTE CASES TO THE RIGHT PEOPLE
  • ORCHESTRATE ACTION ACROSS MULTIPLE DEPARTMENTS
  • PROVIDE A CONSUMER-LIKE SERVICE EXPERIENCE
ServiceNow connector deployment guide 1.0.0.0

Integrate KeyCloak with OpenDJ LDAP

 

  1. Login keycloak server in administrator mode.
  2. Select the realm Demo
  3. Click on User Federation tab.

 

  1. Select ldap from drop down list. You will redirected to Add user federation provider page.

 

  1. Fill the following data :

 

Edit Mode                  –          Select Writable

            Vendor                        –          Other

            Connection URL       –          ldap://<localhost>:1389

            Users DN                    –          dc=example,dc=com

            Bind DN                     –          cn=Directory Manager

            Bind Credential         –          Opendj Password

 

            Cliclk on Test connection.    

  1. Click on Save.
  1. Register new account to Demo realm.
  2. You will be able to see your created user in keycloak User List.

 

  1. You will also able to see your created user in OpenDJ.

 

 

 

 

ServiceNow connector deployment guide 1.0.0.0

KeyCloak SAML SSSO with WordPress

This blog discusses about the wordpress SAML SSO woth KeyCloak IAM

  1. Start wordpress install miniOrange SSO using SAML 2.0 plugin.
  2. Start keycloak server in administartor mode.
  3. In your Keycloak admin console, select the realm that you want to use.
  4. From left menu, select Clients.

 

  1. Create a new client/application. Configure the following:

 

Client ID                                –           The SP-EntityID / Issuer from the wordpress plugin under                                        Identity Provider tab

Name                                      –           Provide a name for this client (Eg. WordPress)

Description                            –           Provide a description (Eg. WordPress site)

Enabled                                  –           ON

Client Protocol                      –           SAML

Include AuthnStatement      –           ON

Sign Documents                    –           ON

Sign Assertions                      –           ON

Signature Algorithm             –           RSA_SHA256

Canonicalization Method     –           EXCLUSIVE

Force Name ID Format        –           ON

Name ID Format                   –           Email

Root URL                              –           The ACS (Assertion Consumer Service) URL from the                                                          wordpress plugin under Identity Provider tab.

Valid Redirect URIs              –           The ACS (Assertion Consumer Service) URL from the                                                          wordpress plugin under Identity Provider tab.

 

  1. Under Fine Grain SAML Endpoint Configuration, configure the following:

 

Assertion Consumer Service –         The ACS (Assertion Consumer Service) URL from the        POST Binding URL                            wordpress plugin under Identity Provider tab.

 

  1. Click on Save.

 

 

  1. Configuring WordPress as SP in WordPress

 

  1. Go to,

http://<YOUR_DOMAIN>>/auth/realms/{YOUR_REALM}/ protocol/ saml/ descriptor.           This will open an XML in the browser.

 

  1. In miniOrange SAML plugin, go to Service Provider Tab. Enter the following values:

Identity Provider Name   –           Keycloak

IdP Entity ID or Issuer     –           Search for entityID. Enter it’s value in this textbox.

SAML Login URL            –           Search for SingleSignOnService Binding=                                                                                                      “urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect”.                                          Enter the Location value in the textbox.

X.509 Certificate               –           Enter the X509Certificate tag value in this textbox

 

  1. In miniOrange SAML plugin, go to Attribute/RoleMapping tab. Enter the following values:

 

Username         –              Name of the username attribute from IdP (Keep NameID by default)

Email                –              Name of the email attribute from IdP (Keep NameID by default)

FirstName        –              Name of the firstname attribute from IdP

LastName        –               Name of the lastname attribute from IdP

 

  1. Under the Role Mapping section, configure which GROUP value coming in the SAML response needs to be mapped to which role in WordPress. The Group value coming in the SAML response will be mapped to the Role assigned here and the user will be assigned that role in WordPress.

Keep all values as it is. Click Save.

  1. Go to SSO Login Settings tab. Enable Check this option if you want to add a Widget to your page under Use a Widget.

 

11.1. Go to Appearances > Widgets.

11.2. Select “Login with Keycloak“. Drag and drop to your favourite location and save.

 

  1. Hit the URL : http://localhost/wordpress

 

 

  1. Click on login with Keycloak, you will be directed to Keycloak Authentication page.

 

 

  1. Login with registered email and password.

 

You will see it redirects to word press and user is logged in.

ServiceNow connector deployment guide 1.0.0.0

Keycloak IAM Installation and Basic Config

 

  1. Download keycloak 3.4.3.Final server zip file from http://www.keycloak.org /downloads.html.

 

  1. Unzip the file and go to the bin/ directory.
  2. Run standalone.sh and hit http://localhost:8080/auth. It will open keycloak welcome page.

 

  1. Fill the data and click on create.
  2. After you create the initial admin account, you can log in to the Admin Console.

Click on Administration Console link or hit http://localhost:8080/auth/admin/.

 

  1. Login with the username and password you created on the Welcome page. The Keycloak Admin Console page opens.

  1. Creating a Realm and User in Keycloak.

7.1. Log in to the Keycloak Admin Console

7.2. In the top left corner dropdown menu that is titled Master, click Add Realm.

7.3. Create new realm from scratch so type demo for the realm name and click Create.

7.4. After creating the realm the main Admin Console page opens. The current realm is now set to demo. You can switch between managing the master realm and the realm you just created by clicking the top left corner dropdown menu.

  1. Creating a New User in Keycloak.

8.1. In the left menu bar click Users. The user list page opens.

8.2. On the right side of the empty user list, click Add User. Fill the user information and click save.

8.3. To define a temporary password for your new user. Click the Credentials tab. Type a new password and confirm it. Click Reset Password to reset the user password to the new one you specified.

 

ServiceNow connector deployment guide 1.0.0.0

VilMinds Agile/Scrum Card

What Is Agile?
The Agile movement seeks alternatives to traditional project management. Agile approaches help teams respond to unpredictability through incremental, iterative work cadences and empirical feedback. Agilists propose alternatives to waterfall, or traditional sequential development.

What is Scrum?
Scrum is the most popular way of introducing Agility due to its simplicity and flexibility.Scrum emphasizes empirical feedback, team self management, and striving to build properly tested product increments within short iterations.
Tools Used in agile/Scrum project.
JIRA , Rally , Redmine etc.

Agile Overview.
Delivering small piece of functionality within short period of time (Sprint).
Small piece of functionality is considered as User Story.
Product Backlog: Complete product functionality (user stories).
Sprint = Short period, it can be 2 Weeks, 3 Weeks depends on the project.

Agile/Scrum roles:
1) Product Owner – Responsible for writing user stories, acceptance criteria.
2) Scrum Master – Responsible to manage the scrum and sprints
3) Team (Developer, Testers, Architects etc.) – Responsible to implement and deliver the user stories

Agile Ceremonies or Events:

1) Sprint grooming
Occurs only once at beginning of the sprint, More than 1 Hour
Product owner explains each user story and acceptance criteria and clarifies the requirements.
Each user story is estimated according to its complexity and weightage; Story points is the measure for estimation.

Different tools can be used to estimate the user story. Ex, Jira agile poker, planning poker (https://www.planningpoker.com/) etc.

2) Sprint Planning/ sprint Kick off
Occurs only once at beginning of the sprint, More than 1 Hour
Planning user stories for implementation/delivery for a particular sprint according to team capacity.
Some or all the user stories from groomed stories can be planned for the particular sprint.
Sprint Backlog: User stories taken for that particular sprint.

Braking user stories in subtasks:
User stories will be broken down in the sub tasks like below and assigned to the team members.
Ex.
1) Analysis and understanding user story- 4Hr
2) Design
3) Writing java code
4) Designing user interface
5) Code quality
6) Unit Testing
7) Test Case writing
8) Test case execution
9) Defect tracing
10) Defect Verification
11) Demo

3) Sprint Review/Demo
Occurs only once at end of the sprint , More than 1 Hour.
At the end of the sprint the implemented/tested user stories will be demoed to the product owner.
Demo to the client (Product owner)

4) Sprint Retrospective
Occurs only once at end of the sprint, More than 1 Hour
The sprint retrospective is a meeting facilitated by the ScrumMaster at which the team discusses the just-concluded sprint and determines what could be changed that might make the next sprint more productive.

Three points will be discussed in this meeting.
a) What went well
b) What went wrong
c) Improvement’s

Ex.
What went right/well wrong Improvement
Sprint demo went well Requirement was not clear Team Sync.

5) Daily Scrum
This is the daily meeting for the particular sprint, 15-20 Minutes.
Team member has to give the status update to the team in following manner.
What I did yesterday, today and if any blocker/dependency.

ServiceNow connector deployment guide 1.0.0.0

Helpful GIT Commands

-Initial git clone
git clone https://jon@git.vilminds.com/primo/mobile/project-name.git

-Git commit Changes
git add –all
git commit -m “Initial Commit”

-Git Push
git push -u origin master

-Git Pull
git pull origin master

-Git Create Branch in Local
git checkout -b new-branch existing-branch

For merging forked branch , need to create pull request and admin can merge it.

-Git add  all files under folder

git add src/test/\*

 

ServiceNow connector deployment guide 1.0.0.0

OpenAM Validate OAuth token – java code

public static void validateOAuthToken(String token) {

Client client = Client.create();
WebResource webResource = client.resource(OPENAM_HOST+”/oauth2/tokeninfo?access_token=”+token);

ClientResponse response = webResource.type(MediaType.APPLICATION_FORM_URLENCODED).get(ClientResponse.class);

String output = response.getEntity(String.class);
System.out.println(response.getStatus());
System.out.println(“>> access token info>>”+output);
}

ServiceNow connector deployment guide 1.0.0.0

Installing WSO2 Identity Server 5.3.0 on Windows

1. Installing the required applications
1.1 . Ensure that your system meets the requirements as per below. Java Development Kit (JDK) is essential to run the product.
System requirements
Memory – 2 GB minimum
– 512 MB heap size.
Disk – 1 GB, excluding space allocated for log files and databases.
Oracle Java SE Development Kit (JDK) – JDK 7 or 8.

1.2. Ensure that the java PATH environment variable is set.

2. Installing the Identity Server
2.1 Download the latest version of the Identity Server from
https://wso2.com/identity-and-access-management

2.2. Extract the archive file to a dedicated directory for the Identity Server

2.3. Set the CARBON_HOME environment variable by pointing it to the directory where
you extract WSO2 Identity Server into.

3. Running the Product On Windows
3.1. Open a command prompt: On Windows, choose Start -> Run, type cmd at the prompt, and press Enter.

3.2. Execute one of the following commands, where <IS_HOME> is the directory where you installed the product distribution: On Windows:
D:\wso2\wso2is-5.3.0/bin/wso2server.bat –run

4. Accessing the management console
4.1. Once the server has started, you can access the Management Console by opening a Web browser and typing in the management console’s URL. The URL is displayed towards the end of the server start script’s console and log. For example:

Hit the URL : https://localhost:9443/carbon

Sign in with admin/admin credentials.