Similarly to registration, a WD or BSP application can trigger any portal event. In this case, the event is passed to the portal by the respective iView. The portal passes the event to all iViews that have registered for this event. The application that finally handles this event can, in turn, have been set up with a different technique than the WD or BSP application triggering it.

Portal eventing functions only between iViews that are on the same browser window. Events between iViews in different browser windows cannot be transported.

All participating iViews must also belong to the same domain. Otherwise portal eventing cannot work due to JavaScript restrictions.

Syntax for Namespace and Names of Events:

Valid characters: “A”"Z”,”a”"z”,”0″”9″,”",”_”,”-”,”.”

Namespaces com.sapportals.portal.* and com.sapportals.* are reserved by sap, normally we used the company namespace.

Namespaces and event are case sensitive so be careful on the typing, because there is no syntax check.

In my tutorial I trigger and register the WD or BSP from different systems into one portal IView.

WebDynpro Event Sender

Goto SE80 create z_portal_event_sender component and application with default.view and default.window.

In the context of default view add context node main and 3 attributes: text_area_1 and text_area_2, text_area_3. In the layout of default view add 3 input fields: input_1, input_2, input_3 which bind respectively to the context attributes: text_area_1, text_area_2, text_area_3, 1 button btn with action trigger_event.

In the event method onactiontrigger_event on view I only want to send input_1 and input_2 to the portal. The data has be concatenated into one parameter on the server side before triggering the portal event

method onactiontrigger_event .
  data:
    node_main                           type ref to if_wd_context_node,
    elem_main                           type ref to if_wd_context_element,
    stru_main                           type if_default=>element_main ,
		item_text_area_1                    like stru_main-text_area_1,
		item_text_area_2                    like stru_main-text_area_2,
		item_text_area_3                    like stru_main-text_area_3.
* navigate from <CONTEXT> to <MAIN> via lead selection
  node_main = wd_context->get_child_node(wd_this->wdctx_main ).
* get element via lead selection
  elem_main = node_main->get_element(  ).
* get single attribute
  elem_main->get_static_attributes(
    exporting
      name =  `TEXT_AREA_1`
    importing
      value = item_text_area_1 ).

	elem_main->get_static_attributes(
    exporting
      name =  `TEXT_AREA_2`
    importing
      value = item_text_area_2 ).

	elem_main->get_static_attributes(
    exporting
      name =  `TEXT_AREA_3`
    importing
      value = item_text_area_3 ).

WebDynpro Event receiver

Goto SE80 create z_portal_event_receiver component and application with default.view and default.window.

In the context of default view add context node main and 3 attributes: text_area_1 and text_area_2, text_area_3. In the layout of default view add 3 input fields: input_1, input_2, input_3 which bind respectively to the context attributes: text_area_1, text_area_2, text_area_3, 1 button btn with action catch_event

Register default view to the portal event Framework, in the wddoinit of default I registered the portal manager, on the server side after receiving the portal parameter, I split the parameter again into different field.

method wddoinit .

  data l_api_component  type ref to if_wd_component.
  data l_portal_manager type ref to if_wd_portal_integration.
  l_api_component = wd_comp_controller->wd_get_api( ).
  l_portal_manager = l_api_component->get_portal_manager( ).
  data l_wd_view type ref to if_wd_view_controller.

  l_wd_view ?= wd_this->wd_get_api( ).
  l_portal_manager->subscribe_event(
      portal_event_namespace = 'com.xiaohong'
      portal_event_name      = 'test_event'
      view                   = l_wd_view
      action                 = 'CATCH_EVENT' ).

Endmethod.

Method onactioncatch_event.

	data: EVT_NAME type STRING,
        evt_parameter type string,
        wa_string type string,
        it_string like table of wa_string.

  EVT_NAME = WDEVENT->GET_STRING( NAME = 'PORTAL_EVENT_NAME' ).

  if EVT_NAME = 'test_event'.
		evt_parameter = WDEVENT->GET_STRING( NAME = 'PORTAL_EVENT_PARAMETER' ).
		Split evt_parameter at "*" into table lt_string.

	  DATA:
	    node_main                           TYPE REF TO if_wd_context_node,
	    elem_main                           TYPE REF TO if_wd_context_element,
	    stru_main                           TYPE if_default=>element_main ,
	    item_text_reciever                  LIKE stru_main-text_reciever.

* 	navigate from <CONTEXT> to <MAIN> via lead selection
  	node_main = wd_context->get_child_node( name = `MAIN` ).
* 	get element via lead selection
  	elem_main = node_main->get_element(  ).
 		Read table it_string into wa_string index 1.
* 	get single attribute
  	elem_main->set_attribute(
  	  EXPORTING
  	    name =  `TEXT_AREA_1`
  	    value = wa_string ). 
  	
		Clear wa_string.
  	
		Read table it_string into wa_string index 2.
  	
		Elem_main->set_attribute(
  	          Exporting name = 'TEXT_AREA_2'
  	            Value = wa_string). 
		)
  endif.
endmethod. 

BSP application event sender

Goto SE80, create bsp application z_portal_bsp_sender, page event_sender.htm with page flow logic, it has 3 input fields and 1 button. When the button is pressed, we trigger the portal event using javascript on the browser instead of server event to avoid the respect/response cycle, technically HTML DOM can read the value of each UI element, so I read the data before triggering the portal event.

Layout of event_sender.htm

<%@page language="abapljavascript" %>
	<script type="text/javascript">
		function alertValue(){
			x = document.getElementById("input_field_1").value + "*" + 
					document.getElementById("input_field_2").value;
			portalFireEvent('com.testNamespace','test_event',x);
		}
	</script>

<%@extension name="htmlb" prefix="htmlb" %>
<htmlb:content design="design2003">
	<htmlb:page title="">
		<htmlb:form>
			<htmlb:label 			for="input_field_1" text="Event Message:" />
			<htmlb:inputField id="input_field_1"	type="STRING" value="<%= EVENT_TEXT_1 %>" />
			<htmlb:label 			for="input_field_2" text="Event Message:" />
			<htmlb:inputField id="input_field_2"	type="STRING" value="<%= EVENT_TEXT_2 %>" />
			<htmlb:label 			for="input_field_3" text="Event Message:" />
			<htmlb:inputField id="input_field_3"	type="STRING" value="<%= EVENT_TEXT_3 %>" />
			<htmlb:button 		text="Trigger Portal Event" onClientClick="alertValue();" />
		</htmlb:form>
	</htmlb>
</htmlb:content>

BSP application event receiver

The portal event send the data to the server, then I split the portal content in the server side.

Goto SE80 and create bsp application z_portal_bsp_receiver. Page event_receiver.htm

Layout of event_receiver.htm

<%@page language="abap" %>
<%@extension name="htmlb" prefix="htmlb" %>
<%@extension name="bsp" 	prefix="bsp" %>

<htmlb:content design="design2003">
	<htmlb:page title="">
		<htmlb:form>
			<bsp:portalEvent name="test_event" namespace="com.testNamespace" />
			<htmlb:label 		for="text1" text="Event Text:" />
			<htmlb:textView id="text1"  text="<%= event_text_1 %>" />
			<htmlb:textView id="text2"  text="<%= event_text_2 %>" />
		</htmlb:form>
	</htmlb>
</htmlb>

OnInputProcessing Event Handler
	data: event type ref to if_htmlb_data.
	data: event_dataobject type string.
	data: event_sourceid type string.
	data: event_namespace type string.
	data: event_name type string.
	Data: wa_string type string.
	Data:lt_string like table of wa_string.
	
	event = cl_htmlb_manager=>get_event_ex(
		runtime->server->request ).
	
	if event is bound.
	  if event->event_name eq 'portalEvent'.
	    event_dataobject = event->event_server_name.
	    event_sourceid = event->event_defined.
	    split event->event_id at ':'  into event_namespace event_name.
	    if event_namespace = 'com.xiaohong' and
	       event_name = 'test_event'.
	   		 Split event_dataobject at '*' into table lt_string.
	 			 Read table lt_string into wa_string index 1.
				 event_text_1 = wa_string.
	 			 Clear wa_String.
 				 Read table lt_string into wa_string index 2.
  			 Event_text_2 = wa_string.
    	endif.
	  endif.
	endif.

First we have to configure the different system into Portal using Single Sign On(SSO).

Configure systems into portal

Configure system landscape

Logon the portal as administrator ->system administration->system configuration->system landscape->create folder name and id. Under new folder create system and choose dedicated Application server for R/3 system and name and id, You have to configure each systems you used in the portal.

Open the new system and modify the property editor, enter all the system technical information: host, port, client, system id; system number. Editor system alias for the new system, alias is used to identify the backend system.

Configure single sign on(SSO) to portal and abap system

Logon the portal as administrator->system administration->system configuration->keystore administration->download SAPLogonTicketKeypair verify.der into local pc and unzip it. Logon to ABAP system user, go to STRUSTSSO2 and import verify.der

Configure user and role on portal

Logon the portal as administrator->user administration->users->create user.

Enter the same user as backend ABAP system.

Content administration->portal content->new role->create role ->open the object for setting->navigation->entry point

User Administration->Roles->edit, assign the user to the role

Configure iview

Logon portal as administrator->content administration->portal content->

Create Iview, add all the four BSP and WDA application into Iview
create page: add all the iview into page by delta link
Portal content->folder ->add iView to role->Delta Link

Add page to the role by Delta Link

Creating new context node

METHOD handlefrom_select_view .

* Get information about selected table
  DATA: lo_nd_tabledata TYPE REF TO if_wd_context_node,
        lo_el_tabledata TYPE REF TO if_wd_context_element,
        ls_tabledata TYPE wd_this->element_tabledata,
        lv_tabname TYPE string.
* navigate from  to  via lead selection
  lo_nd_tabledata = wd_context->get_child_node( name = wd_this->wdctx_tabledata ).
* get element via lead selection
  lo_el_tabledata = lo_nd_tabledata->get_element( ).
* get single attribute
  lo_el_tabledata->get_attribute(
    EXPORTING
      name =  `TABNAME`
    IMPORTING
      value = lv_tabname ).
  TRANSLATE lv_tabname TO UPPER CASE.

* build new context data
  DATA: lo_nd_info_root     TYPE REF TO if_wd_context_node_info,
        lo_nd_info_dbtb     TYPE REF TO if_wd_context_node_info.

  lo_nd_info_root = wd_context->get_node_info( ).
  lo_nd_info_dbtb = lo_nd_info_root->add_new_child_node(
                      name                   = 'DB_TABLE'
                      static_element_type    = lv_tabname
                      is_mandatory           = abap_false
                      is_mandatory_selection = abap_false
                      is_multiple            = abap_true ).

* create a reference to data table
  DATA: lr_db_tab TYPE REF TO data.
  FIELD-SYMBOLS: <fs_db_tab> TYPE ANY TABLE.
  CREATE DATA lr_db_tab TYPE TABLE OF (lv_tabname).
  ASSIGN lr_db_tab->* TO <fs_db_tab>.

* read contents of the database
  SELECT * FROM (lv_tabname)
           INTO CORRESPONDING FIELDS OF TABLE <fs_db_tab>
           UP TO 100 ROWS.

* bind the table to context
  DATA: lo_nd_dyn     TYPE REF TO if_wd_context_node.
  lo_nd_dyn = wd_context->get_child_node( name = 'DB_TABLE' ).
  lo_nd_dyn->bind_table( new_items = <fs_db_tab> ).

ENDMETHOD.

Adding a new table based on a dynamically created context node

METHOD wddomodifyview .

  DATA: lo_group TYPE REF TO cl_wd_group,
        lo_table TYPE REF TO cl_wd_table,
        lo_nd_dn TYPE REF TO if_wd_context_node.

  IF first_time EQ abap_true.
    lo_group ?= view->get_element( id = 'GROUP_1' ).
    lo_nd_dn  = wd_context->get_child_node( name = 'DB_TABLE' ).
    lo_table  = cl_wd_dynamic_tool=>create_table_from_node(
                    ui_parent = lo_group
                    table_id  = 'TABLE_DB_TABLE'
                    node      = lo_nd_dn ).

    lo_table->set_visible_row_count( value = 20 ).

  ENDIF.

ENDMETHOD.

The dish is composed of tree different components.

Mashed Potatoes

• Potatoes
• Butter
• Milk
• Garlic powder
• Salt
• Pepper

Instructions

1. Cut in to large chunks and boil the potatoes until soft
2. Drain the water
3. Mash the potatoes while adding butter, garlic powder, salt & pepper
4. Add milk depending on the desired softness

Mushrooms

• Mushrooms
• Onion
• Garlic [1 or 2 cloves]
• Olive oil
• Red wine
• Worcestershire sauce

Instructions

1. Chop up onions, mushrooms & garlic
2. Add oil garlic and mushrooms to a pan and cook on low heat
3. After a few minutes when the veggies have sweated a bit add a red wine and Worcestershire sauce for flavour and colouring
4. Wait until the liquid reduces

Steak

There are many variations of how to cook a steak.  I’ve followed a typical approach of seasoning the meat on both sides with salt and pepper.  Then on a hot pan flash the meat on both sides [2 minute each] add some butter and give another 2-5 minutes on low heat for the meat to cook [depending on how rear you want it].  Let the steak rest for another 3-5 minutes.

When all the components are done put everything together and serve.

• RTTI: RunTime Type Identification – is used to get the definition of existing variables or existing types
  
• RTTC: RunTime Type Creation – is used to create new variables with any definition; they must be followed by the ABAP statement CREATE DATA … TYPE HANDLE … to create the variable

RTTI and RTTC may be called using methods in CL_ABAP_*DESCR classes. Each class have both RTTI and RTTC methods.

Here is a quick example that illustrates the power and elegance of creating a table:

DATA: lo_lineType   TYPE REF TO cl_abap_structdescr,
      lo_tableType  TYPE REF TO cl_abap_tabledescr,
      lt_key        TYPE abap_keydescr_tab.

lo_lineType ?= cl_abap_typedescr=>describe_by_name( 'SPFLI' ).
APPEND 'CARRID' TO lt_key.
APPEND 'CONNID' TO lt_key.

lo_tableType = cl_abap_tabledescr=>create(
                  p_line_type   = lo_lineType
                  p_table_kind  = cl_abap_tabledescr=>tablekind_sorted
                  p_unique      = abap_true
                  p_key         = lt_key ).

* now lets create some data
DATA: lo_itab TYPE REF TO data.
CREATE DATA lo_itab TYPE HANDLE lo_tableType.

As you can see the steps are quite simple and the result is a standard SPFLI table.

Very simple to make recipe.

Ingredients

• 2 basa fillets, cut into bite-sized pieces
• 2 leeks, chopped
• 6 small potatoes, diced
• 1 tsp minced garlic
• 300 mL 2% milk
• 500 mL low sodium chicken broth
• 2 tbsp butter
• 1 onion, chopped
• pinch of black pepper

Instructions

1. In chicken broth, boil potatoes till tender (~ 30 min).  Then add milk.
2. Sauté onion and garlic in butter (~ 3 min).
3. Add leeks; simmer (~3 min).
4. Add fish and pepper; simmer (~10 min).
5. Once potatoes are mashed, combine mixture; stir well until desired consistency.  Serve.

I’ve picked one of the first google search results [recipe].  Used the ingredients and cooked the contents based on my personal observations & taste.

Ingredients

• olive oil
• 2 medium onions, chopped
• 3 medium carrots, cut into 1/4-inch rounds
• 3 celery ribs, cut into 1/4-inch thick slices
• 1 (6- to 7-pound) chicken
• 2 quarts chicken broth or canned low-sodium broth
• 1 quart cold water, or as needed
• 4 sprigs of fresh parsley
• 3 sprigs of fresh thyme or 1/2 teaspoon dried thyme
• 1 bay leaf
• Salt and freshly ground black pepper
• 2 cups egg noodles

I’ve started by chopping the vegetables, then browned them slightly in the bot.  That followed by adding chicken broth, water and boiling the contents for a good hour. I’ve concluded the dish by adding the noodles for 10 minutes and adding pre made chicken bits.

  DATA: gt_itab       TYPE SOME_TABLE.
  DATA: go_salv       TYPE REF TO cl_salv_table.
  ...
  TRY .
      cl_salv_table=>factory(
        EXPORTING
          list_display    = if_salv_c_bool_sap=>false
        IMPORTING
          r_salv_table    = go_salv
        CHANGING
          t_table         = gt_itab ).
    CATCH cx_salv_msg.

  ENDTRY.

  go_salv->display( ).

I followed the recipe of the Bolognese sauce outlined here by one of Gordon Ramsay’s recipes.  The end result was a deliciousness creamy texture of the sauce that really uplifted the flavour of the dish.  Relatively simple process resulting in complicated flavour.

Ingredients

• 1 onion [which I have to admit I forgot to add]
• 1 large carrot
• 2 cloves of garlic
• Dried oregano
• Ground beef
• Ragu pasta sauce
• Red wine
• Milk
• Worcester sauce