Portal Configuration (Optional)

These steps are only relevant if you are including and SAP portal in your setup

1. Setup a system alias for the SAP R/3 system and R/3 user reference system

The application needs to determine which SAP backend systems to connect to. The SAP reference system for user authentication/SAPLOGON ticket creation and the SAP component system must be configured. In most landscapes there is already a connection setup between portal and SAP R/3 and this can be re-used.

1A. Log on to the Portal as a System Administrator. Navigate to the System Landscape area and find connection for SAP R/3 system.

1B. Assign alias
For your reference system add an alias called : MCC_R3_REF

For your component/logical system add an alias called : MCC_R3_SYS

Note : in a landscape where one portal is assigned to one SAP R/3 system (the most common landscape) you will assign the reference and component alias to the same SAP R/3 connection

2. Set the Security Zone
Security zones enable a system administrator to control which portal components and portal services a portal user can launch. You need to allow access to the Promenta technical components.

2A. In the portal navigate to System Administration –> Permission
2B. In the tree structure navigate to :Security Zones –> Promenta.com –> myCommsCentre
2C. Right click on the myCommsCentre folder and choose Open Permissions.
2D. Add the Everyone group (which is delivered by SAP and all users have)
2E. Click the End User flag
2F. Accept the popup warning

3. [Netweaver 730 and above only] Start services

Following deployment the portal apps delivered will be in a stopped state. The portal should start them automatically when they are accessed. This can be seen in the screenshot below.

Recommendation : it is recommended to manually start all the promenta portal apps so that any errors can be seen and dealt with at install time rather than later during testing phase.

Start all Promenta apps listed on your system – not all apps shown below will be present on your system

CLICK TO ENLARGE
CLICK TO ENLARGE

4. Create content
The customer must create the content (pages, roles, worksets etc) so that the Promenta content can be placed on your portal.

4A. Content on NW7.0

Create iview based on par file com.promenta.pct.wfbsp.par

4B. Content on NW7.3

Create an iview based on portal application com.promenta.pct.wfbsp as shown under :
Content Management –> Portal Content –> Portal Applications

CLICK TO ENLARGE
CLICK TO ENLARGE
To create the Iview :
Expand the portal app to show the Component WfBSP
  • Right-click on the portal app above –> Copy
  • Navigate to PCD location under Content Management where you want the IVew to be inserted
  • Right-click on folder –> Paste as PCD object
  • Assign iview name in normal way

5. (Optional) Setup IView parameters

Only necessary if you are creating your own content as per step 4.

Once the Iview is created (Step 4) apply the following changes to the iview parameters

Note : Check code link holds value com.promenta.pct.wfbsp.WfBSP

– Height Type (com.sap.portal.iview.HeightType) = FullPage
– Isolation Method (com.sap.portal.reserved.iview.IsolationMode) = URL
– Name (com.sap.portal.pcm.Title) = an appropriate iview title
– Logical System (SystemIdentifier) = Alias of the backend SAP ECC system. This would normally be set to MCC_R3_SYS unless running in a multi-system landscape.
– MCC Webform id (FORMID) = the technical id of the webflow in the backend SAP ECC system.

6. (Optional) Assign Iview

Only necessary if you are creating your own content as per step 4.

Assign Iview to portal pages, worksets and roles in the normal way

 

Scroll to Top