Skip to Content
Former Member
Former Member
October 1, 2005 2 minute read

XI: New features in SP14

Follow RSS feed
0 Likes 25 Views 8 Comments

Some new features in XI – SP14 and how to use those features are discussed here.

Java Sections

There is a separate section in which we can define global java variables which can be used in functions in Message Mapping. I found this ‘Java Section’ button in the toolbar in SP13 itself but it was disabled. I was wondering what that button was for and finally in SP14 that button got enabled as ‘Java Sections’.

image

To any XI person with Java background, this ‘Java Section’ in Message Mapping gives a perspective as a Java Class. In ‘Java Section’, there are three sections.

  1. Global variables (Global Scope)
  2. Initialization Section (Like a Java Constructor) and
  3. Clean-Up Section (Like a Java Destructor)

image

So, here we can put all our java coding which are common to one message mapping and use them effectively in all the functions used in that particular message mapping.

image

We can simply use the global variable in the functions used in message mapping. This new feature of ‘Java Section’ available in SP14 can replace the GlobalContainer provided previously by SAP to some extent.

Adapter specific Message Properties

FileAdapter

image

JMS Adapter

image

Mail Adapter & SOAP Adapter

image

OS Command in JDBC Adapter

One interesting thing I found is that ‘Run Operating System Command’ is also found in the configuration part of JDBC Adapter apart from File Adapter configuration.

image

I might have missed a lot of new features which might be available in SP14. But all these features mentioned above in this blog are what I identified as a new feature in a first glance.

Assigned tags

Related Blog Posts

    Related Questions

      8 Comments
      You must be Logged on to comment or reply to a post.
      • Former Member
        …is this adapter specific message properties , you have given screen shots , but i fail to understand the significance,
        ll be good if you can explain

        Thanks
        Saravana

        • Hi Saravana,
          I am not sure about its significance because it is a new feature but I assume that the adapter settings can be set dynamically using this message properties (i mean some specific tags/elements in message). I also did some scenarios to find its significance but i am unable find anything.

          I am also unable to find it from help.sap.com. I think we had to wait till 9th Oct (the date when that particular page on help.sap.com expires) to get an updated page 🙂

          I will surely put it as a blog if I find its significance.

          Best regards,
          Felix

          • Former Member
            Felix~

            Could you please explain this -‘ I think we had to wait till 9th Oct (the date when that particular page on help.sap.com expires) to get an updated page :), please?

            Thank you and best regards

            Kartik Iyengar~

            • Hi kartik Iyengar,

              It is a metatag detail. It can be easily got from view page info in firefox. e.g.

              or
              (HTTP header):
              Expires: Wed, 26 Feb 1997 08:21:57 GMT

              The date and time after which the document should be considered expired. Web robots may delete expired documents from a search engine, or schedule a revisit.

              Browsers use this to save contents in cache and after this particular date mentioned in the metatag, the browser requests once again to the server to reload the new updated contents.

              Here in this weblog, I was actually refering to this particular page.
              http://help.sap.com/saphelp_nw04/helpdata/en/0d/00453c91f37151e10000000a11402f/content.htm
              But today I see that the expiry date is set to 11th Oct and modified on 21st Jul. May be I think expiry date is dynamically set to keep in cache for the next 10 days. 😉

              What ever may be.. what we need is some source for help to update ourself with new features. May be we have to wait a little longer until that page is updated or someone bloging about that particular feature sharing his experience. 🙂

              Best regards,
              Felix Jeyareuben

      • Steven De Saeger
        Hi,

        Another feature that should have been implemented ( according to SAP’s reply to our open oss note – did not yet have a chance to test it 🙂 ) and which is not documented at all:

        When you use the CIDX adapter in combination with BPM then any returned RA and RAE messages should now be transformed into XI status messages and be returned to your BPM so you can use them for error handling …

        Regards,

        Steven