Skip to Content

INSTALLATION INSTRUCTIONS: Cohesion Mobile for SAP

 

Purpose
This document will guide you through the installation of Cohesion Mobile on your SAP system. All steps for this procedure should be completed by your SAP system administrator. You will require access to your application server file system to complete the installation. Note: it is recommended to import Cohesion Mobile into your development system first. You should test all enhancements before moving to the production system. Cohesion applications are delivered in the custom namespace /COHESION/ so they cannot interfere with existing SAP programs in your system.

Pre-Requisites
The Cohesion SAP mobile is available for SAP versions 4.7, ECC 5.0, and ECC 6.0 including Enhancement Packs. The applications are BSP applications so your system should be configured for web access using he SAP Internet Transaction Server or the ABAP Web Application Server.

 

  1. Goto transaction SICF and locate these services and active them 

    /sap/public/bc/its/mimes

  2. Check tranaction SPAD to make sure that printer LP01 is either locked or not connected to a valid printer. If the printer is not locked, the output may be printed to paper instead of being displayed on your mobile device

image

 
Locating your DIR_TRANS Folder
To import the Cohesion Mobile transport into your SAP development system, you need to locate your DIR_TRANS folder. Run transaction AL11 in your development system and look for an entry for DIR_TRANS.

image

Input Files
You should have received two transport files from Cohesion as listed below. The files need to be transferred to your SAP development system into the DIR_TRANS folders. Replace the path /usr/sap/trans with the relevant path from your DIR_TRANS variable.

  • “Co” File: This file is named K90XXXX.DEV and should be stored in the application server /usr/sap/trans/cofiles.
  • Data file: This file is named R90XXXX.DEV and should be stored in the application server folder /usr/sap/trans/data

It is important, that both the files mentioned above (K90XXXX.DEV , R90XXXX.DEV) have identical permissions as the files which are already located in these directories.


Adding the Request to the Transport Queue

After copying the files onto your application server in the relevant transport directories, logon to SAP and run the STMS transaction. You should choose Import Overview and then double-click on your development system import queue.

image

Figure 1 Choose Import Overview from transaction STMS

image

Figure 2 Double click on your development system queue

image

Figure 3 Select Other Requests->Add to add the Cohesion transport to the queue. Enter the transport number received from Cohesion (e.g. DEVK90XXXX).

image

Figure 4 After adding the transport to your DEV queue, click on the number and click the import request button

image

Figure 5 Set the import parameters to load the transport and click the green tick symbol to import


License Key Installation

After installing the transports, you may need to install your license key with transaction /COHESION/LICENSE.
Note: Cohesion Mobile for SAP allows the user to enter their license directly through the phone also.

image

Figure 6 Run transaction /COHESION/LICENSE to install your license key. This is required in each SAP system in your landscape.

image

Figure 7 Enter the user name, product ID and license key. You can upload a file if you have multiple licenses also.

image

Figure 8 You should receive a summary report like the one shown. Licenses are stored in table /COHESION/LIC.

image

Figure 9 You can check which licenses are installed in your system with transaction SE16 and table /COHESION/LIC


Activating Web Services

Before you can start using the Cohesion Mobile for SAP, you may need to activate the Cohesion Web Service.

Go to Transaction SICF.

image

Figure 10 Accept Defaults and Press Execute
Navigate to default_host -> sap -> bc -> bsp -> cohesion. Right Click cohesion and choose activate.

image

Figure 11 Right click cohesion and select “Activate Service”

image

Figure 12 select this button to activate all the Services under cohesion
You should now be ready to run your Cohesion Mobile Transactions in your development system.

Testing the Installation
You can test the installation using the Google Chrome or Apple Safari web browsers. The address of the application should be:

https://your-sap-hostname:your-ssl-port/sap/bc/bsp/cohesion/ap

For example, the address for our Cohesion test system is below. This is a private address that is not available outside the Cohesion network. Contact us at support@cohesion.biz if you are unable to connect.

https://eccqas.cohesion.biz:8025/sap/bc/bsp/cohesion/ap/bc.htm

To test on the iPhone, email the link to your phone. Click on the link from your email and it should open the application in your browser. Add the application to your home screen using the “+” button at the bottom of the browser.

image

Figure 13 Select “Add to Home Screen”


Configuring SSL for Web Applications (Optional)

1. Use transaction RSPFPAR to check the following system parameters and, if required, ask your system administrator to set them as follows:
For the authentication using SAP Logon tickets:
login/accept_sso2_ticket: 1
login/create_sso2_ticket: 2

2. HTTP and HTTPS services in transaction SMICM are set up (menu path: Goto -> Services (shift+F1)).
We recommend that you set the following for both services
TIMEOUT and PROCTIMEOUT to 300 or 600 (seconds)
Default: 60
The values are also set using system parameters (see above):
icm/server_port_# – Standard: 0: http, 1 or 2: https
For example:
icm/server_port_0 = PROT=HTTP, PORT=8000, PROCTIMEOUT=300, TIMEOUT=600
icm/server_port_2 = PROT=HTTPS, PORT=44300, PROCTIMEOUT=300, TIMEOUT=600
Please note that the setting VCLIENT=2 is not supported for iPad or iPhone use.

3. System PSE, SAP CryptoLib, SSL Server, SSL Client. Check transaction STRUSTSSO2 to see if these are implemented. If not, ask your system administrator to activate the certificates accordingly.

Moving to Production
After testing the programs, it is recommended that you create a new transport in your development system and copy the objects from the Cohesion transport. This simplifies the transport path for your enhancement.

image

Figure 14 Run transaction SE09 and click on the create icon on the toolbar

image

Figure 15 Select Workbench request as shown

image

Figure 16 Enter the details of the transport to route through your normal transport path

image

Figure 17 Right click on your transport and choose the Include Objects option

image

Figure 18 Enter the original Cohesion transport number as shown. This will copy all the Cohesion programs to your new transport

image

Figure 19 Your transport now contains the Cohesion Mobile Transactions. You can release this transport and migrate to production with your normal process.

Further Questions

How do you change to a different SAP Client or Language?
Just add the following to the URL
For the Client = ?sap-client=
For Language = ?sap-language=de (Use the Language Codes in SMLT)
Example for Both
?sap-language=fr&sap-client=300

Thank you for choosing Cohesion Mobile Transactions. If you have questions about the upload or require support, please contact Cohesion via our web-site (http://www.cohesion.biz) or email support@cohesion.biz for more details.

 

License
Cohesion Evaluation License
Grant : Licensee is granted a non-exclusive, non-transferable license for an indefinite period for up to 5 named users only (“Term”) for the purpose of evaluating :
Description : Cohesion Mobile for SAP

 

Limited Access: Licensee will use the software only on the above mentioned system, with a maximum of 5 users and provide access only to its employees or contractors who are subject to confidentiality provisions similar to those set out in this license. Licensee will use the software only for the purpose of valuating and refrain from using the software in a production environment. Should these limitations be
violated, the normal license fees will be charged.

Title: The Software belongs to Cohesion, as do any intellectual property rights in it. Licensee will not copy, modify, decompile or assign the software.

Confidentiality: Licensee will keep any information regarding the software confidential, both during and after the term, unless that information becomes public. This provision will survive this License. Cohesion may enforce its rights by seeking injunctive relief.

No warranty: The software is provided on a “as-is” basis. The risk of use arising from performance of the software is licensee’s sole responsibility. Neither cohesion, nor any of its suppliers can be held liable for any damage, of whatever sort, arising from licensee’s use of the software. ALL STATUTORY WARANTIES RELATING TO MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.

Termination: When the term ends, licensee will either : (a) obtain from Cohesion a license to continue using software or (b) immediately cease using the software, remove all copies from any of it’s computers or computer systems, return Software to Cohesion, and certify that these actions have been carried out 6.

Services: all services requested by Licensee from Cohesion in relation to this evaluation license will be charged on a time and material basis according to the normal Cohesion rates.

Effect : By installing this software the licensee agrees to be bound by its terms.
Portions of this software are subject to the license below.
Copyright (c) 2007-2009, iUI Project Members
All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

* Neither the name of the iUI Project nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
“AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

    1. John Carpinelli
      Hi Greg,

      You are correct about the Apple store. Corporate customers want to change their applications any time without third party approval. That is an issue with native apps on the iPhone. The customer can customize the Cohesion mobile screens using ABAP and basic HTML skills.

      When using the Cohesion app, the iPhone connects directly to a BSP application running on the SAP server. Usually, there will be no proxy server between the iPhone and the SAP server.

      If the iPhone or iPad user is on the company wireless network, there should be no proxy servers or remote access required. Wifi will often be deployed in meeting rooms and warehouses so devices can connect directly to SAP.

      If the user is outside of the office, the iPhone must connect to the corporate network via VPN. Apple provides enterprise deployment guides on their web-site explaining how to deploy the iPhone VPN for remote access. Once connected through the VPN, most companies will not have a proxy server between the iPhone and SAP.

      The applications are using BSP rather than webdynpro. BSP provides more flexibility on the user interface and allows us to improve the user experience for touch screen devices.

      (0) 

Leave a Reply