SAPinst then creates by default client 001 as the production client for the ABAP part of your SAP system. The ABAP part of the system initially contains only clients 000 and 001.
You can install the Java Add-In to an already existing ABAP system.
You can change the default names of the Java users J2EE_ADMIN, J2EE_GUEST and SAPJSF during the input phase of the installation.
SAP System ID
Instance Number: Technical identifier for internal processes, consisting of a two-digit number from 00 to 97.
ABAP/Java Message Server Port
The external message server port uses the parameter rdisp/msserv with default value 36
The internal message server port uses the parameter rdisp/msserv_internal with default value 39
ABAP RFC User, Password
The user DDIC is normally used for the RFC logon ABAP RFC user. It has the required special administrator rights. Alternatively, you can use user SAP*.
Java users Administrator Name:
SAPinst sets the user name J2EE_ADMIN by default. If required, you can choose another user name according to your requirements.
SAPinst sets the following user names by default.
n For the Java part of an ABAP+Java system: J2EE_ADMIN
n For a Java system: Administrator.
Communication User Name: This user is used for the communication between the ABAP and the Java part of an ABAP+Java system. SAPinst sets the user name SAPJSF by default.
Master Password This password is used for all user accounts SAPinst creates and for the secure store key phrase. The length has to be 8-14 characters. Depending on your installation scenario there might be more restrictions.
Enterprise Portal URL The portal URL consists of the following:
http://
SLD HTTP Host The host name of the System Landscape Directory (SLD)
SLD HTTP Port The HTTP port of the Java system where the SLD is installed. The following naming convention applies:
5
SLD Data Supplier User and password n
If you want to install a local SLD, SAPinst creates this user during the installation. If you want to connect your system to an existing central SLD, you have to enter the existing SLD Data Supplier User and password of the central SLD during the installation.
We recommend that you name this user SLDDSUSER
SLD ABAP API User and password n
If you want to install a local SLD, SAPinst creates this user during the installation. n If you want to connect your system to an existing central SLD, you have to enter the existing SLD Data Supplier User and password of the central SLD during the installation.
We recommend that you name this user SLDAPIUSER
RFC User, Password The ABAP RFC user of the SLD ...
Code page The code page that is used by your database (Unicode or Non-Unicode).
Database schemata, Passwords The Java database schema is namedSAP
Running Adobe Document Services on Non-Supported Platforms
Adobe document services (ADS) are currently not supported to run natively on all platforms supported by SAP systems based on SAP NetWeaver, in particular on 64-bit platforms.
Procedure
To use ADS in SAP landscapes on non-supported platforms, install an additional standalone AS Java on a platform supported by ADS.
Usage Type Development Infrastructure
The SAP NetWeaver Development Infrastructure (NWDI) is the environment for all processes in Java-based development and software life-cycle management. You can centrally manage all development phases with the Change Management Service (CMS), from the definition of a central development environment for each software project through to quality management and production. The CMS controls the management of sources in the Design Time Repository (DTR) and archives in the Component Build Service (CBS). The component model adds metadata to Java-based projects, which is the basis for the new development process.
There are the following Java development scenarios with SAP NetWeaver:
n Scenario “Java Projects with Central Source File Storage”: development with central source code version control only Scenario “Developing Components with the NWDI”: all services of the Development Infrastructure and the SAP component model are used
SAP recommends to perform a domain installation.
1. Check that you have Domain Administrators rights.
Logging On to the SAP System
You need to check that you can log on to the SAP system using the following standard users.
ABAP Usersser User Name Client
SAP* 000, 001, 066
DDIC 000, 001
ABAP+Java UserUseAdministrator J2EE_ADMIN
Java Standalone Users Administrator Administrator
Logging On to the J2EE Engine
1. Start a Web browser and enter the following URL:
http://
Establishing the Portal URL
http://
Generating the SAP Solution Manager Key
1. In your SAP Solution Manager system, call transaction SMSY (System Landscape Maintenance).
Performing Initial ABAP Configuration
Configuring the transport management system
1,Set up operation modes transaction RZ04
2,Set up logon groups transaction SMLG
3,Set up administrators
4,Schedule background jobs
5,Install a printer
6,Configure the system log
Installing languages using transaction I18N:
Performing language transport using transation SMLT
Activating and configuring the integrated Internet Transaction Server (ITS),see SAP Note 742048
Post-Installation Steps for Adobe Document Services
1,Creating Role ADSCallers and Assigning it to ADSUSER(transaction PFCG).
Installation Check and Quick Tests for Adobe Document Services
Enter the following URL in your web browser:
http://
Checking the ABAP Connection
1. Log on to your SAP system.
2. Call transaction SE38.
3. Enter the name of the test report FP_PDF_TEST_00.
Performing Post-Installation Steps for CAF Core
In SLD
1. In the SAP System Landscape Directory (SLD), create a new project.
2. Create a new software component (SC) to be developed.
3. Create SCs of the build plug-ins for the dependent development component (DC). They are:
Archive Names
BI-MMR CAF-KM EPBC2 SAP_JTECHS
BI_UDI CAF-UM EP-PSERV SAP_PRT
BI-REPPLAN EC-JSTARTUP KMC-CM SAP-EU
BI-WDALV EP_BUILDT LM-TOOLS SAP-JEE
CAF EPBC SAP_BUILDT UWLJWF
4. Define the build plug-in dependencies created in step 3 above.
5. Define the SC dependencies created in step 2 above.
In CMS
1. In CMS, identify or create a domain.
2. Identify an existing track or create a new track for composite application development in
Landscape Configurator--> Creating a Development Track.
3. Add the SC created in step 2 in the section above to the track.
4. Add the runtime system of the track.
See Landscape Configurator--> Creating a Development Track--> Configuring Runtime Systems.
5. Check in the archives listed in the table below.
6. Import the archives into the track.
Configuring the BI Java Connectors
BI JDBC Connector
If you have not already done so, you must first deploy your datasource’s JDBC driver, performing the following steps:
a) Start the Visual Administrator. .
A) On your central instance host, change to the admin directory:
(path: \usr\sap\
B) Double-click go.bat.
b) In the Cluster tab select Server x--> Services--> JDBC Connector.
c) In the right frame, select the node Drivers on the Runtime tab.
d) From the icon bar choose Create New Driver or Data source.
e) In the DB Driver field in the Add Driver dialog box, enter a name of your choice for your JDBC driver.
f) Navigate to your JDBC driver's JAR file and select it.
g) To select additional JAR files, select Yes when prompted; if finished, select No.
Connection Properties for the BI JDBC Connector
USERNAME Data source user name User with at least reading authorization for the data source.(These authorizations differ according to the used data source.)
PASSWORD Data source password (your password)
URL URL string specifying the location of a database (used by the java.sql.DriverManager to determine which driver to use) jdbc:mysql://localhost/test
DRIVERNAME Class name of JDBC driver used for this connection com.mysql.jdbc.Driver
Checking the Connectors Implementation
After the configuration of the different connectors, you can perform a rough installation check by just displaying the different connector pages.
BI JDBC Connector http://
BI ODBO Connector http://
BI SAP Query Connector http://
BI XMLA Connector http://
Setting Environment Variable CPIC_MAX_CONV
1. Log on to your operating system as user
2. Set environment variable CPIC_MAX_CONV to a higher value (at least 200) and restart the system.
Performing PI-Specific Steps for SLD Configuration
Local and Central System Landscape Directory (SLD)
Mapping Security Role to User
1. Log on to the Visual Administrator of the J2EE engine of the SLD host.
2. Choose Cluster® Server® Services® Security Provider.
3. In the Runtime tab, choose Policy Configurations and then the column Components, and select the component
sap.com/com.sap.lcr*sld.
4. Switch to the Security Roles tab to display the assigned roles.
5. Select role LcrInstanceWriterLD.
The user SLDAPIUSER already exists with its security role LcrInstanceWriterLD.
6. Switch to edit mode and add user PIAPPLUSER with the same role LcrInstanceWriterLD.
.
Maintaining SLD Connection Parameters (ABAP API)
1. Log on to the SAP XI Integration Server System as user DDIC and call transaction SLDAPICUST. The screen Maintain SLD Access Data is displayed.
2. Choose Display <-> Change and proceed as follows:
a) Replace the existing SLDAPIUSER with PIAPPLUSER user.
For a central SLD, make sure you use the user with security role LcrInstanceWriterLD.
b) Make sure your entry is marked as Primary.
Only the entry marked as Primary is active.
c) Save your settings.
Checking the CR Data in the SLD (optional)
Since CR_Content.zip contains all available SAP components, the content of this file grows with time. Theextensions contain information about new components (new releases and Support Packages, for example).
This content in the SLD has to be updated from time to time.
Ensuring User Security
Recommendation
In all cases, the user ID and password are only encoded when transported across the network.
Therefore,
we recommend using encryption at the network layer, either by using the Secure Sockets Layer (SSL) protocol for HTTP connections, or Secure Network Communications (SNC) for the SAP protocols dialog and RFC.
Operating system user
SAPService
Oracle database user
SAP
SYSTEM ‒
SYS ‒
OUTLN ‒
DBSNMP ‒
ABAP+Java Users
SAP* User exists at least in SAP system clients 000, 001 and 066.
DDIC User exists at least in SAP system clients 000 and 001.
EARLYWATCH User exists at least in SAP system client 066.
SAPCPIC User exists at least in SAP system clients 000 and 001.
Administrator The name that you gave this user during the installation or the default name J2EE_ADMIN
Users for Adobe Document Services (ADS)
ADSUSER User exists at least in SAP system clients 000 and 001.
ADS_AGENT User exists at least in SAP system clients 000 and 001.
Data supplier user for System Landscape Directory (SLD) (optional) The name that you gave this user during the installation.The recommended name is SLDDSUSER.User exists at least in SAP system clients 000 and 001.
Note
SAPinst created this user automatically if you chose Configure local SLD during the installation.
ABAP API user for System Landscape Directory (SLD)(optional)
The name that you gave this user during the installation. The recommended name is SLDAPIUSER.
User exists at least in SAP system clients 000 and 001.
DI Configuration
Choose each of the items you need: Design Time Repository Configuration, Component Build Service, Change Management Service.
Importing the Build Archives
1. Before the first check-in and import of the build archives, restart the J2EE Engine once.
2. Copy the build archives SAPJEE0x_0.SCA , SAPJTECHS0x_0.SCA and SAPBUILDT0x_0.SCA from the folder
\usr\sap\trans\EPS\in\ CMSP< hostname>
3. Start the CMS Web UI with user NWDI_ADM.
4. Select the Demo track in the Transport Studio.
5. Switch to the Check-In tab.
6. Click on the Value help button.
7. Select the following software components:
n sap.com SAP-JEE
n sap.com SAP_JTECHS
n sap.com SAP_BUILDT
8. Switch to the Development tab.
9. Select Select All and then Import.
10. Switch to the Consolidation tab.
11. Select Select All and then Import.
Preparing User Management for an External ABAP System
For a Java system, you can also deploy user management for an external ABAP system. In this case,
you configure the User Management Engine (UME) of the J2EE Engine for the user management of a
separate ABAP system.
Prerequisites
n The ABAP system is based on at least SAP Web AS ABAP release 6.20 SP25.
n In transaction PFCG, check that the roles SAP_BC_JSF_COMMUNICATION and SAP_BC_JSF_COMMUNICATION_RO
exist and make sure that their profiles are generated.
n In transaction PFCG, check that the roles SAP_J2EE_ADMIN, SAP_J2EE_GUEST and SAP_BC_FP_ICF exist.
Neither role contains any ABAP permissions, so you do not need to generate any profiles.
n In transaction PFCG, create a role named ADSCallers. You do not need to maintain authorization data or generate any profiles for that role.
Administration of the ABAP system
Perform the following administration steps in the ABAP system:
1. In transaction SU01 create a new communication user and assign it to the role SAP_BC_JSF_COMMUNICATION_RO.
2. In transaction SU01 create a new dialog user and assign it to role SAP_J2EE_ADMIN. This is your administrator user in the J2EE Engine.
3. In transaction SU01 create a new dialog user and assign it to role SAP_J2EE_GUEST. This is your guest user in the J2EE Engine.
4. In transaction SU01 create the following dialog users :
Users for Adobe Document Services (ADS) (optional):
l ADSUSER:
In transaction PFCG, assign the role ADSCallers to this user.
l ADS_AGENT:
In transaction PFCG, assign the role SAP_BC_FP_ICF to this user.
n SLD Data supplier user (optional):
You only have to create this user if you want to install SAP System Landscape Directory (SLD). The SLD data supplier user name that you enter later on during the Java system installation must be identical to this user.
SLD ABAP API user (optional):
You only have to create this user if you want to install SAP System Landscape Directory (SLD). The SLD ABAP API user name that you enter later on during the Java system installation must be identicalto this user.
Initial Technical Configuration for Application Server Java (AS Java)
Initial Technical Configuration for Adobe Document Services
SAPinst automatically performs initial technical configuration steps specific to Adobe Document Services (ADS) during the installation.
However, you have to perform some of these steps manually if:
n You upgraded your SAP system to NetWeaver 2004s SR1.
n You have installed AS Java on a separate host and want to use ADS for a standalone ABAP system.
n You want to change existing parameters or you want to set additional parameters.
Checking the IIOP Service
The startup mode of the service iiop must be set to always. To verify this, you have to check and if required modify special settings on the central instance host.
Procedure
1. Start the configuration tool of the J2EE engine:
Run \usr\sap\
The J2EE Engine ‒ Config Tool screen appears.
2. In the left frame, open the tree Cluster data® Global dispatcher configuration® Services.
3. Choose service iiop.
4. The field Startup mode in the right frame must be set to always.
5. Choose Apply changes.
6. Repeat the steps 2. ‒ 5. for the following path: Cluster data® Global server configuration® Services.
Checking Java Startup Properties
You have to check if the Java startup property for Adobe document services is set. To do so, you have to check and if required modify special settings on the central instance host.
Procedure
1. Start the configuration tool of the J2EE engine:
Run \usr\sap\
The J2EE Engine ‒ Config Tool screen appears.
2. Select cluster data® instance_
3. In the right frame, check if the following line exists in the section Java Parameters of the tab
General:
-Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.
services.ts.jts.ots.PortableInterceptor.JTSInitializer
If it is not true, add the line to this section.
Creating a User for Basic Authentication
To ensure secure access, you must create a user and assign the security role ADSCaller to this user
. The ADSCaller security role was created during the SAP system installation.
1. Log on to the Visual Administrator of the J2EE Engine.
a) On your central instance host, change to the admin directory:
(path: \usr\sap\
b) Double-click go.bat.
2. On the Cluster tab, choose Server
3. On the User Management tab, choose Create Group to create a group called ADSCallers, if the group does not exist. In the dialog box that follows, enter the name and choose OK.
4. Choose Create User.
The Create New User dialog box is displayed.
5. In the User name, Password, and Confirm password boxes, enter ADSUser for the user name and enter a password.
6. Choose the Tree tab in the right panel. In the User Tree, select ADSCallers, and then choose OK.
7. Choose the Tree tab in the left panel. Select ADSCallers® ADSUser.
8. In the Authentication area, select No password change required.
9. On the Policy Configurations tab, in the Components area, select
com.adobe/AdobeDocumentServices*AdobeDocumentServicesAssembly.jar.
10. On the Security Roles tab, select ADSCaller from the Security Roles list.
11. In the Mappings area, choose Add, which is assigned to Users.
The dialog Choose Users or Groups is displayed.
12. Choose the Tree tab.
13. In the User Tree, under the ADSCallers group, select the ADSUser that you just created and choose OK.
This assigns the new user to the ADSCaller security role.
Creating a User in AS ABAP
1. Log on to the SAP system with an admin user, in the client that is used for the UME authentication.
2. Choose Tools® Administration® User Maintenance® User (transaction SU01).
3. Enter ADSUser as user name and choose Create.
4. Choose system user as type for ADSUser.
5. Choose Tools® Administration® User Maintenance® Role Administration® Roles (transaction PFCG).
6. Create a role ADSCallers (no authorizations required).
7. Activate the role.
8. Assign the user ADSUser to this role.
9. Log on to the Visual Administrator of the J2EE Engine.
a) On your central instance host, change to the admin directory:
(path: /usr/sap/
(path: \usr\sap\
b) Run go.sh.
c) Double-click go.bat.
10. On the Cluster tab, choose Server
11. On the User Management tab, choose the Tree tab in the left panel.
12. In the User Tree, ensure that the user you created in ABAP appears under the ADSCallers group.
13. On the Policy Configurations tab, in the Components area, select
com.adobe/AdobeDocumentServices*AdobeDocumentServicesAssembly.jar.
14. On the Security Roles tab, select ADSCAller from the Security Roles list.
15. In the Mappings area, choose Add, which is assigned to Users.
The dialog Choose Users or Groups is displayed.
16. Choose the Tree tab.
17. In the User Tree, under the ADSCallers group, select the ADSUser you just created and choose OK.
This assigns the new user to the ADSCaller security role.
Creating a Service User in the ABAP Environment
You need to create the service user ADS_AGENT for processing forms between an ABAP and a Java
environment.
Procedure
1. Log on to the ABAP client specified in the profile parameter login/system_client.
2. Choose transaction SU01 (User Management).
3. Enter the name ADS_AGENT in the User field and choose User® Create.
4. Choose the Logon data tab and assign a password.
5. Choose Service as the user type for ADS_AGENT.
6. Choose the Role tab and assign the role SAP_BC_FP_ICF to the user ADS_AGENT.
Creating a Web Service Destination
Here you find information how to create a Web Service Destination.
Procedure
1. Log on to the Visual Administrator of the J2EE engine:
a) On your central instance host, change to the admin directory:
(path: \usr\sap\
b) Double-click go.bat.
2. On the Cluster tab, choose Server
3. Choose Web Service Clients ® sap.com > tc~wd~pdfobject ®
com.sap.tc.webdynpro.adsproxy.AdsProxy*ConfigPort_Document.
4. From the Authentication list, select BASIC.
5. In the User and Password boxes, enter as user name ADSUser and a password.
6. Choose Save.
7. Activate the authentication data as follows: Navigate to Services® Deploy.
8. Choose the button Application.
9. Choose sap.com/tc~wd~pdfobject in the tree.
10. Choose Stop Application.
11. For restarting the application, choose Start Application.
Creating a HTTP Destination
You have to create a HTTP destination to the back-end where the Adobe document services are installed.
Procedure
1. Start the Visual Administrator of the J2EE Engine.
a) On your central instance host, change to the admin directory:
(path: \usr\sap\
b) Double-click go.bat.
2. On the Cluster tab, choose Server
displayed in the right pane.
3. Choose New in the navigation panel.
4. In the dialog box that follows, enter the name FP_ICF_DATA_
5. As the target URL, enter the message server (or Web Dispatcher) of the SAP NetWeaver AS ABAP in
the URL field:
http://
and in case of SSL:
https://
6. Select the authentication method to use for the connection, and enter the parameters for the authentication method in the corresponding fields (if applicable).
n In the Username field, enter ADS_AGENT (must exist as service user in usage type AS ABAP).
n In the Password field, enter the same password as given for the AS ABAP service user ADS_AGENT.
7. If the connection is to use HTTPS, specify how the connection should handle SSL server authentication.
8. Save your settings.
Creating the ADS Connection in ABAP
You use this procedure to create a connection in the ABAP environment to use when connecting to Adobe document services.
Procedure
1. Log on to the central instance host.
2. Call transaction SM59.
3. Choose Create.
4. Enter at least the following:
n RFC destination: ADS
n Connection type: G
n Description:
5. Choose ENTER .
6. Choose the Technical settings tab and enter at least the following:
n Target host:
Enter the host name where you J2EE engine is located or the host name of the Windows dialog instance.
n Service No.:
l Enter the J2EE HTTP port number.
The following naming convention applies:
5
l Or enter the port number of the Windows dialog instance.
n Path prefix:
Enter exactly the string /AdobeDocumentServices/Config?style=rpc or, if you want to set up SSL,
/AdobeDocumentServicesSec/Config?style=rpc
7. Choose the Logon/Security tab and configure the security account to your security requirements.
8. Save your settings.
9. Choose Test Connection.
A screen is displayed. The field status_reason: OK indicates that the test was successful.
Activating the ICF Service FP
The communication between the Destination Service of the SAP NetWeaver AS Java and AS ABAP uses the
Internet Communication Framework (ICF). You have to activate the corresponding service.
Procedure
1. Choose transaction SICF.
2. Choose default_host® sap® bc® fp in the tree.
3. Choose Service/Virt.Host® Activate.
The ICF service is now active.
Initial Technical Configuration for Composite Application Framework Core
SAPinst automatically performs initial technical configuration steps specific to the Composite Application Framework Core (CAF) during the installation.
n However, you have to perform some of these steps manually if:
You upgraded your SAP system to NetWeaver 2004s SR1
n You want to change existing parameters or you want to set additional parameters.
The following steps might be affected:
n Create roles CAFAdmin and CAFUIAdmin
n Set configuration parameters
Configuring the Connection for System Landscape Directory
SAPinst automatically configures the connection for System Landscape Directory according to the parameters
you entered on the related SAPinst screens during the input phase.
This section provides information on how to configure your SAP system for System Landscape Directory (SLD).
You can now configure your SAP System for SLD as follows:
n As an SLD server (and client)
n As an SLD client
Initial Technical Configuration for Enterprise Portal (EP)
SAPinst automatically performs EP-specific initial technical configuration steps during the installation.
However, you might have to perform some of these steps manually if:
n You upgraded your SAP system to NetWeaver 2004s SR1.
n You have installed usage type EP as an additional usage type to an existing SAP system as described in SAP Note 883948.
The following steps might be affected:
n Copying CMS_MAPPING Properties
n Renaming InitialPermissions.xml.template
n Renaming initialPermissionsKMC.xml.template
Copying CMS_MAPPING Properties
Copy file cms_mapping.properties from source directory
servlet_jsp\irj\root\WEB-INF\portal\system\pcd\Migration\mapping\
to target directory
Renaming InitialPermissions.xml.template
1. Go to directory
servlet_jsp\irj\root\WEB-INF\portal\system\xml\acl
2. Rename file initialPermissions.xml.template to initialPermissions.xml.
Renaming initialPermissionsKMC.xml.template
1. Go to directory
servlet_jsp\irj\root\WEB-INF\portal\system\xml\acl
2. Rename file initialPermissionsKMC.xml.template to initialPermissionsKMC.xml.
Initial Technical Configuration for Process Integration (PI)
SAPinst automatically performs PI-specific initial technical configuration steps during the
installation.
However, you might have to perform some of these steps manually if:
n You upgraded your SAP system to NetWeaver 2004s SR1.
n You have installed usage type PI as an additional usage type to an existing SAP system as
described in SAP Note 883948.
Importing the SAP Exchange Profile
.
Note
If SAPinst has finished successfully, the exchange_profile.xml file does not exist on your system.
In this case, you can skip this step.
Procedure
1. On your PI server host, open the following URL:
http://
The following naming convention applies for
5
50000, for example, if your J2EE instance is 00
2. Enter the logon information:
User Name: PISUPER
Password:
The Exchange Profile page appears
3. Choose Connection.
The Server Settings page appears.
4. Enter the required information for the PI host.
Use the logon information of user PILDUSER.
5. Choose Save.
The Exchange Profile page appears.
6. Choose Import.
The Import Profile page appears.
7. Choose Browse and select the following file:
/usr/sap/
8. Choose Import Data.
The profile will be imported.
Assigning SAP_ALL Rights to User PISUPER
1. Log on to your SAP NetWeaver AS ABAP host as user with SAP_ALL rights (use DDIC or SAP*).
2. Call transaction SU01.
3. Select user PISUPER.
4. Navigate to the Profiles tab and switch to edit mode.
5. In the row Profile, add SAP_ALL.
6. Save your settings.
Activating the ICF Services
The Internet Communication Framework (ICF) is a HTTP framework that provides an ABAP interface for
HTTP requests. Via ICF services, the SAP Web Application Server can use the HTTP protocol for remote
communication as client and as server.
Assigning Roles to Groups
To assign the roles to the different groups, start the Visual Administrator of the J2EE Engine.
Assigning Role "Administrator" to Group SAP_XI_ADMINISTRATOR
1. Choose Cluster® Server® Services® Security Provider®
sap.com.\com.sap.rprof.remoteprofileexchangeprofile.
2. Select Security Roles.
3. Select Administer.
4. Select the group SAP_XI_ADMINISTRATOR.
5. Choose Add and assign the role administrator.
6. Save your settings.
Assigning Security Role "LcrAdministrator" to Group SAP_SLD_ADMINISTRATOR
1. Choose Cluster® Server® Services® Security Provider.
2. On the Runtime tab in the right frame, choose Policy Configuration® Component.
3. Select sap.com/com.sap.lcr*sld.
4. On the right, choose Security Roles and select the role LcrAdministrator.
5. Select the role type Security Role.
6. In the lower frame, add group SAP_SLD_ADMINISTRATOR.
Initial Technical Configuration for Business Information Java(BI Java)
SAPinst automatically performs BI Java-specific initial technical configuration steps during the
installation.
However, you might have to perform some of these steps manually if:
n You upgraded your SAP system to NetWeaver 2004s SR1.
n You have installed usage type BI Java as an additional usage type to an existing SAP system as
described in
SAP Note 883948.
Configuring BI Java Information Broadcasting
For the configuration of the BI Information Broadcasting you need to carry out the following steps
in your
ABAP system:
1. Call transaction SPRO and carry out the following steps:
a) Settings for Information Broadcasting:
Go to SAP NetWeaver® Business Intelligence® Reporting-relevant Settings® Settings for Information
Broadcasting
b) Destinations for Web Dynpro ALV:
Go to SAP NetWeaver®Application Server®Web Dynpro for ABAP®Set-Up Printing for Web Dynpro ABAP ALV
n Create RFC destination in the SAP NetWeaver Portal
n Create RFC destination to the SAP NetWeaver Portal
n Set-Up Web Service destination for the Adobe Document Services
2. Installation of BI Content:
Call transaction RSTCO_ADMIN to check whether the installation has been carried out successfully. If
the installation status is red, restart the installation by calling transaction RSTCO_ADMIN again.
Check the installation log if you need further assistance or information.
For more information, see SAP Note 834280.
Process Chains: Transporting Texts for the Alert Category
Alerts can be triggered and sent for BI process chains that contain errors. Defining the alert
categories
is necessary for this purpose. Alert category BWAC_PROCESS_CHAIN_FRAMEWORK is returned for errors in
background processing of process chains. This category has set texts that are not transported when
the alert category is transported.
Renaming initialPermissionsBI.xml.template
If SAPinst does not rename the initialPermissionsBI.xml.template file automatically, you will need
to rename it yourself.
Procedure
1. Go to directory
servlet_jsp\irj\root\WEB-INF\portal\system\xml\acl
2. Rename file initialPermissionsBI.xml.template to initialPermissionsBI.xml.
Performing the Client Copy
If you install a new ABAP or ABAP+Java system, in most cases you do not need to perform the client
copy for
the ABAP stack. SAPinst creates three ABAP clients during the installation, client 000, client 001,
and client 066.
You can use client 001 for production.
The following procedure describes how to perform a client copy manually. We recommend that you use
client 001 as source client, however you can also use client 000 as source client.
Procedure
1. Maintain the new client with transaction SCC4.
2. Activate kernel user SAP*:
a) Set the profile parameter login/no_automatic_user_sapstar to 0.
b) Restart the application server.
3. Log on to the new client with kernel user SAP* and password PASS.
4. Copy client 000 with transaction SCCL and profile SAP_CUST.
5. Check the log files with transaction SCC3.
6. Deactivate kernel user SAP*:
a) Reset login/no_automatic_user_sapstar to 1.
b) Restart the application server.
No comments:
Post a Comment