You are trying to navigate with anonymous user to a Web Dynpro page/iView and get the portal logon screen.
Other terms

Guest access, authentication schema, security, DSM, Web Dynpro Proxy page
Reason and Prerequisites
By default, the portal does not allow navigation to Web Dynpro content with anonymous user.This note is valid from NetWeaver 7.0 SP Stack 12.This note is relevant for Web Dynpro iViews and pages that run in the Web Dynpro Page Builder (the ‘Code Link’ property of the iView/page is set to com.sap.portal.wdintegrator.WebDynproIntegrator/com.sap.portal.wdintegrator.WebDynproIntegratorPage respectively).Solution

You have to perform the following steps to enable running Web Dynpro iViews/pages with anonymous user:
1. Make sure that the Web Dynpro application runs without login when you navigate to this application as a standalone application (not via the portal).2. From the Portal Catalog, open the iView/page property editor and set the property ‘Authentication Scheme’ to ‘anonymous’. Perform this step for all Web Dynpro iViews/pages that you are planning to run with anonymous user.3. Add the iView/page to a portal role.4. Assign the role to the ‘Anonymous Users’ group.5. Navigate to the permission editor: ‘System Administration’ -> ‘Permissions’ -> ‘Portal Permissions’.6. Browse to the folder: ‘Security Zones’ -> ’sap.com’ -> ‘NetWeaver.Portal’ -> ‘low_safety’.7. Open the component ‘com.sap.portal.appintegrator.sap’ -> ‘WebDynproPageBuilder’.8. Grant the Read and End User rights to the ‘Anonymous Users’ group.9. Perform Step 8 for the following components:a) com.sap.portal.dsm -> Terminatorb) com.sap.portal.epcf.loader -> WdScriptBlockProviderc) com.sap.portal.appintegrator -> Loading

After upgrading Solution Manager 7.0 to EHP1 and higher the Portal Activity Reporting is no longer available for SAP NetWeaver 04 Enterprise Portal.

Other terms

Portal Activity Reporting, Activity Data Collector, Portal, EP, PADC, Solution Manager, EHP1, com.sap.sup.admin.bwextract.E2ePadcExtractor, EP6

Reason and Prerequisites

Up to Solution Manager 7.0 SP17 the Portal Activity Reporting in Solution Manager was based on the Portal Activity Report data where the data was stored in the Portal database. With Solution Manager 7.0 EHP1 the Portal Activity Reporting in Solution Manager was re-designed, now using the Portal Activity Data Collector (ADC) data and storing it in the BI of Solution Manager. This provides more flexibility and options in analysing the data. As of Solution Manager 7.0 EHP1 the Portal Activity Reporting based on Portal Activity Report data was disabled in Solution Manager.

Solution

There are three possible options to get Portal Activity Reporting data for your SAP NetWeaver 04 Enterprise Portal:
1. Workaround with Portal iViews:
The Portal Activity Reporting data used in Solution Manager 7.0 up to SP17 is also accessible via iViews. A description how to create these iViews is available on help.sap.com
http://help.sap.com/saphelp_nw04/helpdata/en/fb/144120ea5b4e9c9385d493a578d6c9/frameset.htm2. There will be a fix with Solution Manager 7.0 EHP1 SP stack 22 so the Portal Activity Reporting Extractors can also be activated for SAP Netweaver 04 Enterprise Portal.
In addition the Enterprise Portal needs to be at least on SAP Netweaver 04 SP21.3. Upgrade the Enterprise Portal to NetWeaver 7.0 and setup the Portal Activity Reporting according SAP note 1309740.

NW2004 (NW04) engine installation on HA system finished successfully and engine page can be launched -> / index.html.
Portal installation fails with the below exceptions:
1. java.lang.NoClassDefFoundError: iaik/utils/Base64Exception
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.(DBConnectionPool.java:108)
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.(PersistenceHandler.java:38)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.(ConfigurationCache.java:149)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.< init>(ConfigurationManagerBootstrapImpl.java:49)
at com.sap.engine.configtool.batch.BatchConfig.initDBConnetion(BatchConfig.java:64)
at com.sap.engine.configtool.batch.BatchConfig.go(BatchConfig.java:52)
at com.sap.engine.configtool.batch.BatchConfig.main(BatchConfig.java:94)
2. ERROR: Not deployed. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application sap.com/com.sapportals.dqe.beans..
Reason: Exception during generation of components of application sap.com/com.sapportals.dqe.beans in container EJBContainer.; nested exception is: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/com.sapportals.dqe.beans in container EJBContainer.
attached exception.
Caused by: java.lang.NoClassDefFoundError: com/metamatrix/platform/service/api/exception/ServiceException
at java.lang.Class.getDeclaredConstructors0(Native Method)
The exceptions can be found in sapinst_instdir folder in java.log/sapinst.log/sapinst_dev.log files.

Other terms

Portal installation, Installation, HA, High Availability, NW04, NW2004, NetWeaver 2004
Reason and Prerequisites

Prerequisites:
SAP NetWeaver 2004 all SP’s.
Reasons:
In HA system, the portal installer may fail to locate the jar file mentioned below during the installation.
Solution

For exception No 1:
A. Make sure SAP Note No. 810159 (Subsequent installation of SAP JAVA CRYPTO TOOLKIT) was applied.
Or follow instructions in: http://help.sap.com/saphelp_nw04/helpdata/en/8d/cb71b8046e6e469bf3dd283104e65b/content.htm
B. Verify the following:
- iaik_jce.jar file should be located at: #.\usr\sap/H36/DVEBMGS36/SYS/global/security/lib/engine
- iaik_jce_export.jar file should be located at: #.\usr\sap/H36/DVEBMGS36/j2ee/deploying/lib
If both files are not stored there, please locate the files manually and then run the sapinst again.
For exception No 2:
Please restart the engine and then run the sapinst again.

In HTMLB Editor the style of the ordered list or the “Numbered List” is not the same as the text added to the editor.
Other terms

HTMLB for Java
Reason and Prerequisites

Program error
Solution

The issue described above will be fixed by an HTMLB for Java patch.In section “SP Patch Level” you can find information which patches contain the respective correction.
Please install this patch or a newer one (HTLMB patches are always cumulative).
If the section “SP Patch Level” is not available or the information about which patch contains the correction is missing, this means that this has not been determined, yet. In this case please re-check this note at a later point of time.

Downloading HTMLB for Java Patches

All HTMLB for Java patches are available on SAP Service Marketplace. Note 330793 explains how to download patches from SAP Service Marketplace.

Release Specific:
NW04S/ NW 7.00 / NW04S Ehp1/ NW 7.01/ NW04S Ehp2 / NW 7.02

The patch for this release will be a SCA. Deploy the sca directly using SDM.
Recommendation for Portal Usage
In the “SP Patch Level” tab, if there is no software component for EPBC2, then please apply the latest relevant EPBC2.SCA which is available in the service market place.
Recommendation for Portal Independent Usage
In the “SP Patch Level” tab, if there is no software component for SAPJTECHS, then please apply the latest relevant SAPJTECHS.SCA which is available in the service market place.

NW07 / NW 7.10 / NW07 Ehp1 / NW 7.11

The patch for this release will be a SCA. Deploy the sca directly using SDM.
Recommendation for Portal Usage
In the “SP Patch Level” tab, if there is no software component for EPBASIS, then please apply the latest relevant EPBASIS.SCA which is available in the service market place.
Recommendation for Portal Independent Usage
In the “SP Patch Level” tab, if there is no software component for FRAMEWORK, then please apply the latest relevant FRAMEWORK.SCA which is available in the service market place.

Note:

Due to the fact that many of the SDAs included in the SCA are offine deployment, the engine is restarted during the deployment. An update is only required on the engine.

Time required:

The required time depends on whether the engine has to be restarted. In addition, the time required for the restart is determined by the applications installed on the engine.

When the KM API is used to manage documents in KM folders, there is incomplete trace information written by SAP Portal application to the SAP Activity Data Collector (ADC) log files, for the ADC OpCodes which return information about the portal request (see http://help.sap.com/saphelp_nw70/helpdata/en/47/8ab49e1b141e1ee10000000a42189d/content.htm)

Reason and Prerequisites

Reason:
The portal request (IPortalComponentRequest, see
http://help.sap.com/javadocs/NW04S/current/ep/com/sapportals/por tal/prt/component/IPortalComponentRequest.html) is not set in the
PortalComponentRequestCache. The class is used to store the portal request for the current user, when the user navigates in the KM.
Prerequisite:
You must have access to portal request.
Solution

In order to log the ADC OpCodes in the custom application set the IPortalComponentRequest to the class PortalComponentRequestCache(PortalComponentRequestCache.setPortalComponentRequest(request)), the class can be find in the jar: bc.util.private_api.jar, package:com.sapportals.wcm.util.pcr.

NW 700 SP20 , Portal SP20
Portal logon page does not display languages other than English, while the user admin and SAP NetWeaver Administrator logon pages do.
Other terms

Logon, Portal, Translation,NW 700 SP20
Reason and Prerequisites

The portal logon page uses the portal archive com.sap.portal.runtime.logon.par. In the portal archive under PORTAL-INF -> lib -> umelogonbase.jar , you should find the language files in the jar file. If the par file in your file system does not include these language files, then this is the reason for the missing translations.
Solution

Unzip and deploy the attached file com.sap.portal.runtime.logon.par with the PortalAnywhere App.
Links:
http://host:50000/irj/servlet/prt/portal/prtroot/PortalAnywhere.defaulthttp://host:50000/irj/servlet/prt/portal/prttarget/adc/prteventname/selectArchive/prtroot/PortalAnywhere.Go

The attached par file is only valid for SAP NetWeaver 7.0 SPS 20!!!

The Approve and Reject buttons are missing in UWL preview area or the items are missing form context menu.

Reason and Prerequisites

The configuration XML file cannot be generated due to the missing RFC destination for the provider connector. The result is that the item type information, for example, available actions, dynamic parameters, visualization parameters, cannot be retrieved from the backend.

Solution

1. Refer to SAP note 1133821. Check that, after applying, the destination names and the UWL connector names exactly match, even considering case-sensitiveness.
2. Reactivating connector. See the three steps below.
After you have checked/prepared the RFC destination for future use:
2.1 Deactivate the respective connector in the UWL config UI from Portal->System Administration->System Configuration->Universal Worklist Press the respective “Deactivate” button. On the dialog with question: “Are you sure you want to deactivate the system?” press “Yes”. Make sure both checkboxes below are selected:
- Delete the registered configuration?
- Clear cache for the system?
2.2 Activate connector by pressing the “Activate” button.
2.3 Press “Register”

When browsing the KM navigation iView depending on the
KM Security policy(i.e. attached AclSecurityManager and assigned ACL permissions) and according to the internal folders’ structure in KM repositories(e.g. a large number of folders 500 and above) as a
result the process of listing resp.repository contents could be really slow.

Other terms

Bad performance in KM navigation iView when using ACLs

Reason and Prerequisites

Inappropriate mechanism when checking ACL permissions against a huge
number of folders(i.e. serveral hundred folders)
Releases where the issue is observed:
o SAP Netweaver 7.00 SP20 and before
o SAP Netweaver 7.01 SP05 and before
o SAP Netweaver 7.02 SP01 and before

Solution

A) The issue is cleared in these deliveries:
o KMC BASE COMPONENTS 7.00 SP21
o SAP EHP1 Patch 1 for KMC BASE COMPONENTS SP05
o SAP EHP1 FOR KMC BASE COMPONENTS SP06
o SAP EHP2 FOR KMC BASE COMPONENTS SP02
B) Possible workaround before the official deliveries:
Refactoring the internal repository’s structure,e.g. if we have
500 folders on one level for bettering the performance we could
set 10×50 structure,i.e. one level of 10 folders and 50 folders
inside each one of the 10 folders. After that set the ACL permissions according to the new folders’ structure.
The main purpose in this workaround is to make a more balanced folders structure,e.g. 500 folders could be also restructured as:
25×20, 50×10, etc. according to the landscape that the administrator
needs to achieve.