在 SAP J2EE 引擎上与 BW 组件通讯时出错的解决方案
在SAP J2EE 引擎上与BW 组件通讯时出错
在SAP J2EE 引擎上与BW 组件通讯时出错
RSBOLAP 017 JA V A communication通讯错误，门户通讯时出现未知错误
RSBOLAP 017 JAVA communication error:an unknown error occured during portal communication
Diagnosis
An error has occurred during communication with the BW components on SAP J2EE Engine.
System Response
Procedure
Contact your system administrator for detailed error analysis.
Procedure for System Administration
SAP Note 888687 provides detailed instructions on analyzing communication and logon problems.
Summary
Symptom
This note describes how to analyze logon problems and communication problems in the area of BEx Web Java. It illustrates ways of analyzing the most common errors and also describes the information that SAP Support require to process messages in this area efficiently.
Other terms
BEx Web, Web Application, broadcasting, RFC, HTTP, HTTPS, ABAP, Java, Single Sign-On, SSO
Reason and Prerequisites
You configure information broadcasting in a system landscape with SAP NetWeaver 2004 or a higher version. or
You configure the "Enterprise Reporting, Query, and Analysis" IT scenario and, in particular, the "Query, Reporting and Analysis" scenario variant in a system landscape with SAP NetWeaver 2004s or a higher version.
When you test the configuration or when you execute an application, problems occur in the communication between the SAP Web Application Server Java and the SAP Web Application Server ABAP.
Solution
Classifying the problem
Information broadcasting and Java-based BEx Web Applications communicate differently between Java and ABAP. In the following section, the possible problems are divided into categories. Determine which category your question belongs to, read the information under "General procedure... " (depending on the communication protocol) and then read the section that deals specifically with your problem.
Note that there are two different protocols:
?RFC communication: RFC communication is always used when the SAP Web Application Server JAVA and the SAP Web Application Server ABAP communicate "in the background", which means
that they communicate with each other on the server. For instance, when query results are read to
display them in a Java-based BEx Web Application or when precalculated HTML pages are
generated in a batch job and the pages are then distributed to a Knowledge Management folder using information broadcasting.
?HTTP(S) communication: This type of communication uses the Web browser as an interim step. For example, it is used when the BEx broadcaster (which is an ABAP-based BEx Web Application) is
called from a Java-based BEx Web Application. It is also used in the BEx broadcaster when the
dialog box for selecting the folder is called to export the data into the portal, and this has been
implemented as a Java iView. Technically, the two actions specified here are executed when a URL is started on the client side.
It is important to bear the direction of the communication in mind:
?Java to ABAP communication: The initiator of the action is on the Java side and the data recipient is on the ABAP side.
?ABAP to Java communication: The initiator of the action is on the ABAP side and the data recipient is on the Java side.
Finally, there are the following two problem areas:
?An error may occur when setting up the communication: This happens if a technical connection between the two systems cannot be established.
?There may be an authentication (logon) error: The technical connection exists, but there is a problem identifying the user in the recipient that corresponds with the user in the initiator. Since both Java and
ABAP work only with authenticated users and not service users, it is absolutely necessary that the
user logs on to the calling system correctly so that the overall scenario can function correctly.
Note that logon tickets are used in the area of information broadcasting and Java-based BEx Web Applications. In these scenarios, the user does not need to log on to the Web browser or the SAP GUI twice. A double logon indicates that there is an error in the configuration. There are some exceptions to this rule, which render another logon necessary:
o When you call a BEx Web Application or the Broadcaster from a BEx tool, such as the BEx Web Application Designer.
o When you use a specific export format that references contents (for instance, MIME objects) from the SAP Web Application Server or other servers.
We shall now present information about more exact ways of analyzing the problems for each combination of the three subject areas that are mentioned above.
General procedure when using RFC as a communication protocol
If problems occur when you use RFC as a communication protocol, in the SAP J2EE Visual Administrator, use the following menu path
?"
to change the following locations to the "ALL" severity to receive more exact information: ?com.sap.ip.bi.webapplications
?com.sap.portal.connectors.BW
?com.sap.portal.ivs.semantic.systemLandscape
?com.sap.portal.ivs.systemConnectionTests
?com.sap.security.api.saml
?com.sap.security.core.server.jaas
?com.sap.security.core.server.saml
?com.sap.security.core.session
?com.sap.security.core.ticket
?com.sap.security.core.umap
?com.sap.security.core.util
Save the changes and distribute them to all server nodes. Do not forget to reset the values to their default values as soon as you have found the reason for the error. You do this to avoid unnecessary entries in the log and to prevent a negative impact on system performance.
After resetting the trace settings, carry out the action that caused the error again.
For more information about the cause of the error in an RFC communication, see the last entries in the
dev_jrfc.trc file in the following directory
?/usr/sap/
All RFC errors are logged in this file regardless of the direction of the communication. In most cases, this allows you to narrow down the cause of the error. You can also find the log entries for the individual components concerned in the following file
?/usr/sap/
You can view these in the "Log Viewer" in SAP J2EE Visual Administrator. The newest entries are displayed at the top in the "Log Viewer", which differs from the dev_jrfc.trc file.
Note that for a cluster installation, extra files are created for each server node. Since you cannot determine which server node is processing the RFC request, you may have to go through all these files.
Necessary information for SAP support when you open an OSS message and when you use RFC as a communication protocol
Ensure that you provide the following information in a message. By providing all the information, you can speed up the message processing because there is no need for further clarifications:
1. SAP support also requires the dev_jrfc.trc and defaultTrace.trc files for troubleshooting. Proceed as described under "General procedure when using RFC as a communication protocol"
If you create an OSS message, attach these files to the message in the case of RFC communication problems. Ensure that you copy the files directly from the respective server and avoid making any format conversions.
If your system is a cluster installation, attach the files of all cluster nodes to the message. This is necessary because there is no way of determining which server node is processing the RFC request.
2. Also, attach the ABAP certificate to the message as an attachment. You can export this into a file by saving the corresponding certificate by selecting "Export" in SAP J2EE Visual Administrator in "View" "TicketKeystore"
under "
3. Create screenshots of the login module settings and attach these to the message. The settings are under "
"com.sap.security.core.server.jaas.EvaluateTicketLoginModule" in the list of the "login modules' and choose "Modify". Change the window size and the column sequence in such a way that all entries that exist there are visible, and then create the screenshot. In the same way, proceed under "evaluate_assertion_ticket" with the "com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule" login module.
4. SAP support also requires an ABAP user name, for which there is a counterpart in J2EE, and the passwords of both users.
5. Finally, name the RFC destination that is used for the communication.
Communication errors in RFC-based Java to ABAP communication
To determine the correct SAP NetWeaver BI ABAP system, the system tries to determine the correct logon parameters for an RFC logon using the alias in the portal system landscape. If this is successful, the system transfers the parameters to the JRFC interface and this interface is responsible for the actual communication.
Typical problems and their characteristic error messages are as follows:
?The user does not have any read authorization for the system alias in the portal system landscape.
o Error message: "No permission for system alias ..." in the defaultTrace.trc log file.
o Solution: In portal system landscape maintenance, under "Authorizations", select the "User"
checkbox for the "Everyone" user group, for another role or another user group to which the
user is assigned, or select it for a list of single users.
? A parameter is missing from the system parameters and this parameter is necessary for setting up the connection.
o Error message: "'...' is missing" in the dev_jrfc.trc log file
o Solution: In the portal system landscape maintenance, check the parameters that were entered in the "Connector" category for your SAP NetWeaver BI ABAP system. The system
needs the parameter specified in the error message for the connection setup, but this has
not been entered.
? A system parameter is not specified correctly causing the connection setup to fail.
o Error message: "hostname '...' unknown", "service '...' unknown" or an error message in the dev_jrfc.trc log file
o Solution: Correct the incorrect parameter in the "Connector" settings in the System
Landscape Editor in the portal.
Communication errors in RFC-based ABAP to Java communication
In ABAP to Java communication, the SAP J2EE Engine works as an RFC server. When you start up the J2EE Engine the "JCo RFC Provider" registers itself under a unique name on the RFC gateway. After this registration, you can perform an RFC call from ABAP. This call is addressed to the RFC gateway, which forwards it to the "JCo RFC Provider" of the SAP J2EE Engine.
Typical problems and their characteristic error messages are as follows:
? A system parameter is not specified correctly causing the connection setup to fail.
o Error message: "hostname '...' unknown", "service '...' unknown" or an error message in the dev_jrfc.trc log file
o Solution: Correct the incorrect parameter in the settings of the RFC Bundle in the J2EE Visual Administrator in "
Authentication errors in RFC-based Java to ABAP communication
After the successful physical connection, the SAP Web Application Server ABAP tries to log the user on using the information available. In the areas of information broadcasting and the "Enterprise Reporting, Query, and Analysis" IT scenario, the system usually uses logon tickets to log the user on.
Typical problems and their characteristic error messages are as follows:
?The SAP Web Application Server ABAP does not accept the logon ticket created by the SAP Web Application Server Java because it does not recognize the certificate with which the ticket was
created.
o Error message: "The issuer of the SSO ticket could not be checked" in the dev_jrfc.trc log file
o Solution: In Transaction STRUSTSSO2 in the SAP Web Application Server ABAP, check whether the certificate of the SAP Web Application Server Java appears under "Certificate
list" and under "Logon ticket". The client in "Logon Ticket" should usually be specified as
"000". An empty value here is not valid. Also check in the tree view on the right-hand side of
the screen to see if a green traffic light is displayed for all application servers in "System
PSE". If this is not the case, the information on the respective application servers is obsolete.
In this case, select "Distribute" from the context menu for "System PSE" until all application
servers display a green traffic light.
?There is no ABAP user assigned for the calling J2EE user. This error only occurs if the user ID for the J2EE user and the ABAP user are not the same.
o Error message: "Name or password is not correct (repeat the logon)" in the dev_jrfc.trc log file
o Solution: Check if a user assignment (user mapping) exists for the user for the SAP User Management Engine (UME) master system. Here, it is important that mapping in the UME
master system is always used to determine the ABAP user name. This is also the case
when you want to open a connection to a system that is not a UME master system.
?The SAP Web Application Server ABAP is not maintained as a UME reference system and therefore, SSO tickets are not issued correctly.
o Error message: " message: 'password' missing" in the dev_jrfc.trc log file"
o Solution: Enter the SAP Web Application Server ABAP as a UME reference system and start the SAP Web Application Server Java so that the settings are transferred.
?The logon method is not set to "SAPLOGONTICKET" in the system in the system landscape maintenance portal, which is assigned to the SAP Web Application Server ABAP.
o Error message: "message: 'user' missing" in the dev_jrfc.trc log file"
o Solution: Set the "Logon Method" parameter to "SAPLOGONTICKET" in the SAP Web Application Server ABAP in the system landscape maintenance portal.
?The times of the system clocks between the SAP Web Application Server JAVA and the SAP Web Application Server ABAP do not correspond. As a result, the SAP logon ticket issued by the SAP Web Application Server JAVA is not yet valid or is no longer valid.
o Solution: Synchronize the two system clocks so that the system can determine the validity of the SAP logon ticket correctly.
If the errors specified above do not apply or do not help solve the problem, you can determine the exact error by following the steps in Note 495911 describing how to record a logon trace.
Authentication errors in RFC-based ABAP to Java communication
JAAS login modules run for the authentication of a user on the J2EE side. Login module
"com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule" is used in this case for the
RFC-based ABAP to Java communication. See "Component", "evaluate_assertion_ticket" for this login module. This login module only accepts logon tickets from systems that have a certificate that is known by the J2EE Engine and that were also specified in the configuration of the login module. If the J2EE user ID is different to the ABAP user ID, an "inverse" user mapping is used to determine the J2EE user ID. For this, the user mapping
is interpreted "backwards" for the UME master system.
Typical problems and their characteristic error messages are as follows:
?The login module does not accept any RFC logons from the calling ABAP system.
o Error message: ABAP short dump "Incoming call is not authorized."
o Solution: Check the correct configuration of the login module in accordance with Note 721815. That notes describes the procedure for EvaluateTicketLoginModule. In the case of
an RFC logon, you must configure the EvaluateAssertionTicket login module instead of the
login module under "evaluate_assertion_ticket".
You can determine "issuer distinguished name" and "subject distinguished name" for the note mentioned above by selecting the certificate of your BW back-end system under "
Check the correct configuration of the login module as described in Note 721815. The defaultTrace.trc log file contains information about the reason why the logon attempt was unsuccessful.
?The "inverse" user assignment (user mapping) is not unique.
o Error message: com.sap.security.api.umap.MultipleHitException: Too much hits found
o Solution: For a specified ABAP user, the system found more than one Java user for which a user assignment for that ABAP user is maintained. However, this "inverse" user assignment
must be unique for the ABAP to JAVA communication because otherwise, the UME system
cannot determine which JAVA user must be logged on. Determine which Java users are
mapped to the ABAP user and delete all user assignments except for one.
?The times of the system clocks between the SAP Web Application Server ABAP and the SAP Web Application Server JAVA do not correspond. As a result, the SAP logon ticket issued by the SAP Web Application Server JAVA is not yet valid or is no longer valid.
o Error message: Ticket is not yet valid... / Ticket is not valid until ...
o Solution: Synchronize the two system clocks so that the system can determine the validity of the SAP logon ticket correctly.
General procedure when using HTTP(S) as a communication protocol
When you use HTTP(S) as a communication protocol, it is important to know the name of the URL from which the incorrect page is called. You must also determine the URL that was called. To determine the two URLs, right-click the respective browser window and select "Properties" (MS Internet Explorer) or "This Frame" -> (if it
is available) "View Frame Info" or "View Page Info" (Firefox) from the browser context menu. The URL is displayed in a browser dialog. Choose this URL and select Ctrl+A to highlight it. Select Ctrl+ to copy the URL to the clipboard. Ensure that you copy the complete URL.
Necessary information for SAP support when you open an OSS message and when you use HTTP(S) as a communication protocol
Ensure that you provide the following information in a message. By providing all the information, you can speed up the message processing because there is no need for further clarifications:
1. If you are having problems using HTTP(S), specify the two URLs that are determined under "General procedure when using HTTP(S) as a communication protocol" in the OSS message.
2. SAP support also requires an ABAP user name, for which there is a counterpart in J2EE, and the passwords of both users.
Communication errors in HTTP(S)-based Java to ABAP communication
The URL is generated based on the information defined for the respective SAP Web Application Server ABAP in the System Landscape Editor portal in "SAP Web Application Server (WAS)".
Typical problems and their characteristic error messages are as follows:
?The parameters for the ABAP SAP Web Application Server are not maintained correctly.
o Error message: "The page cannot be displayed" or the return value 404 is displayed in the Web browser
o Solution: Check the parameters and correct them. The simplest way to obtain the correct values is to execute a test run in Transaction SE37 in the ABAP system for the
"RSBB_URL_PREFIX_GET" function module, in which you specify "HTTP" or "HTTPS" for
the "I_PROTOCOL" parameter depending on your configuration.
Communication errors in HTTP(S)-based ABAP to Java communication
The URL is generated based on the information defined in the SAP Web Application Server ABAP in the "RSPOR_T_PORTAL" view. You can use Transaction SM30 to display and modify this information, if required.
Typical problems and their characteristic error messages are as follows:
?The parameters for the J2EE system are not maintained correctly.
o Error message: "The page cannot be displayed" or the return value 404 is displayed in the Web browser
o Solution: Check the "URL Prefix for Portal" parameter and correct it. The parameter must contain the same protocol name, server name and port that you use to call the portal main
page, for instance.
Authentication errors in HTTP(S)-based Java to ABAP communication
The SAP Web Application Server ABAP in HTTP(S) only accepts queries that come from a system with a certificate that is known by the system.
The same problems may occur as those specified in the "RFC-based Java to ABAP communication" section. Although detailed error messages are not written to a log file, you should still carry out the steps described in "Solution".
You can also implement Note 495911 in this case.
Problems with the format of the URL may also prevent the exchange of cookies between ABAP and Java and as a result the behavior of Single Sign-On is incorrect. For more information about this, see Note 654982 and also Note 830830, which applies to BEx Web Applications.
Authentication errors in HTTP(S)-based ABAP to Java communication
JAAS login modules run for the authentication of a user on the J2EE side. The "EvaluateTicketLoginModule" login module is used for this for the HTTP(S)-based ABAP to Java communication. See "Component", "Ticket" for this login module. This login module only accepts logon tickets from systems that have a certificate that is known by the J2EE Engine and that were also specified in the configuration of the login module. If the J2EE user ID is different to the ABAP user ID, an "inverse" user mapping is used to determine the J2EE user ID. For this, the user mapping is interpreted "backwards" for the UME master system.
Typical problems and their characteristic error messages are as follows:
The login module does not accept any HTTP(S) logons from the calling SAP Web Application Server ABAP.
o Error: The end user is asked for logon data again (Basic Authentication dialog box)
o Solution: Check the correct configuration of the login module as described in Note 721815.
The defaultTrace.trc log file contains information about the reason why the logon attempt
was unsuccessful.
Problems with the format of the URL may also prevent the exchange of cookies between ABAP and Java and as a result the behavior of Single Sign-On is incorrect. For more information about this, see Note 654982 and also Note 830830, which applies to BEx Web Applications.
Additional Information
For further information, see the following sources.
For communication errors:
?SAP NetWeaver Problem Analysis Guide "JCo Exceptions":
https://www.wendangku.net/doc/de14568081.html,/saphelp_erp2005/helpdata/en/6c/7ffb3f6c78ee28e10000000a1550b0/frameset.h tm
For authentication errors:
?SAP Online Help "Administration When Using Logon Tickets":
https://www.wendangku.net/doc/de14568081.html,/saphelp_erp2005/helpdata/en/e3/e86878c8204acc856d8d5da4a54fa4/frameset.
htm
?How-to Guide "How to Configure Single Sign-On in a Complex System Landscape": https://https://www.wendangku.net/doc/de14568081.html,/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/security/How%20to %20Configure%20SSO%20in%20a%20Complex%20System%20Landscape.pdf
Symptom
You were asked by SAP support to use the "SAP NetWeaver BI Diagnostics & Support Desk Tool" to check the configuration of your system and to collect detailed information regarding your SAP NetWeaver BI installation.
This note describes the process of using this tool.
For general remarks regarding the importance of an all-green "SAP NetWeaver BI Diagnostics & Support Desk Tool", see note 1177154.
The tool will not show an all-green status in case you are using it in a high-availability environment, using SAP Web Dispatcher, the alternative RFC configuration in note 974818, or both. We are currently looking into this topic. In those cases, please make sure to point out this configuration to SAP support and reference this section of this note in your message. Also, make sure that the other traffic lights not related to these two areas are still green.
Other terms
supportdesk, configuration BI Java
Reason and Prerequisites
In order to process your message efficiently, SAP support requires a couple of settings which you can collect manually in various places, like
?SAP J2EE Visual Administrator (only NetWeaver 7.0x)
?Portal administration UIs
?NetWeaver Administrator UIs
and so on. "SAP NetWeaver BI Diagnostics & Support Desk Tool" automates the process of collecting this information.
Additionally, "SAP NetWeaver BI Diagnostics & Support Desk Tool" includes a complete set of all basic configuration checks required to configure BI-Java. Moreover, it provides hints for the sources of configuration issues and offers instructions to correct the configuration.
Solution
Be aware that the procedures differ deppending on the release (SAP NetWeaver 7.0x and SAP NetWeaver >= 7.30).
Usage of the tool (release independent)
In order to use the tool, follow these steps:
1. Close all open web browsers.
2. Logon to your Portal using
"Administrators" group. Usually, this is "Administrator" or "j2ee_admin" or another user from either user group "GRUP.PRIVATE_DATASOURCE.un:Administrators" or
"GRUP.R3_ROLE_DS.SAP_J2EE_ADMIN".
3. Change the URL in your browser to
lt
4. In case a red traffic light is shown on the initial tool screen indicating a configuration issue, click the
link to get more details on the configuration issues found for your system. Go through the list of
checks marked with a red traffic light and see the instructions provided for each check in order to
correct the configuration.
5. In case of changes to the configuration, click the "Reload configuration" button to re-run the
configuration checks and update the check results.
6. If all traffic lights turn green and the issue is resolved you do not take any additional actions.,
?In NetWeaver 7.0x: In case you have deployed the tool as described below, continue with the steps described below for undeploying the tool.
7. If you can't correct the configuration on your own or all traffic lights are green and the issue persists,
continue with the next bullet point.
8. If you have a specific error situation which for example occurs during navigation step in a BEx Web
Application Java, click on the "Start reproducing error" button. If you have issues with the overall
configuration, go to the next step.
9. Click the "Download support info" button. When prompted, store the downloaded file
"supportdesk.zip" to your local harddisk.
10. If you have clicked the "Start reproducing error" before, it is important to click the "Stop
reproducing error" button now. This will restore all log levels to their original values and helps to
prevent performance degradation due to too many messages written to the log files.
11. Attach the file "supportdesk.zip" to your OSS message or send the file via e-mail to
bw.bex.support@https://www.wendangku.net/doc/de14568081.html, stating the OSS message number and title in the e-mail title. Additional release dependent information for SAP NetWeaver 7.30
Currently there is no additional deployment option for this release.
Known Issues:
o Check for deployed components fails when Support Packages of ABAP and Java are not equals. This is incorrect. You are allowed to deploy the BI Java patches according to the
note 1506722.
Additional release dependent information for SAP NetWeaver 7.0x (7.0 and Enhancement Packages)
Support Desk Tool is delivered in SAP standard delivery of Usage type BI Java. You can execute the tool on every server which includes BI Java. Deploy new version only when requested by support organisation or when the delivered version is older than the version attached to this note.
Deployment Procedure (only for NetWeaver 7.0x)
The latest available version for the Support Desk Tool is 0.426.
In case you are asked by SAP Support to use "SAP NetWeaver BI Diagnostics & Support Desk Tool" and you have already deployed a version to your SAP Web Application Server Java, please check your version and the attached version. In case the attached version is newer, deploy the latest version attached to this note again because the tool is frequently updated to cover the most prominent issues reported via OSS. Also, always import the latest version of correction instruction attached to this note into the SAP Web Application Server ABAP part of your SAP NetWeaver BI system.
In order to deploy the newer version of the tool, follow these steps:
1. Import the correction instruction attached to this note into your SAP NetWeaver BI system.
2. Open the file "tool.zip" attached to this note and extract the file "com.sap.ip.bi.supportdesk.par" to
your local harddisk. Please leave the file name all lowercase.
3. Close all open web browsers.
4. Logon to your Portal using
https://www.wendangku.net/doc/de14568081.html,:50000/irj) with a user belonging to the "Administrators" group. Usually,
this is "Administrator" or "j2ee_admin" or another user from either user group
"GRUP.PRIVATE_DATASOURCE.un:Administrators" or "GRUP.R3_ROLE_DS.SAP_J2EE_ADMIN".
Make sure that this user has authorizations for function group SYST in the SAP Web
Application Server ABAP part of your SAP NetWeaver BI system. After using the tool, you can
remove the authorization again. It is only required for the tool itself.
5. Change the URL in your browser to <
http|https> ://
onsole.default
6. Click the "Browse..." button and select the file "com.sap.ip.bi.supportdesk.par" from your local
harddisk. Press "Open".
7. Click the "Upload" button to deploy the tool to your SAP NetWeaver Web Application Server Java.
8. Be aware that this attached version has a higher technical number and it can be not overwritten by
applying new Patch or Support Package. You will need to undeploy this tool:
?Close all open web browsers.
?Logon to your Portal using
?Change the URL in your browser to <
http|https> ://
onsole.default
?In the "Archive Remover" section, select the entry "com.sap.ip.bi.supportdesk".
?Press the "Clean" button.
Symptom
This note describes how to setup BEx Web in SAP NetWeaver 2004s. All required steps are mentioned. Additionally, this note contains a checklist to check the installation and configuration.
Other terms
Business Explorer, RSPOR_SETUP, BEx Web, Runtime, J2EE, Web Application, BEx Information Broadcasting, RFC, HTTP, HTTPS, ABAP, Java, Single Sign-On, SSO
Reason and Prerequisites
You configure BEx Web and BEx Information Broadcasting in a system landscape with SAP NetWeaver 2004s.
Solution
Overview
?Other References
o Frequently Asked Questions (FAQ)
o SDN Forum
o Learning Map for Consultants
?Definition of Terminology
o Usage Types
?Architecture
?Installation (*)
o Types of Installation
?Configuration Overview(*)
?Configuration Tools (*)
o Template Installer
o Report RSPOR_SETUP
?Configuration Checks (*)
?SAP Support Messages (*)
?Additional Information
Topics marked with (*) should be read by everyone who installs, upgrades and configures a SAP NetWeaver 2004s system with Usage Type BI-Java.
This note will be frequently updated.
Other References
?Documentation
You can find a detailed description of all required steps in the BI system under transaction SPRO / SAP Reference IMG / SAP Customizing Implementation Guide / SAP NetWeaver / Business Intelligence / Reporting-relevant Settings / Web-Based Settings / Integration into the Portal.
?Frequently Asked Questions (FAQ)
You can access a list of frequently asked questions for BI under https://www.wendangku.net/doc/de14568081.html, / Home / Developer Areas / SAP NetWeaver / Business Intelligence and than Quick Links / SAP BI FAQs
(https://https://www.wendangku.net/doc/de14568081.html,/irj/sdn/docs?rid=/webcontent/uuid/feb70f5d-0701-0010-68a1-f7d46f2cf274). This list is frequently updated.
?SDN Forum
There is a SDN Forum available during Ramp-Up of SAP NetWeaver 2004s under https://www.wendangku.net/doc/de14568081.html, / Forums / SAP Business Intelligence / SAP NetWeaver 2004s Ramp-Up
(https://https://www.wendangku.net/doc/de14568081.html,/thread.jspa?forumID=154). You use this forum to place your question and discuss with experts.
Definition of Terminology
SAP introduced new terms with SAP NetWeaver 2004 like IT practices, IT scenarios and Usage Types. Usage types are a new structuring element for SAP software on a technical level.
For more information, see SAP Service Marketplace at https://www.wendangku.net/doc/de14568081.html,/instguidesNW2004s
Usage Types
?AS-ABAP
o Contains all ABAP-based SAP WebAS functionality (software components SAP_ABA, SAP_BASIS and SAP_BW)
Data Warehouse Management, OLAP processor, Existing SAP BW 3.5 Web Runtime, ...
o Internet Graphics Service (IGS) comprised
?AS-Java
o Contains all Java-based SAP WebAS functionality (J2EE)
o Adobe Document Services (ADS), Universal Data Integration (UDI) and Metadata Model Repository (MMR) comprised
o Universal Data Integration (UDI) is an independent component that is used for data retrieval and does not require Usage Type BI-Java
o See note 853572 for additional information about AS-Java
?EP
o Contains Portal
o Requires Usage Type AS-Java
?BI
o Contains BI Content Add-On (software component BI_CONT)
o Requires Usage Type AS-ABAP
?BI-Java
o Contains all Java- and WebDynpro-based BI functionality
New NW2004s Web Runtime (incl. Analysis Item, Formatted Reporting, Web Printing, PDF Export, ...), new Planning Modeler for BI Integrated Planning, ...
o Requires Usage Type EP and AS-Java
o See Release Notes under https://www.wendangku.net/doc/de14568081.html,/saphelp_nw04s/helpdata/en/index.htm
?BI accelerator
o Standalone engine based on TREX
?Search and Classification
o Standalone engine based on TREX
BI accelerator and Search and Classification require two different TREX standalone engines Architecture
As described above, BEx Web in SAP NetWeaver 2004s (Usage Type BI-Java) requires Usage Types EP and AS-Java, i.e. a Portal on a Java stack is required. This Java stack could be installed on the same server or on another server (see Types of Installation for details).
BEx Web Runtime and BI Consumer Services (BICS) are implemented in Java and using Portal Runtime functionality. BEx Web Runtime is responsible to generate output for Web Browser and BICS retrieves data from BI Platform and/or UDI.
In SAP NetWeaver 2004s, load is moved from AS-ABAP (BI-ABAP) to AS-Java (BI-Java). BI generates load on Portal (AS-Java), therefore BI users generate more load on Portal than normal Enterprise Portal users. See note 927530 for additional information about BI-Java sizing.
Which functionalities of BEx Web in SAP NetWeaver 2004s are requiring a Portal?
?New BEx Web Application Designer (Unicode, Command Wizard, ...)
?Exporting to PDF and Printing
?Integrated Planning
?Drag&Drop (Analysis Web Item)
?Web Items (Container Layout, Menu Bar, Tab Pages, Button Group, ...)
?Formatted Reporting with BEx Report Designer
?Document Integration with storage in Knowledge Management
?...
For details, see Release Notes for Usage Type BI-Java under
https://www.wendangku.net/doc/de14568081.html,/saphelp_nw04s/helpdata/en/index.htm
If you don't want to use the new BEx Web functionality, you can still use BEx Web 3.5 Runtime that is running only with Usage Type AS-ABAP.
Installation
Types of Installation
As result of your installation or upgrade process, you can have the following system state:
?Application Server ABAP (AS-ABAP with own system ID and instance number)
?Application Server Java (AS-Java with own system ID and instance number)
?Double-Stack (ABAP and Java combined on one server with identical system ID and instance number)
In case of AS-ABAP and AS-Java the ABAP stack and Java stack are separated by system ID (SID) and instance number. But both stacks could be installed together on one server or separately on two different servers.Both stacks are like different systems.
In case of Double-Stack installation, the ABAP stack and Java stack are running as one system on one server.
The term Add-In installation describes an installation process - it is not a system state. The result of an Add-In installation is a Double-Stack system (AS-ABAP and AS-Java with on system ID). An Add-In installation allows to install a Java stack to an existing ABAP stack. An Add-In installation of an ABAP stack to an existing Java stack is not possible.
Important
In case of Add-In installation, the system ID (SID) of AS-ABAP and AS-Java is identical. This causes problems during import and certificates, if you are using the Template Installer. Please see topic Additional Information for details about these settings.
Important
In case of Add-In installation, the User Management (see Configuration) is automatically set to client 001. If you want to use another client, you have to adjust a few settings. Please see topic Additional Information for details about these settings.
See FAQ for details about possible system landscapes.
Types of Upgrade
?From SAP EP 6.0 (SAP NetWeaver 2004)
?From SAP BW 3.5 (SAP NetWeaver 2004)
?From SAP BW 3.x
Upgrade from SAP EP 6.0 (SAP NetWeaver 2004)
If you upgrade a SAP EP 6.0 Portal with existing System Objects to BW (now BI) systems in the Portal System Landscape, please ensure to maintain the new properties at the System Object (see Additional Information below for details).
See FAQ for details about possible system landscapes.
See https://www.wendangku.net/doc/de14568081.html,/instguidesnw2004s for general installation and upgrade information about SAP NetWeaver 2004s.
Configuration Overview
You can summarize the configuration in three main topics:
1. Communication
2. Single Sign-On (SSO)
3. User Management
You have to setup both directions for communication:
1. Java to ABAP communication
2. ABAP to Java communication
For communication, the RFC/JCo protocol and HTTP(S) web protocol are used. Communication is used to create and display BI content in the Portal. Communication is also be used to display Portal content in BI (e.g. BEx Information Broadcasting shows Knowledge Management folder). See note 888687 for technical details.
For Single Sign-On (SSO), you have to ensure that Java and ABAP trust each other:
1. Java is trusting ABAP
2. ABAP is trusting Java
Single Sign-On (SSO) is working with SAP Logon Tickets. SAP Logon Tickets are created with the help of certificates and could be validated with certificates. Therefore, certificates must be exchanged between Java and ABAP.
Certificates consist of a public key and optionally of a private key. The private key of certificate is required for creating and signing SAP Logon Tickets. The public key of certificate is used for validating SAP Logon Tickets. SAP Logon Tickets are digitally signed with the private key of the issuing system's certificate. They contain the user ID, authentication scheme, validity period, issuing system and digital signature but they do not contain any passwords. SAP Logon Tickets are validated with the public key of the issuing system's certificate (the public key is located in System PSE or TicketKeystore). They are only accepted if the issuing system is part of Single Sign-On Access Control List (ACL) or EvaluateTicketLoginModule in the validating system.
See note 888687 for additional technical details.
User Management could help you to minimize the effort of administrating your user accounts. Common user storage for ABAP and Java is recommended. Several options are available:
1. LDAP Directory (external)
2. ABAP System (as Central User Administration or single system)
3. Java System Database (J2EE, former Portal User Management Engine; double maintenance of
user required)
Option 2 is recommended. For Add-In installation, option 2 is automatically set up. See References for details. Configuration Tool
To configure BI-Java, you should use the Template Installer (template-based automatic configuration). In order to have the latest corrections for the Template Installer available, please use the latest patch of the SCA
LM-TOOLS for your Support Package Stack. The latest patch can be downloaded from SAP Service Marketplace.
How to use this Configuration Tool?
At first, use the Template Installer to perform the automatic configuration. In most cases, this
SAP BASIS_BW_STMS传输系统的配置和管理
传输系统的配置和管理 本章主要内容： 传输系统的配置 传输CHANGE REQUEST SAP的整个系统一般包括开发系统、测试系统、生产系统。所有的配置、开发都要求在开发系统完成，然后形成CHANGE REQUEST，再通过传输系统传入测试系统进行测试，最后传入生产系统。SAP的传输系统具有域的概念，所有的系统都要求处于同一个传输域中，并且有并只能有一个域控制器，用来控制对CHANGE REQUEST的传输，一般情况下传输系统的域控制器都选择为开发系统，并且把传输域控制器的/usr/sap/trans目录共享出来，保证测试、生产系统可以对/usr/sap/trans目录进行读写访问。 7.1 传输系统的配置 配置传输系统的步骤如下： 1 在开发、测试、生产系统上，设置传输路径的参数（修改参数文件的方法参见“十修改参数文件”）： RZ10--修改子系统参数文件--扩展管理，把参数“DIR_TRANS”设置为//SAPTRANSHOST/sapmnt/trans。其中SAPTRANSHOST为传输域控制器的主机名。 在WINDOWS系统上，如果开发、测试、生产系统不在一个域内，需要建立各个域的信任关系，确保所有系统实现对/usr/sap/trans的读写访问。 2 登陆传输域控制器（以下指定为开发系统）的CLIENT 000，运行STMS。
2 在没有配置传输系统时，系统将弹出窗口，要求配置传输系统。作为域控制器的开发系统，直接在弹出窗口点保存，默认开发系统为域控制器。 3 登陆测试或生产系统的CLIENT 000，运行事物代码STMS
4 系统要求配置传输，点保存右侧的“OTHER CONFIGURATION” 5 选择Include system in domain
面试的十大方面及举例
面试的十大方面及举例1．语言表达、仪表 2．工作经验 3．应聘动机与期望
4．事业心、进取心、自信心 5．工作态度、组织纪律性、诚实可靠性 6．分析判断能力 7．应变能力 8．自知力、自控力
9．组织协调能力、人力关系与适应能力 10．精力、活力与兴趣、爱好 11．专业知识水平及特长
具体举例 一．常见区域销售类问题 HR 美琳凯 1．每段离职原因 2．处理客户投诉的案例 3．销售业绩如何 4．对自己的职业规划 5．如何解释“销售支持“ 6．对“城市经理“职责的理解 美赞臣 1.合同怎么谈 2.活动执行怎么谈 3.作为客户经历应具备什么素质 4.考核标准 5.卖场货款收回是怎么操作的 欧莱雅 1.对羽西品牌有什么感觉，代表什么，怎么定位 2.人员管理 3.对时尚感兴趣吗 不凡帝 1.成功案例 2.生意增长的来源 3.销售计划 4.增强团队凝聚力 5.到了新公司准备怎么做 6.为什么考虑这个职位 7.目前团队的架构、人员结构、年龄、性格 8.每个卖场的生意占比，觉得哪个做的好 9.目前工作压力大不大 10.希望负责多大的生意量 Line 吉佰利 1．请描述一下你们公司的认识架构 2．下面的团队怎么分配的；如何管理团队 3．和经销商的关系如何；经销商的毛利，费用怎么操作4．用3个词来形容自己，为什么这样形容；个性优缺点5．与其他功能部门协调工作的案例 6．对灰色收入的看法 7．对未来的规划 8．更换工作的原因，过去的工作经验
美琳凯 1．离职原因 2．你认为自己适合的工作是什么样的 惠氏 1．如何带领团队 2．如何提升销售业绩 3．是否有医务渠道的经验 4．举一个例子说明自己的学习和创新能力 5．如果是一个需要迅速启动的市场会如何操作 Final 吉佰利 1.你再以前单位学到些什么 2.为什么要考虑我们公司 3.带领多大团队 4.生意量，在公司中占比 5.如何提升占比 6.用什么指标衡量下面人员 美琳凯 1．工作现状，认为自己做得很出色的事情 2．为什么考虑跳槽 3．处理投诉的案例 4．做美琳凯的优势 5．希望自己上司是什么样的 6．如果公司不能给你一些费用的支持，要如何处理客情关系7．最近在看什么书，有什么收获 二．常见NKA面试问题 HR 美赞臣 1.现在的状况如何，为什么考虑新的机会 2.卖场谈判如何操作 3.在谈判过程中有没有遇到过困难 4.应聘职位操作的卖场与现在已经操作的卖场有什么区别 5.期望的薪资，为什么期待这么多 飞利浦 1．以前的客户如何操作 2．面读比较强势的客户一般如何处理 3．带领团队达成目标如何 4．合同谈判之前一般会做什么准备 5．如何与销售团队沟通 6．离职原因 7．成功案例举例 APP
SAP系统BW模块配置和操作指导详解概述
SAP系统BW模块配置和操作指导详解概述 业务说明 基于SAP ECC6 使用RSA3 0TCT_DS01数据源可以查看对BW数据的读取情况。 为了从EP中链接到SAP系统，需要配置单点登录，另外需要用户在ECC中拥有RSRR_WEB的权限 本文是由塞依教育编辑整理，了解更多SAP培训信息，请进入https://www.wendangku.net/doc/de14568081.html,/knowledge/ 基本原理 以下是基于文件的BW设置的基本原理，也可以说是一个基本的操作过程。 1.设置一个源系统，用于确定数据从哪里来。 2.创建一个Datasource，用于存放抽取过来的数据。此时的抽取式通过InfoPackage实现的。 3.创建一个DataStore Object对象，用于存放处理后的数据。Datasource和DataStore Object之间通过Transformation（转换规则）进行关联，同时需要创建一个Transfer Process用于数据的抽取处理。每个DataStore Object是属于一个InfoArea，也就是说一个Info Area下可以根据需要按照不同的规则更新出不同DataStore Object。 4.在Explorer中创建一个查询，查询需要的数据，设计查询时可以设置一个过滤器进行必要的筛选。 Table RSIDOCSA VE 相关概念 BI（Business Intelligence，商务智能） SAP BI（SAP Business Information Warehouse） DW（Data Warehouse，数据仓库） DM （Data Mining，数据挖掘） OLTP（Online Transaction Process，在线事务处理） OLAP（Online Analysis Process，在线分析处理） 逻辑视图
行为面试题库-考核各项能力
行为面试题库 【有关计划与组织的面试问题】 你的工作时间表是否经常被没有预料的情况打乱？你是怎么做的？请给出一个最近的例子。 在你的时间表上你是如何决定哪些事最重要？给出例子。 你是否遇到过一次情况，所有的事情需要同事完成？你是如何处理的？结果如何？ 我们有时候对一些项目、活动、责任范围的理解会因人而异，请问你是否有过理解错误的经历，当时的情况是怎样的？你最终是如何解决的？ 你时候有过特别不成功的工作经历？你是否还记得当时的情况？你当时是怎么做的？ 【有关诚实正直的面试问题】 你是否遇到过你的客户问你的产品的弱点、不足之处的时候，你是怎么处理的？ 你是否有过当时客户所要求购买的比他们原先预算的要多的产品？具体情况是怎样的？你是怎样来处理的？ 你是否遇到过你的主管要求你做某事，但你却认为不合适的，或许是不符合公司规章 制度的，你会怎么办？ 我们总是希望与诚实的员工一起工作，请给我一个例子你是否看见某员工做的事你认为不合适，或者是违反公司规章制度的，当时你是怎么处理的？ 【有关执行力的面试问题】 我们在日常工作时，有时候可能会由于工作倦怠而忽略一些细节，以致造成损失。你有没有类似的经历？当时的情况是怎样的？为什么发生？之后你有做了什么？ 你是否遇到过你的主管要求你做某一项工作，你却有不同的想法和观点，但你的主管又没有接受你的建议，最终你是怎样处理的？ 【有关决策能力的面试问题】 有时候，我们虽承受执行的压力，但衡量利弊得失之后，仍决定不采取行动。请举一个这样的例子说明你这方面的经验。 谈谈在过去六个月内你曾面对最大的挑战问题是什么？你是如何处理？ 有时候我们需要快速作出决定，请讲述一次你要很快作出决定的经验，当时的情况怎样？ 请举一个你在工作方面的棘手问题。（你如何认清或者进一步了解问题症结所在？） 请实际讲述一个你必须多方咨询以收集信息的情况。（你如何指导该问些什么？） 有时候，我们很幸运能在问题扩大之前，及早解决。请举一个你及早发现问题以避免事态严重的例子。 【有关适应力的面试问题】 请举一例说明你面临意想不到的政策改变。这些改变对你产生什么影响？针对这些改变你采取了哪些行动？ 请举一例说明当您的客户联系人发生转变时，你用了多长时间同新联系人建立有效的工作关系？你对此采取了那些行动？ 谈谈你所遇到的最难共处的主管。（你如何处理这种棘手的关系？）
Tableau 基础入门
在本教程中，我们将在Tableau中进行一些基本操作，以熟悉其界面。创建任何Tableau数据分析报告涉及三个基本步骤。它们在下面给出。 ?连接到数据源: 它涉及定位数据并使用适当类型的连接来读取数据。 ?选择尺寸和度量: 这包括从源数据中选择所需的列进行分析。 ?应用可视化技术: 这涉及将所需的可视化方法（如特定图表或图形类型）应用于正在分析的数据。 在本教程中，我们将使用Tableau安装附带的样本数据集，名为sample - superstore.xls。找到Tableau的安装文件夹，然后转到My Tableau Repository 。在它下面你会发现上面的文件在Datasources \\ 9.2 \\ en_US-US。 连接到数据源 一个打开的Tableau，我们得到开始页面显示各种数据源。在标题连接下，我们有选择文件或服务器或保存的数据源的选项。在文件下，我们选择excel。 然后导航到文件“Sample - Superstore.xls"，如上所述。excel文件有三张命令，人和返回。我们选择订单。 选择尺寸和度量 接下来，我们通过决定尺寸和度量来选择要分析的数据。尺寸是描述性数据，而度量是数字数据。当放在一起时，它们帮助我们可视化关于作为度量的数据的维度数据的性能。我们选择类别和区域作为维度和销售额作为度量。 拖放它们，如下所示。结果显示每个区域的每个类别的总销售额。
应用可视化技术 在上一步中，我们看到数据仅作为数字可用。我们必须读取和计算每个值来判断性能。但我们可以将它们看作是具有不同颜色的图表或图表，以便更快地做出判断。 我们将总和(销售)列从“标记"标签拖放到“列"货架。现在，显示销售额数值的表格会自动变为条形图。
SAP BW配置及操作手册(BW中文图文教程)
SAP BW配置及操作手册 SAP BW配置及操作手册 概述 业务说明 基于SAP ECC6 使用RSA3 0TCT_DS01数据源可以查看对BW数据的读取情况。 为了从EP中链接到SAP系统，需要配置单点登录，另外需要用户在ECC中拥有RSRR_WEB 的权限 基本原理 以下是基于文件的BW设置的基本原理，也可以说是一个基本的操作过程。 1.设置一个源系统，用于确定数据从哪里来。 2.创建一个Datasource，用于存放抽取过来的数据。此时的抽取式通过InfoPackage实现的。 3.创建一个DataStore Object对象，用于存放处理后的数据。Datasource和DataStore Object 之间通过Transformation（转换规则）进行关联，同时需要创建一个Transfer Process用于数据的抽取处理。每个DataStore Object是属于一个InfoArea，也就是说一个Info Area下可以根据需要按照不同的规则更新出不同DataStore Object。 4.在Explorer中创建一个查询，查询需要的数据，设计查询时可以设置一个过滤器进行必要的筛选。 T able RSIDOCSA VE
相关概念 BI（Business Intelligence，商务智能） SAP BI（SAP Business Information Warehouse）DW（Data Warehouse，数据仓库） DM （Data Mining，数据挖掘） OL TP（Online Transaction Process，在线事务处理）OLAP（Online Analysis Process，在线分析处理） 逻辑视图 概念（BW） 信息区域（Info Area）
面试问题考察
普通应聘者问题 第一部分人格特质面问题 一、人际沟通交往能力 1.请举例说明你与同事意见有分歧时，你是如何处理从而达成一致的。 测评要点：主要考察应聘者的人际沟通能力，在别人的否定面前，能否坚持自己观点，并有计划的说服别人接受自己的想法。 2.请说说当你有好的创意时，你是怎么让同事和主管认可的。 测评要点：主要考察应聘者的人际沟通能力，能否很好的阐述自己的想法和观点，让别人接受。 3.当你的工作需要有其他部门配合时，你通过什么方法达到目的，请举例说明。 测评要点：主要考察应聘者的人际沟通能力，能否有效的做到横向的沟通。 4当你正干着一项工作时，领导又让你干另一项工作，因为只有你具有相关的专业知识。在这种情况下，你将怎么处理为什么 测评要点：主要考察应聘者的人际沟通能力，能否做到有效的纵向沟通。 5假如你的两个同事的冲突已经影响到整个团队，让你去调节冲突，并使冲突双方能够自己解决问题，你会怎样做 测评要点：主要考察应聘者的人际沟通能力，能否在不伤害到双方的利益的情况下化解矛盾。 6如果你以后有机会成为组长或者以上的领导，你向员工提出了一个很不受欢迎的想法，你采用什么办法来减少员工对这一想法的抵触情绪 测评要点：主要考察应聘者的人际沟通能力，能否在对下的时候做到化解员工的抵触情绪。 7在完成某项工作时，你认为你上级领导的要求的方式不是最好的，自己有更好的方法，你该如何处理 测评要点：主要考察应聘者的人际沟通能力，能否做到有效的纵向沟通。 8请介绍下你和你最好的朋友是怎么相处的，如何解决分歧和隔阂 测评要点：主要考察应聘者的人际沟通能力，从朋友的相处看应聘者在平等关系中能否有效地解决分歧。 二、责任心 1.你是否愿意向上级提些合理化建设 测评要点：主要考察应聘者的责任心，是否愿意为公司贡献自己的才智。 2 假如分配给你一项任务，眼看着期限将到难以完成，你怎么办 测评要点：主要考察应聘者的责任心怎样，能否顶着压力加班加点完成任务。
S r面试提问范例
最近的工作经验 4.1、每个人在工作中都会有特别紧张和繁忙的时候。现在请你告诉我你最近经 历过的非常紧张和繁忙的时候。 ?这是什么时候的事？ ?这段时间与平时相比使你感到紧张的程度如何？ ?你是如何度过这段时间的？ ?你最终将工作完成得怎么样？ 3.1、你能够想到你最近完成的工作，它可以反映出你运用新技术去解决工作中 遇到的问题吗？ ?那是什么样的问题？ ?你用了什么新技术？ ?你是如何学会这种技术的？ ?使用这种技术取得了什么样的结果？ ?这种技术与你通常使用的技术相比，有哪些优点和缺点？ 3.2、请你告诉我在过去几个月内你涉猎到的对你工作很有启发的资料。 ?该资料的大致内容是什么？ ?你是从哪里获得该资料的？ ?你仔细阅读该资料了吗？ ?资料中的观点给你什么样的启发？ ?资料中的观点对你的工作有什么用处？
工作经历或习惯 1.1、能够以较高的标准要求自己对于研发人员而言很重要。你能讲一件事说明 你在工作中精益求精吗？ ?你当时要完成的任务是什么？ ?你要达到的正常标准是什么？ ?你完成的任务到达什么水平？ ?你这样作是出于什么想法呢？ ?你经常以这种方式工作吗？ 1.2、你能回忆一件你在工作中力求提高产品的性能或工作效率的事情吗？ ?当时你从事的是什么样的任务？ ?当时工作或产品处于什么样的情形？ ?你为什么要对它进行改进？ ?你采取什么方法改进它？ ?改进之后有哪些优点？ ?别人对你的工作有何评价？ 3.3、请讲出一件你通过学习尽快胜任新的工作任务的事。 ?你要从事的工作任务是什么？ ?接到任务后你怎么办？ ?你用了多长时间获得完成该任务所必须的知识？ ?你在这个过程中遇见困难了吗？ ?你最后完成任务的情况如何？ 4.2、人在面对极大压力时都会想办法解除压力。你曾经在工作中面对过非常大 的压力吗？
基于 Tableau 软件的数据分析领域预测方法(IJIEEB-V11-N1-3)
I.J. Information Engineering and Electronic Business, 2019, 1, 19-26 Published Online January 2019 in MECS (https://www.wendangku.net/doc/de14568081.html,/) DOI: 10.5815/ijieeb.2019.01.03 An Approach for Forecast Prediction in Data Analytics Field by Tableau Software Bibhudutta Jena Email: bibhudutta93@https://www.wendangku.net/doc/de14568081.html, Received: 13 December 2017; Accepted: 18 October 2018; Published: 08 January 2019 Abstract—The current era is generally treated as the era of data, Users of computer are gradually increasing day by day and vast amount of data is generated from multiple domains such as healthcare- domain, Business related domains etc. The terminology Business Intelligence (BI) generally refers different technologies, applications and practices used for the collection, integration, analysis, and presentation of information of business related domain. The main motive for Business intelligence and analytics are to help in decision making process and to enhance the profit of the organisation. Various business related tools are used to analyze & visualize different types of data which are generated frequently. Tableau prepared its mark on the Field of BI by being one of the first companies to permit business customers the ability to achieve equitably arduous data visualization in a very interesting, drag and drop manner. Tableau will enhance decision making, add operational awareness, and increase performance throughout the organization The presented paper describes different tools used for business intelligence field and provides a depth knowledge regarding the tableau tool. It also describes why tableau is widely used for data visualization purpose in different organization day by day. The main aim of this paper is to describe how easily forecasting and analysis can be done by using this tool ,this paper has explained how easily prediction can be done through tableau by taking the dataset of a superstore and predict the forthcoming sales and profit for the next four quarters of the forthcoming year. In the collected dataset sales and profit details of different categories of goods are given and by using the forecasting method in tableau platform these two measures are calculated for the forthcoming year and represented in a fruitful way. Finally, the paper has compared all the framework used for business intelligence and analytics on the basis of various parameters such as complexity, speed etc. Index Terms—Big Data, Business Intelligence, Data Visualization, Tableau, QlickVieew. I.I NTRODUCTION Due to the increased market competition increased data management and analysis has landed as in an era that requires further optimization data management and analysis. Big data technologies like apache HADOOP provide a frame work for parallel data processing and generation of analyzed results .MAPREDUCE method is used for analysis of data using various data analysis algorithms like clustering, fragmentation and aggregation. (BI) generally refers different technologies, applications and practices used for the collection, integration, analysis, and presentation of information of business related domain[1]. The main motive for Business intelligence and analytics are to help in decision making process and to enhance the profit of the organisation. Various business related tools are used to analyze & visualize different types of data which are generated frequently. Data is one of the most important and vital aspect of different activities in today's world. Now -a -days the modern civilization gradually more dependent on the age of information which is concentrated in computers, So the Society is becoming more dependent on computers and technology for functioning in every- day life .As the number of users are gradually increasing day by day, So the data generated by them is also enlarging gradually[2].The main aim of this paper is to describe how easily forecasting and analysis can be done by using this tool ,this paper has explained how easily prediction can be done through tableau by taking the dataset of a superstore and predict the forthcoming sales and profit for the next four quarters of the forthcoming year. The reminder of this paper is organized as. Section II presents a literature survey on various approaches and tools used for business intelligence and analysis purpose. Section III presents a brief idea about Tableau tools and its application. The motivation for this work is laid out in Section II. Section IV represents the Implementation part for the forecast analysis of sample retail store data Finally, Section V concludes the paper. II.L ITERATURE S URVEY Tableau presently has the largest customer domain. When businesses organization are focusing for a BI solution, it’s always their first choice. In the below section the paper has described different BI tools that are currently used in the business market for enhancing the business strategy. Sisense is one of the leaders in the market of BI and a winner of the Best Business Intelligence Software Award given by Finances Online [3][4], It was considered as one of the most adopted business, software review platforms. The users of this
Tableau 设计流程之数据类型介绍
Tableau 设计流程 由于Tableau帮助我们分析许多时间段，维度和度量的大量数据，因此需 要非常细致的规划来创建良好的仪表板或故事。因此重要的是要知道设计一个 好的仪表板的方法。像任何其他人类努力领域一样，有许多最佳实践要遵循， 以创建良好的工作表和仪表板。 虽然从Tableau项目预期的最终结果是理想的仪表板与故事，有许多中间 步骤，需要完成达到这一目标。以下是创建有效仪表板时应该理想地遵循的设 计步骤流程。 连接到数据源 Tableau连接到所有常用的数据源。它具有内置的连接器，在提供连接参 数后负责建立连接。无论是简单文本文件，关系源，无Sql源或云数据库，tableau几乎连接到所有数据源。 构建数据视图 连接到数据源后，您将获得Tableau环境中可用的所有列和数据。您可以 将它们分为维，度量和创建任何所需的层次结构。使用这些，您构建的视图传 统上称为报告。Tableau提供了轻松的拖放功能来构建视图。 增强视图 上面创建的视图需要进一步增强使用过滤器，聚合，轴标签，颜色和边框 的格式。 创建工作表 我们创建不同的工作表，以便对相同的数据或不同的数据创建不同的视图。创建和组织仪表板
Tableau 数据类型 作为数据分析工具，Tableau将每个数据分为四个类别之一，即 - String，Number，Boolean和datetime。从源加载数据后，tableau会自动分配数据类
Tableau 显示 作为一种高级数据可视化工具，Tableau通过提供许多分析技术，无需编 写任何自定义代码，即可轻松实现数据分析一个这样的功能是显示。使用它， 我们只需要应用一个必需的视图到工作表中的现有数据。这些视图可以是饼图，散点图或折线图。 无论何时创建带有数据的工作表，它都会显示在右上角，如下所示。某些 视图选项将显示为灰色，具体取决于数据窗格中所选内容的性质。 显示两个字段
【岗位说明书】SAPBW配置及其操作手册
E:\80万word\管理信息化-综合\doxc转doc\.....\ E:\80万word\管理信息化-综合\doxc转doc\.....\
SAP BW配置及操作手册 SAP BW配置及操作手册 概述 业务说明 基于SAP ECC6 使用RSA3 0TCT_DS01数据源可以查看对BW数据的读取情况。 为了从EP中链接到SAP系统，需要配置单点登录，另外需要用户在ECC中拥有RSRR_WEB 的权限 基本原理 以下是基于文件的BW设置的基本原理，也可以说是一个基本的操作过程。 1.设置一个源系统，用于确定数据从哪里来。 2.创建一个Datasource，用于存放抽取过来的数据。此时的抽取式通过InfoPackage实现的。 3.创建一个DataStore Object对象，用于存放处理后的数据。Datasource和DataStore Object 之间通过Transformation（转换规则）进行关联，同时需要创建一个Transfer Process用于数据的抽取处理。每个DataStore Object是属于一个InfoArea，也就是说一个Info Area下可以根据需要按照不同的规则更新出不同DataStore Object。 4.在Explorer中创建一个查询，查询需要的数据，设计查询时可以设置一个过滤器进行必要的筛选。 Table RSIDOCSA VE
相关概念 BI（Business Intelligence，商务智能） SAP BI（SAP Business Information Warehouse）DW（Data Warehouse，数据仓库） DM （Data Mining，数据挖掘） OL TP（Online Transaction Process，在线事务处理）OLAP（Online Analysis Process，在线分析处理） 逻辑视图 概念（BW） 信息区域（Info Area）
招聘面试考核内容
招聘面试考核内容 业务员应具备的基本素质： ①有正确的人生观，品德好，勤奋、能吃苦、有团队精神。 ②责任感、自信心和沟通能力。 ③基本礼仪，无不良嗜好。 ④学习能力。 ⑤身体健康。 区域经理应具备的基本素质： ①有正确的人生观，品德优秀，勤奋、能吃苦，有团队精神。 ②责任感、自信心。 ③相应的智商和情商，一定的知识水准。 ④基本礼仪，无不良嗜好。 ⑤学习能力。 ⑥领导力： a、组织协调能力； b、沟通能力； c、管理魄力； d、综合分析能力； e、说服能力。 不予录用情形： 招聘业务员，有下列情况者不予录用：
（1）两年内换过五个单位； （2）身体相貌有缺陷； （3）信用可疑，有坏习惯记录或不良行为记录； （4）因合并、销售业绩下降而失业； （5）离不开家庭，或对工作需要出差犹豫不决； （6）最近几年有入院治疗记录； （7）体态太胖者。 一、面试要素：行为动机。 ◆观察要点：工作兴趣与岗位是否匹配，期望值与公司情况是否匹配；成就动机是否与岗位匹配。 ①请你谈谈过去的学习生活和工作经历？为什么加入我们公司？ ②在你的工作经历中，最成功的是哪一段（成功在什么地方？为什么成功？），最失败的是哪一段？（为什么失败？） ③你为什么要应聘这个职位，你认为有哪些有利条件？还有哪些不利条件？怎么克服不利条件？ ④为什么要变换工作； ⑤为什么在一年中换两次工作； ⑥在失业期间，你做些什么； ⑦希望有什么样的薪金水平； ⑧以前的收入或佣金是多少； ⑨你希望公司如何安排你的工作？（你在选择工作时都考虑哪些因素？）个人有什么长远打算？
⑩如果现在给你100万你准备怎样花费？ 你对这个工作最喜欢哪些方面，最不喜欢哪些方面？ 好：考生意向清楚，态度诚实，有较强的事业追求，又不回避生活需要，职位条件达到或超过考生预期；在追问下情绪稳定。 中：基本意向清楚可信，求职动机与职位条件不冲突，情绪基本稳定。 差：意向模糊不清，态度虚假，或求职动机与职位条件冲突，在追问下情绪不稳定或失控。 学生行为动机及能力测试： ①你喜欢哪一门课程？ ②在学校你都参加过什么活动？ ③你的学习成绩如何？在班上位置如何？你的学习习惯怎样？ ④为什么学习这个专业，你当初的职业考虑是什么？你最喜欢什么职业？ ⑤在学校几年，你认为你最大收获是什么？ ⑥你的假期是怎么过的？ ⑦在学校参加过什么团体？获过何种荣誉？你最珍惜那一种荣誉？ ⑧未来二年或五年有什么打算？ 参考评分标准： 好：考生对自己未来设想明确，做出的准备全面、充分，表达清晰、流畅，动机与岗位匹配；有相应的组织能力，分析问题、解决问题的能力。 中：考生对未来有设想，有一定准备；表达有条理，动机合理，有一定的能力。
Tableau Server-最佳商业智能云平台
We?Help?People?See?and?Understand?Data
?
Tableau?Server: 最佳商业智能云平台
—
商业智能工具的明智之选
—
Tableau Software 是一个商业智能应用平台， 结合了 Tableau Desktop 前端智能分析工具 与 Tableau Server 云端发布平台，不仅具备了高效直观的可视化数据分析功能，更提供了基于 浏览器的分享应用功能。在传统商业智能工具中，缓慢的处理速度让数据处理犹如陷入泥潭之 中，而选择 Tableau，其易学实用的特点。则无疑为您的数据处理工作开启了便捷高效的大门。 您也许常会遇到这样的问题：您需要完成某项工作，然而现有的工具却笨重而缓慢。 Tableau 将提供给您一个新的选择。作为杰出的新一代智能商务平台，它将數據分析处理能量 提高了数百倍，这无疑是它聪明高效的证明。只要您需要，您还可以随时扩展它的功能。同时， 客户在线培训中心让您不必费时费力就可以自力开始 Tableau Software 的体验之旅。 任何使用 过程中您遇到的问题，数天之内就将会得到解答。
操作面板的在线交互功能
您可以将所需的所有数据嵌入 Tableau 强大的操作面板 中，接着将它发布在 Tableau Server 云端服务器上，以便您 通过浏览器就可以进行数据过滤、高亮显示、钻取数据等功 能，同时可按数据分析的不同深度了解各种相关情况。它可 以方便的嵌入在您的门户网站中或者 Share Point 网站上， 或直接随邮件发出链接。依信息需要订制数分钟或数小时内 即时更新数据。 使用 Tableau，只需几次点击或拖放数据，您就可方便的将电子表格或数据库的数据变为 操作面板中的可视化视图。当您的客户、同事、工作伙伴登录一个进过安全认证的网站时，您 就可以提供给他们相应的动态交互的可视化视图，并透过这些视图回答他们的疑问。所有这些 完成所需要的时间，将快的超乎您的想象。
从等待的泥潭中解放出来
在众多商业工具中，能够自助服务的商业智能工具是最 为便捷高效的。如今，商业用户可以透过 Tableau 这样的工 具来自主完成报表。他们可以将所分析的问题或解答，变为 当前最需要优先考虑的事情和付诸实践的工作事项。从此商 业用户可以专注于商业活动中，而 IT 人员也可以由忙于应付 多变的使用者需求当中脱身，而进行更有价值的 IT 事务。
Tableau Server 1 support@https://www.wendangku.net/doc/de14568081.html,?
手把手教你Tableau高级数据分析功能(附数据集)
手把手教你Tableau高级数据分析功能（附数据集） 原文标题：A Step-by-Step Guide to learn Advanced Tableau –for Data Science and Business Intelligence Professionals作者：Pavleen Kaur翻译：李清扬校对：卢苗苗本文共4000字，建议阅读8分钟。 本文借助高级图表创建计算深入研究数据以提取对数据的 分析，并了解R如何与Tableau相互集成和使用。 简介 “查看数据。显示图表。讲故事。吸引观众。”Tableau是当今数据科学和商业智能专业人员使用的最流行的数据可视化工具之一。它使您能够以交互和多彩的方式创建具有洞察力和影响力的可视化效果图。它的用途不仅仅是创建传统的图表和图表。您可以使用它来挖掘可操作的数据解析，这要归功于它提供的大量功能和自定义。以其易用性和简单的功能而闻名，制作如下所示的富有洞察力的仪表盘只需点击几下鼠标：在本文中，我们将看到一些超越拖放功能的高级图表。我们将创建计算以深入研究数据以提取对数据的分析。我们还将看看R如何与Tableau相互集成和使用。本文假定您掌握丰富的使用Tableau的知识，例如基本图表形成，计算，参数等。如果您不这样做，我会建议先参考以下文章，然后再返回此处：
Tableau for Beginners - 简化数据可视化中级Tableau指南- 适用于数据科学和商业智能专业人员 -science/ 目录1. 高级图形- 可视化超越“显示我”运动图凹凸图甜甜圈图表瀑布图帕累托图2. 在Tableau中引入R编程1. 高级图形- 可视化超越'Show Me' 几乎所有的Tableau用户都知道各种基本图形，例如介绍仪表板中显示的那些图形。这些图表可以使用Tableau的“Show Me”功能轻松完成。但由于这是一篇面向高级用户的文章，因此我们将超越“Show Me”并探索需要额外计算的图表。首先，让我们快速浏览一下我们将在接下来的几节中做什么。以下是我们超市的销售额和利润的一些基本分析。简单的图表可以达到与主板中的相同的目的，但我认为您会对这些图表的宏伟感到兴奋和激动。()1.1动态图表在开始之前，先看看Hans Rosling的世界经济图表展示()。点击播放键，看到魔法在你面前展开。有兴趣自己做一个类似的图表展示吗？不要担心如何做这些动画！你所看到的被称为动态图表。使用此功能，您可以实时查看数据中的变化。因此，我们首先下载可在此处找到的Superstore数据集()。现在让趋势线如下图所示对你来说应该很容易：但是本节我们首先要学习的是如何使下面的趋势线运动（gif动图）： 所以让我们开始吧！ 导入您的数据集，并创建上述趋势图。我们的X轴是订单
Tableau教程_新手教程—函数篇之index()
从一个应用场景开始，BOSS需要一份数据，近几年每年销售额最高的10个产品，以及这些产品在每年营业额的累积占比，就是下面这个图中 蓝色的条形代表每个产品在当年的销售额，橙色三角形表示累积销售占比，我们可以看到，10个产品的销售额达到了20%
接下来我们就需要用Index()函数来制作上图 官方对index的解释：返回分区中当前的索引 个人觉得把“索引”两个字换成“行号”更好理解，严谨一些的说法是，根据特定排序规则返回分区中当前行号 下面一步一步演示给大家如何制作上图： 老规矩，使用系统自带数据源superstore，打开Tableau Desktop设计界面 1、在度量区域，空白处点击右键，创建-->计算字段内容为index() 字段名为Index 2、[Order Date] [Product Name]拖至行功能区，[Sales] [index]分别拖至列功能区 3、右键列功能去中的Index字段-->编辑表计算根据以下因素计算-->高级
4、将Order Date 年 product Name 选择至寻址框，顺序不能乱哦 排序-->字段-->Sale-->总计-->降序确定 5、重新启动间隔-->Order Date年确定
6、接下来的报表是这个样子啦
7、右键Index字段，转换为离散，而后将Index字段拖至行功能区[Order Date] 与[Product Name]之间，我们可以看到Sales已经逆序了 8、按住Ctrl键，将Index字段拖至标记功能区，右键转换为连续，再把拖至筛选器，范围选择1--------10，确定，重点的东西已经做完了，下面是锦上添花 9、再拖一个Sales至列功能区，右键-->添加表计算- 计算类型-->汇总 计算因素-->高级 弹出窗口中操作： 寻址--> Order Date 年Product Name 排序-->自动-->Sales-->总计-->降序确定 重新启动间隔-->Order Date 年 勾选对结果执行从属计算 从属类型：总额百分比 值汇总范围：区
- 基于 Tableau 软件的数据分析领域预测方法(IJIEEB-V11-N1-3)
- Tableau商业智能BI平台采购技术要求
- Tableau图表实战——Nieson
- 数据可视化Tableau商业培训教材
- Tableau基础使用指南-新版.pdf
- Tableau实时数仓解决方案
- 手把手教你Tableau高级数据分析功能(附数据集)
- Tableau中文简介
- Tableau超详细教程-案例实践项目
- Tableau教程_经典图例之Nightingale's Rose(玫瑰图)
- Tableau培训入门介绍
- Tableau基础使用指南ppt课件
- Tableau入门3数据处理
- Tableau培训ppt课件
- Tableau基础使用指南ppt课件
- Tableau Server-最佳商业智能云平台
- 手把手教你Tableau高级数据分析功能(附数据集)
- Tableau教程_如何将除了Top 10以外的数据显示为-其它
- Tableau简介(商业智能)
- Tableau 基础入门