The web blog http://www.learnsccd.com strives to be a comprehensive guide to SCCD, TADDM, SERVICE NOW and MAXIMO tools. This is a personal site maintained solely by me. I intend to update it regularly.For live updates please follow us on.

Clearing Websphere Application Server Cache

Clearing Websphere Application Server Cache


1. Log into the WebSphere Integrated Solutions Console. 

2. Shut down the Maximo application server (default name MXServer). 

3. Delete cached files from temp, tranlog, wstemp and, optionally, logs directories: 

Windows

    C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\temp\XXXXXNode01\MXServer\*.*
    C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\tranlog\XXXXXCell01\XXXXXNode01\MXServer\*.*
    C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\wstemp\*.*
    (optional) C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\MXServer\*.*

Unix 
 

    /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/temp/XXXXXNode01/MXServer/*.*
    /opt/IBM/WebSphere/AppServer/profiles/ctgAppSrv01/tranlog/XXXXXCell01/XXXXXNode01/MXServer/*.*
    /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/wstemp/*.*
    (optional) /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/MXServer/*.*

Find Which Java version is my WebSphere Application Server V8.5 using?

Find Which Java version is my WebSphere Application Server V8.5 using?


1. Find the list of Java versions available for WAS. 
    C:\Program Files\IBM\Websphere\profiles\AppSrv01\bin>managesdk.bat -listAvailable

2. Associate one of the Java version for WAS single profile
    C:\Program Files\IBM\Websphere\profiles\AppSrv01\bin>managesdk.bat -enableProfile -                profileName Dmgr01 -sdkName 1.7.1_64 -enableServers

3.Associate One of the the Java versions for WAS all profiles
    C:\Program Files\IBM\Websphere\profiles\AppSrv01\bin>managesdk.bat -enableProfileAll -sdkname 1.7.1_64 -enableServers
 

Clearing WebSphere temporary file caches for Maximo Asset Management

Clearing WebSphere temporary file caches for Maximo Asset Management


1. Log into the WebSphere Integrated Solutions Console. 

2. Shut down the Maximo application server (default name MXServer). 

3. Under Applications > Application Types > WebSphere enterprise applications, select and uninstall the Maximo Enterprise application (maximo.ear) completely. 

4. Delete cached files from temp, tranlog, wstemp and, optionally, logs directories: 

Windows (WebSphere location is C:\Program Files\IBM\WebSphere\AppServer, the application server profile is called ctgAppSrv01, the node is called ctgNode01, and the Maximo server is called MXServer)

    C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\temp\ctgNode01\MXServer\*.* 
    C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\tranlog\ctgCell01\ctgNode01\MXServer\*.* 
    C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\wstemp\*.* 
    (optional) C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\MXServer\*.*


Unix ( WebSphere location is /opt/IBM/WebSphere/AppServer/profiles/ctgAppSrv01, the application server profile is called ctgAppSrv01, the node is called ctgNode01, and the Maximo server is called MXServer).


    /opt/IBM/WebSphere/AppServer/profiles/ctgAppSrv01/temp/ctgNode01/MXServer/*.* 
    /opt/IBM/WebSphere/AppServer/profiles/ctgAppSrv01/tranlog/ctgCell01/ctgNode01/MXServer/*.* 
    /opt/IBM/WebSphere/AppServer/profiles/ctgAppSrv01/wstemp/*.* 
    (optional) /opt/IBM/WebSphere/AppServer/profiles/ctgAppSrv01/logs/MXServer/*.*


5. Delete MAXIMO.ear from /installedApps, both the contents of the directory and the directory itself: 

Windows (locations as above): 

    C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\installedApps\ctgCell01\MAXIMO.ear


Unix (locations as above): 

    /opt/IBM/WebSphere/AppServer/profiles/ctgAppSrv01/installedApps/ctgCell01/MAXIMO.ear


   You do not need to delete MXIEHS.ear directory. 

5. Deploy the Maximo enterprise application. If using LDAP server authentication, make sure that the security permissions are set as previously for the MAXIMO Enterprise Application. 

6. Synchronize nodes. System Administration > Nodes, check the node to synchronize, then click the Synchronize button. 
[Use Full resynchronize if you have made manual file edits on the node. Deploying a Maximo ear does not make manual file edits on the node, so it should not be necessary to use this function. Full synchronize can take a much longer to complete. If Synchronize fails immediately, manual synchronization will be necessary.] 

7. Restart MXServer

Note: In WebSphere 8.0 and 8.5.5 on Windows, the default installation directories may be in C:\Program Files (x86)\IBM rather than C:\Program Files\IBM. 

Manually configuring Microsoft SQL Server 2014

Manually configuring MS SQL Server 2014


1. Configure the listener port.
If the default instance of the Microsoft SQL Server Database Engine listens on TCP port 1433. Named instances of the Microsoft SQL Server Database Engine and Microsoft SQL Server Compact Edition are configured for dynamic ports, which means they select any available port when the service starts. When connecting to a named instance across a firewall, configure the Database Engine to listen on a specific port, to open this port in the firewall.
a. Open Programs > Microsoft SQL Server 2014 > Configuration Tools > SQL Server Configuration Manager
b. From the Microsoft SQL Server Configuration Manager Navigation pane, expand SQL Server Network Configuration > Protocols for <instance name>, and then double-click TCP/IP.
c. In the TCP/IP Properties dialog box, click the IP addresses tab.
d. For each IP address listed, ensure that the TCP Dynamic Ports field is blank. If the TCP Dynamic Ports field contains a value of  0, that IP address is using dynamic ports. Since Maximo 7.6  requires Microsoft SQL Server to listen on a static port, this field must be blank.
e. For each IP address listed, enter 1433 for the TCP Port field.
f. Click OK.
g. From the SQL Server Configuration Manager Navigation pane, click SQL Server Services.
h. Right-click SQL Server (<instance name>) and then click Restart, to stop, and restart Microsoft SQL Server.
i. Verify the Microsoft SQL Server instance is running, and then close SQL Server Configuration Manager.
2. Verify that you enabled the Full-text Search setting during the installation of Microsoft SQL Server 2014. To determine if Full-text Search is installed on your existing Microsoft SQL Server database, perform the following steps:
a. Open SQL Server Management Studio, select SQL Server Authentication as the authentication type, and enter the credentials for the sa user ID, and then click Connect.
b. Click New Query.
c. Type the following command:
select FULLTEXTSERVICEPROPERTY ( 'IsFulltextInstalled' )
If you did not install Full-text Search (the resulting value is zero), you must do so at this time. To install Full-text Search, insert the Microsoft SQL Server 2008 product media into the system and start the installation wizard. Navigate through the wizard and enable the Full-Text Search option located on the Custom portion of the Setup Type dialog box. To finish the installation process, restart the server.
3. Create a Microsoft SQL Server Database.
a. Open SQL Server Management Studio (Start > Programs > Microsoft SQL Server 2014 > SQL Server Management Studio)
b. Right-click the Databases folder from the navigation tree, and select New Database.
c. In the Database name entry field, specify a unique database name (for example maxdb76)
d. For the maxdb76 Logical Name, change the Initial Size (MB) attribute to 500 (MB), and also set the value of the Auto growth field to By 1MB, unrestricted growth.
e. If you prefer, modify the log settings to accommodate your production environment.
f. Click OK.
4. Create the Maximo® User for Microsoft SQL Server.
a. Open Microsoft SQL Server Management Studio (Start > Programs > Microsoft SQL Server 2014 > SQL Server Management Studio)
b. Click New Query.
c. Select the maximo 7.6  database (maxdb76) from the Available Databases menu,
d. Enter the following script to create the Maximo database user MAXIMO with a password of  MAXIMO.
e. sp_addlogin MAXIMO,MAXIMO
go
This value is case-sensitive.
f. Click Execute.
g. Enter the following script to change the database owner to maximo.
h. sp_changedbowner MAXIMO
go
i. Click Execute.

Configuring Maximo 7.6 Web Services to use Soap version 12

Maximo 7.6 Web Services to use Soap version 12


1.  Login to Maximo application,  Navigate to System Configuration -->Platform Configuration-->
     System Properties and locate  mxe.int.soapversion  property , make sure that Current and Global        values are set to soap12.

2. Navigate to IBM\SMP\maximo\applications\maximo\meaweb\webmodule\WEB-INF\webservices
    and modify the XML to match the sample:

<?xml version="1.0" encoding="UTF-8"?>
<webservices xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <webservice-description>
      <webservice-description-name>jaxws</webservice-description-name>
      <!--wsdl-file>WEB-INF/wsdl/wsprovider11.wsdl</wsdl-file-->
      <wsdl-file>WEB-INF/wsdl/wsprovider12.wsdl</wsdl-file>
      <port-component>
        <port-component-name>JAXWSWebServiceProviderPort</port-component-name>
        <wsdl-service xmlns:pfx="http://webservices.iface.psdi/">pfx:jaxws</wsdl-service>
        <wsdl-port xmlns:pfx="http://webservices.iface.psdi/">pfx:JAXWSWebServiceProviderPort</wsdl-port>
        <protocol-binding>http://www.w3.org/2003/05/soap/bindings/HTTP/</protocol-binding>
        <service-impl-bean>
          <servlet-link>jaxws</servlet-link>
        </service-impl-bean>
      </port-component>
    </webservice-description>
</webservices>
 

3.  Rebuild and redeploy the EAR file.

4. Call WSDL, scroll to the bottom of the file and verify that it has SOAP12Binding.

You all set, you should be able to call  a Web Service using soap12 version.

NOTE: After the change ONLY   Soap12 version will be available for all webservices.  

Maximo 7.6 Feature Packs

Maximo 7.6 Feature Packs

With Maximo 7.6 IBM is now using a Continuous Delivery process to deliver new features. Instead of releasing all the new features in one chunk in the major releases, IBM is now pushing new features into the feature packs (the old good fixpacks) each 4-6 months.

Maximo 7.6.0.1

Updated commands to minimize downtime
When you install a feature pack or upgrade your current deployment, the configuration portion of the process includes tasks to update the database and build and deploy application EAR files. The application server must be stopped during this phase of the deployment, which can lead to extended downtime of your production environment. Maximo 7.6.0.1 feature pack delivers an improved updatedb program that splits the preparation of product class files and database updates into two separate commands: updatedblitepreprocessor and updatedblite. The first step of the updated process does not require stopping the application server.

New inventory reports
Three new reports were added in 7.6.0.1 to display the inventory item cost type (Average, Standard, LIFO, FIFO) and calculate its ABC, Economic Order Quantity (EOQ), or Report Output Period (ROP) by evaluating the transaction tables. The three new reports are Inventory ABC Transaction Date Analysis, Inventory EOQ Transaction Date Analysis, and Inventory ROP Transaction Date Analysis.

New with inventory usage documents
Inventory Usage application forces a complete issue of all items on the usage document. In the past if you wanted to do a partial issue of items on the usage document, you had to manually create a new usage doc with the remaining items. In 7.6.0.1, you can now issue a partial quantity of an inventory usage document and create another usage document for the remaining quantity. 

Maximo 7.6.0.2

New Invoice Cost Variance report
The new Invoice Cost Variance report displays the cost variances for LIFO/FIFO items. These variances occur when there is a difference in the received Purchase Order Line cost and the Invoiced Line cost. This report can be used to reconcile cost differences.

Maximo 7.6.0.3

SAML authentication protocol support
The application server can now be configured to integrate Security Assertion Markup Language (SAML) authentication protocol that authenticates your session to an Identity Provider (IdP) rather than directly to the system.

Asset depreciation
Maximo 7.6.0.3 allows the creation of asset depreciation schedules to reduce the value of an asset according to user-defined period thresholds. This feature provides you with a more accurate view of an asset’s current value and facilitates better decision making regarding an asset’s lifecycle.

Maximo 7.6.0.4

JSON mapping
The Maximo Integration Framework JSON API is now improved for IBM Maximo Asset Management 7.6.0.4. These improvements make it easier to send data in and out of Maximo.

Maximo 7.6.0.2 provided support for a RESTful JSON API to access Maximo data in a synchronous model using ‘Maximo JSON’-formatted data. New capabilities are now provided to support asynchronous integration of JSON messages through the integration JMS queues. This support is provided for Enterprise Service (inbound) and Publish Channel (outbound) messages. In order to support this capability, a JSON Mapper component is provided that supports the conversion of JSON data to and from Maximo XML. This is needed since the Integration Framework natively processes Maximo XML in order to interact with the Maximo Business Objects (MBOs).

The JSON Mapper application is being provided to allow an implementer to define a map of a JSON formatted message to and from a Maximo XML message that is defined by the Object Structure associated with the channel or service. The application allows the user to select JSON objects and properties and map them to Maximo objects and attributes. The map acts as a customization layer on the channel or service in a similar manner that is supported using Java™ or Scripting. As part of its definition, the map identifies the Channel or Service for which it will be executed. This map capability can also be used with an enterprise service that is invoked synchronously (no JMS queue) but where there is no support for a JSON Map with an Invocation Channel.

No Java in direct printing
The direct print feature no longer uses an applet and is now accessible on more browsers.
Data download from Start Center
This new feature allows you to download the contents of results sets in a Comma Separated Value (CSV) format via a new download button.

Maximo 7.6.0.5

Work Centers
Work Centers are a brand new user interface for Maximo that simplify the way you can access and complete daily tasks without opening multiple applications. Work Centers are role-based user interfaces that you can access on any device, including desktop computers, notebooks, tablets, or smartphones. Four work centers are ready and available in Maximo 7.6.0.5: Business Analysis, Work Supervision, Work Execution, Business Analysis.

Integration security
You can now configure authorization for data loaded through integration object structures. In the Object Structures application, developers can define and implement signature options (sigoptions) for an object structure. In the Security Groups application, security administrators can now grant user access to a specific object structure. Users who are associated with an inbound integration transaction can be granted read, insert, save, and delete access.

Improved Upgrade capabilities
The configuration tool includes a new upgrade action called Configure Existing 7.5 Environment for Upgrade. This action configures an existing Maximo Asset Management 7.5 deployment so it can be upgraded to a Maximo Asset Management 7.6 environment.

The configuration tool includes a new optional deployment action Update the database with the UpdateDBLite feature. This action helps you decrease the amount of production server downtime for upgrades and fix pack installations.

Maximo 7.6.0.6

Service Requests Work Center
The brand new Service Requests Work Center allows users to quickly create service requests by using your desktop computer, laptop computer, or mobile device. You can also monitor the status of existing service requests that you created or are effected by. You can add new service requests by specifying the request category, identifying the location, defining the asset, and providing a description. You can upload photographs or videos to requests to provide more information.

Data Set Designer
Business analysts can use the Data Set Designer to create data sets quickly and without the involvement of IT personnel. Building a data set in the Data Set Designer involves selecting an object set and specifying the content or fields that you want to include. You can then configure the content by selecting fields and applying filters and sorting. While you are configuring the data set, you can use the preview feature and then you can export its contents to comma-separated value (CSV) format.

Building Information Models (BIM) applications
A new module, Building Information Models, is added to IBM Maximo Asset Management which includes two new applications: Building Information Modeling (BIM) Projects and Manage BIM Viewer applications. In the BIM Projects application, you can import building model data in COBie format into Maximo. After you import building data, you can view and manage the data in the Assets and Locations applications. If you install a third-party building model viewer in the Manage BIM Viewer application, you can display 3D view of the BIM models in the Assets, Locations, or Work Order Tracking applications.

License Usage Monitor application
You can use the new License Usage Monitor application to monitor your usage of licenses for Maximo products. You can use this information to optimize usage of licenses and determine whether your organization has purchased the correct number of licenses. The License Usage Monitor application does not prevent overuse of licenses and does not replace the IBM license auditing process. This application gathers information to help you understand your license usage.

No Java in Workflow Designer
The Maximo Workflow Designer application was updated and no longer requires a Java applet to function. This new design allows the Workflow Designer to be used with browsers with newer technology, such as Microsoft Edge, which do not support Java applets.

ServiceNow - Inbound Email Actions

ServiceNow - Inbound Email Actions


Inbound email actions enable an administrator to define the actions ServiceNow takes when receiving email. Inbound email actions are similar to business rules, using both conditions and scripts. The inbound email action checks the email for a watermark that associates it with a task and checks for other conditions. If the conditions are met, the inbound email action runs the script.

By default, if an email has no identifiable watermark, an inbound email action attempts to create a new incident from the message. If the email has a watermark of an existing incident, an inbound email action updates the existing incident according to the action's script.

To add an Inbound Email Action:
  1. Navigate to System Policy > Email > Inbound Actions
  2. Click New
  3. Complete the fields on the form


ServiceNow - Web Services

ServiceNow - Web Services


  • Overview
  • Web Services Components
  • Web Services Methods

Overview

A Web Service is an HTTP-based communication method that lets diverse applications exchange information and talk to each other. 

  • Inbound Web Services: Inbound web services allow you to access and modify ServiceNow data using a client application.
  • Outbound Web Services: Outbound web services allow you to send SOAP and REST messages to external web service providers. 

Publisher of Web Services (Provider/Producing)
  1. Publishing a web service in ServiceNow that can be consumed by a 3rd party can be accomplished by creating a new Inbound Web Service
  2. Publishes web services for clients to invoke (consume)

Consumer of Web Services (Consuming)
  1. Consuming a 3rd party web service from ServiceNow can be accomplished by creating a new Outbound SOAP Message
  2. Invokes / Consumes published web services.

Web Services Components

Web Services and ServiceNow
A method of communication between two electronic devices over a network

ServiceNow supports both inbound (provider) and outbound (consumer) web services.


Web Services Methods

The ServiceNow system supports access (input and query) to its tables and their data by using these below methods:
  • Direct Web Services (get, insert, query)
  • Web Service import sets that do data mapping using Transform Maps
  • Scripted Web Services that are executed in JavaScript
Direct Web Service: Endpoints are accessed directly using a URL, which is integrated on  the UI level between two or more applications. It directly manipulates the data into the target tables. Therefore, there are many security considerations with this Web Service Method.

URL format: https://<instance name>.service-now.com/<table_name>.do

Mapped Web Service: All Web Services import sets go through a transform map to match fields.

Scripted Web Services: Helpful when the other system requires a very specific integration that Simple Web Services cannot provide. It parses the information and determines the source.
Example: Servers in locations all over the world are tracked in one CMDB. The MID Server checks the server message queue and uses scripting to determine which location sent the record. If it was San Diego, the update will go to San Diego Servers table.

Note: If we have a large amount of data, Mapped Web Services process data one by one and the cost of transformation is quite high. Scripted Web Services is lower cost and for large amount of data, the better choice.