jquery link

my custom css

slimbox 2

analytics

Tuesday, September 27, 2011

Things to do after upgraded to Katya 64-bit...

Yes, I know it's a late upgrade and the new release is coming soon. But, who cares. I just got a chance to do it last night.

1) Enabling Compiz will cause windows movement lagging
Solution:
  • At CCSM, go to "Composite -> General -> Refresh Rate" and change the value to 60
  • Then go to "OpenGL -> General", unchecked "Sync To VBlank" option

2) Enabling Blur effect, adding "class=Gnome-terminal" will cause windows flicker.
Solution:
  • Use type "Normal" instead
	type=Menu | PopupMenu | DropdownMenu | Tooltip | Notification | Combo | Dnd | Normal

3) Overlay scroll started to annoy me
Solution:
  • Uninstall the library
	$ sudo apt-get --purge remove overlay-scrollbar liboverlay-scrollbar-0.1-0

4) My Quake 3 demo is not working
Solution:
  • Install ia32-libs library
	$ sudo apt-get install ia32-libs

5) No sound from my headphone jack?
Solution:

Thursday, September 15, 2011

WebService - PI - WebService scenario...

Scenario overview:
  • Third party app sending request to PI webservice.
  • PI passing the request to third party webservice.
  • Third party webservice returning response to PI.
  • PI webservice returning response to third party app.

Steps at Enterprise Service Builder
1) Create request and response Data Type for SENDER.

2) Create request and response Message Type for SENDER.

3) Create External Definition and import wsdl file generated from external webservice. By doing so you should have the request and response External Message for RECEIVER.

4) Create outbound Service Interface.
  • Category: Outbound
  • Mode: Synchronous
  • For Request and Response Role, use Type as Message Type and assign Name with request and response message type respectively

5) Create inbound Service Interface.
  • Category: Inbound
  • Mode: Synchronous
  • For Request and Response Role, use Type as External Message and assign Name with request and response external message respectively

6) Create Message Mapping for request.
  • Source: Request Message Type
  • Target: Request External Message

7) Create Message Mapping for response.
  • Source: Response External Message
  • Target: Response Message Type

8) Create Operation Mapping.
  • Source Operation: Outbound Service Interface
  • Target Operation: Inbound Service Interface
  • Request Mapping Program: Request Message Mapping
  • Response Mapping Program: Response Message Mapping

Steps at Integration Builder
1) Create Configuration Scenario.

2) Create Business Component.

3) Add SENDER Communication Channel to Business Component.
  • Adapter Type: SOAP

4) Add RECEIVER Communication Channel to Business Component.
  • Adapter Type: SOAP
  • Target URL: Third party webservice URL
  • SOAP Action: Third party webservice SOAP Action

5) Create Receiver Determination.
  • Sender
    • Communication Component: Business Component
    • Interface: Outbound Service Interface
    • Namespace: namespace defined in ESB

6) Create Interface Determination.
  • Sender
    • Communication Component: Business Component
    • Interface: Outbound Service Interface
    • Namespace: namespace defined in ESB
  • Receiver
    • Communication Component: Business Component
    • Receiver Interfaces:
      • Operation Mapping: Operation Mapping defined in ESB (important)
      • Name: Inbound Service Interface
      • Namespace: namespace defined in ESB

7) Create Sender Agreement.
  • Sender
    • Communication Component: Business Component
    • Interface: Outbound Service Interface
    • Namespace: namespace defined in ESB
    • Sender Communication Channel: SENDER communication channel

8) Create Receiver Agreement.
  • Sender
    • Communication Component: Business Component
  • Receiver
    • Communication Component: Business Component
    • Interfaces: Inbound Service Interface
    • Namespace: namespace defined in ESB
    • Receiver Communication Channel: RECEIVER communication channel

Tuesday, September 13, 2011

Basic info for SAP PI - F2F...

1) Create software component at System Landscape Directory (SLD) and import it into Enterprise Service Repository (ESR).

2) Build sequence for Enterprise Service Builder (ESB)
  • Namespace
  • Datatype
  • Messagetype
  • Service Interface
  • Message Mapping
  • Operation Mapping

3) Build sequence for Integration Builder (IB)
  • Configuration Scenario
  • Business Component (or Business System)
  • Communication Channel
  • FCC configuration in Communication Channel
  • Receiver Determination
  • Interface Determination
  • Sender Agreement
  • Receiver Agreement

For file to file scenario that doesn't require any mapping where source and target files are expected to be the same:
  • Create Communication Channel for both sender and receiver Business System
  • Create Integrated Configuration

Important notes:
- SLDAPICUST
- SM59
- SLDCHECK

- SU01
- SXI_CACHE
- SXMB_IFR
- SXI_MONITOR
- SXMB_MONI

When creating datatype, make sure the structure is properly construct

    data-type-name // your datatype name
        record // represent data row
            detail // represent data structure
                field1
                field2
                field3

Ref link: Step by Step Guides - Connectivity

** This post is just for my own personal reference.