Layers

Application (Layer 7)

This layer supports application and end-user processes. Communication partners are identified, quality of service is identified, user authentication and privacy are considered, and any constraints on data syntax are identified. Everything at this layer is application-specific. This layer provides application services for file transfers, e-mail, and other network software services. Telnet and FTP are applications that exist entirely in the application level. Tiered application architectures are part of this layer.

Presentation (Layer 6)

This layer provides independence from differences in data representation (e.g., encryption) by translating from application to network format, and vice versa. The presentation layer works to transform data into the form that the application layer can accept. This layer formats and encrypts data to be sent across a network, providing freedom from compatibility problems. It is sometimes called the syntax layer.

Session (Layer 5)

This layer establishes, manages and terminates connections between applications. The session layer sets up, coordinates, and terminates conversations, exchanges, and dialogues between the applications at each end. It deals with session and connection coordination.

Transport (Layer 4)

This layer provides transparent transfer of data between end systems, or hosts, and is responsible for end-to-end error recovery and flow control. It ensures complete data transfer.

Network (Layer 3)

This layer provides switching and routing technologies, creating logical paths, known as virtual circuits, for transmitting data from node to node. Routing and forwarding are functions of this layer, as well as addressing, internetworking, error handling, congestion control and packet sequencing.

Data Link (Layer 2)

At this layer, data packets are encoded and decoded into bits. It furnishes transmission protocol knowledge and management and handles errors in the physical layer, flow control and frame synchronization. The data link layer is divided into two sub layers: The Media Access Control (MAC) layer and the Logical Link Control (LLC) layer. The MAC sub layer controls how a computer on the network gains access to the data and permission to transmit it. The LLC layer controls frame synchronization, flow control and error checking.

Physical (Layer 1)

This layer conveys the bit stream - electrical impulse, light or radio signal -- through the network at the electrical and mechanical level. It provides the hardware means of sending and receiving data on a carrier, including defining cables, cards and physical aspects. Fast Ethernet, RS232, and ATM are protocols with physical layer components.

Deploying the confhelp.properties file in CCMDB

The confhelp.properties file must be deployed to enable the help system for the product.

To deploy the confhelp.properties file, complete the following steps:

1. Ensure that you are logged in to the administrative workstation.
2. Run the following command:

3.  \jacl\solutions\Sendfile.bat

4. 

5. 

6.  $

7.  "\applications\

8.  maximohelp\helpweb\webmodule\WEB-INF\confhelp.properties"

9.  "WASInstallLocation>\properties"

"confhelp.properties"

Capturing the Hostname on a Ticket

You can configure the SmartCloud Control Desk to automatically store the hostname/IP of a user's workstation (client machine or machine connection to SmartCloud Control Desk) in a ticket (Service Request, Incident or Problem) when the ticket is created by following these steps.

1.     Add new field to TICKET named CREATEDBYHOST

2.     Set the default value of CREATEDBYHOST to 127.0.0.1

3.     Create a relationship named 'CREATEDBY' on object SR (of INCIDENT, PROBLEM) with child object: PERSON
where clause: personid=:createdby)

4.     Create a crossover domain named SESSION2TKT on object MAXSESSION
from field CLIENTHOST to field CREATEDBYHOST and
validation where clause:userid=:CREATEDBY.USER.MAXSESSION.userid
list where clause:userid=:CREATEDBY.USER.MAXSESSION.userid

5.     Associate the SESSION2TKT domain with CREATEDBYHOST

6.     Save all changes and run configdb

In order to capture the hostname of the user's workstation (client machine) and not just the IP address, your web server must be configured to perform reverse DNS lookups.

To enable reverse DNS lookups in the IBM HTTP Server do the following:

1.     Edit the httpd.conf file (located in Program Files\IBM\HTTPServer\conf\httpd.conf on Windows

2.     Find the line that says: HostnameLookups off

3.     Change the line to say: HostnameLookups on

4.     Save the file and restart the web server

How to Change the Drilldown limit in Maximo

1. Go to the Application Designer application
2. Select the Action "Export System XML"
3. Highlight the line Library in the Export System XML dialog and click on the Export XML icon,.

4. Using the "save as" option, save two copies of this file. Name one of them library.xml and the other library.xml.bk, which will serve as a backup.
5. Open library.xml in a text editor
6. Find the string
7. insert maxchildren="200" directly after it.

Note: this will change the display limit for Location children to 200. You may designate another limit by selecting another numeric value.

Note: You should find only one "non commented" occurrence of the string

The changed section of the library.xml file should look like the section below. The inserted string is shown in bold:

8. Find the string
9. insert maxchildren="200" directly after it.

Note: this will change the display limit for Asset children to 200. You may designate another limit by selecting another numeric value.

Note: You should find only one “non commented” occurrence of the string

10. Save library.xml
11. On the Application Designer main tab, select the Import icon, and browse to the library.xml file that you have updated.

12. Click OK to import the file.