ServiceNow connector deployment guide

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

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.

ServiceNow connector deployment guide

Liferay Service Builder – Connect to External/Seperate Database

  • Create a  Liferay plugin project
  • Create a service.xml , ex like below.

<?xml version=”1.0″ encoding=”UTF-8″?>
<!DOCTYPE service-builder PUBLIC “-//Liferay//DTD Service Builder 6.2.0//EN” “”>
<service-builder package-path=”com.dinacs” auto-namespace-tables=”false”>
<entity name=”Feedback” local-service=”true” remote-service=”true”>

<column name=”feedbackId” type=”long” primary=”true” />

<column name=”feedbackTitle” type=”String” />
<column name=”feedbackText” type=”String” />

  • Build the service
  • Add your separate database details in ex like below.

# liferay default db

# seperate database

  • Create ext-spring.xml file under docroot/WEB-INF/src/META-INF
  • Place the content like below in ext-spring.xml

<?xml version=”1.0″?>

<beans xmlns=””
xmlns:aop=”” xmlns:context=””
xmlns:tx=”” xmlns:xsi=””

<bean id=”basePersistence” abstract=”true”>
<property name=”dataSource” ref=”dinacsDS” />
<property name=”sessionFactory” ref=”dinacsSessionFactory” />

<bean id=”dinacsHibernateSessionFactory”
<property name=”dataSource” ref=”dinacsDS” />

<bean id=”dinacsSessionFactory” class=”com.liferay.portal.dao.orm.hibernate.SessionFactoryImpl”
<property name=”sessionFactoryImplementor” ref=”dinacsHibernateSessionFactory” />

<bean id=”dinacsDS”
<property name=”targetDataSource”>
<bean class=”com.liferay.portal.dao.jdbc.util.DataSourceFactoryBean”>
<property name=”propertyPrefix” value=”jdbc.dinacs.” />

  • Edit the service.xml and add data-source , session-factory and tx-manager attributes to the entity tag.
  • Ex like below.

<?xml version=”1.0″ encoding=”UTF-8″?>
<!DOCTYPE service-builder PUBLIC “-//Liferay//DTD Service Builder 6.2.0//EN” “”>
<service-builder package-path=”com.dinacs” auto-namespace-tables=”false”>
<entity name=”Feedback” local-service=”true” remote-service=”true” data-source=”dinacsDS” session-factory=”dinacsSessionFactory” tx-manager=”dinacsTransactionManager” >

<column name=”feedbackId” type=”long” primary=”true” />

<column name=”feedbackTitle” type=”String” />
<column name=”feedbackText” type=”String” />

  • Build the service again.
  • Deploy the portlet.

Note : tables will be created in the liferay default database only , need to manually create the tables in separate database.

ServiceNow connector deployment guide

Integrating Solr Search Engine with Liferay portal

Step 1: Setting up Solr server

1.1 download solr 4.3.1 from
1.2 Unzip it and navigate to solr-4.3.1\example and double click on start.jar
1.3 browse localhost:8983 and verify solr is up and running

Step 2: Install Solr 4 search Engine plugin on Liferay  Portal

2.1 Copy solr plugin war file to deploy folder (liferay.home/deploy)

Step 3 : Integrating Liferay Portal With Solr

Change the solr url as follows in solr-spring.xml which is located in liferay.home/tomcat/webapps/solr-web/WEB-INF/classes/META-INF/
Set the value of constructor-arg from

<bean id=”solrServer”
<constructor-arg type=”java.lang.String” value=”” />
to this :
<bean id=”solrServer”
<constructor-arg type=”java.lang.String” value=” http://${}:${solr.port.number}/solr” /> </bean>

Step 4: Restart Liferay and solr servers.

ServiceNow connector deployment guide

Integrating OKTA SSO With Liferay Portal Using SAML

1 : Installing SAML Plugin on Liferay Portal.

1.1 Download and Copy saml plugin war file to deploy folder (liferay.home/deploy)

If you do not have saml plugin war file.

1.1 Login to the Liferay portal as admin and go to the control panel
1.2 Click on apps and then purchased tab.
1.3 In purchased tab click on EE.
1.4 Search for SAML 2.0 and click on install.

2 : Creating Chicklet in OKTA For Liferay , We can create developer okta account for this trial.

2.1 Get the service provider url (liferay sp) . ex http://your domain or ip /c/portal/saml/acs
2.2  Create Okta Chicklet with following details
service provider url ex: http://your domain or ip /c/portal/saml/acs
Audience restriction ex : Liferay
Okta Metadata file : save it in xml and put it in the liferay.home/data/ directory

3: Creating keystore

Create keystore in the liferay.home/data/ directory using below command
keytool -genkey -keyalg RSA -alias Dinacs -keystore keystore.jks -storepass dinacs-validity 360           -keysize 2048

Enter the details and keep alias password as same as the keystore password.
It creates keystore.jks file in the liferay.home/data directory.

4:  Modify file

Navigate to liferay.home and open file .
Add below entries to the file and save it.

# Enable SAML Plugin
# Set the role to sp on the Service Provider side
# Set the SAML entity id, it matches the alias we used to setup the keystore
# The metadata location for Identity Provider
# Keystore
# keystore type
# location of the keystore
# pwd for accessing the keystore
# pwd for accessing the certificate of the entity in the keystore
# Service Provider
# the chicklet url from okta – your idp url
saml.sp.session.keepalive.url=http://your ip or domain :8080/c/portal/saml/idp/keepalive
# Service Provider user attribute mappings
#Set this to true to enable reminder queries that are used to help reset a user’s password.
# auto generate screen names

Step 5: Restart Server and Test SSO

Hit your liferay url and if you are not logged in then it will redirect you to the okta login page , after entering login credentials , Okta will redirect back to the liferay . User will be created in the liferay portal and will see it logged in.