Details Desplay Dialog

Hello all,
i face the attached error after deploying the hardware connected to the EtheCAT CRIO9024 port, and the robot doesn't move at all. Can u help me find out what this error msg is about?
Thanks and regards,
Samira
Attachments:
error list.pdf ‏298 KB

Hello hsm78,
thanks but i have run this vi without problems before, and recently i face strange error msges like the one i attached earlier or the other one here attached. What do u think might be wrong?
regards,
Samira
Attachments:
error.pdf ‏324 KB

Similar Messages

HT204135 How can one make the printer dialog box to have Show Details as default?

I very often use different presets from document to document. Thanks.

Once you select the Show Details for any application, the next time you use that application and select to print, the full details pane should be shown.
If this is not happening and the applications always show the Hidden Details print dialog then you may need to perform some sort of reset.
Also, if you were to use the Presets option and set commonly used settings as a Preset, then even if the print dialog is not showing the extra details, you can still select the desired Preset from this print dialog.

In CQ5 How to retrieve information stored provided via dialog and stored in a node of content folder

Hi,
I have to get few details in dialog of a component and stored it in node of the content package. how can i retrieve the saved information from the jsp.?
any help will be helpful.
Thanks in advance.

Hi Raja,
In a component's jsp, assuming <cq:defineObjects> has been called, you can use the properties scripting variable to get the node's properties.
Have you gone through the tutorial at http://dev.day.com/docs/en/cq/current/developing/components.html#Extending%20the%20Text%20 and%20Image%20Component%20-%20An%20Example ?
Regards,
Justin

Growing a JOptionPane dialog vertically

I am writing a simple JPanel for use within message dialogs.
Just wanted to add "more details" functionality really, for error dumps etc.
I've so far used this with JOptionPane:
 DetailsPanel detailsPanel = new DetailsPanel();
 detailsPanel.setMessage("Some error occurred");
 detailsPanel.setMessageDetails("Error dump details, stack trace, blah blah...");
 JOptionPane.showMessageDialog(frame, detailsPanel, "ERROR", JOptionPane.ERROR_MESSAGE);
However, when the button is clicked to display the extra details, the dialog doesn't resize to account for the extra text. I'm using a GridBagLayout manager, but previously had a BorderLayout. Neither seem to work. Have tried adding to a frame manually, same effect. Tried explicitly resizing the panel and parent, revaliding, invalidating, repainting blah blah.
Am I missing something obvious? Thanks for any help. Andy.
Here is the class:
import java.awt.GridBagConstraints;
import java.awt.GridBagLayout;
import java.awt.event.ActionEvent;
import java.awt.event.ActionListener;
import javax.swing.JButton;
import javax.swing.JLabel;
import javax.swing.JPanel;
import javax.swing.JScrollPane;
import javax.swing.JTextArea;
* Displays a string message and allows user to expand "more details" for
* error output etc.
* Can be used in conjunction with javax.swing.JOptionPane:
* DetailsPanel details = new DetailsPanel();
* details.setMessage("Something bad happened");
* details.setMessageDetails("Error code 12345 -- system dump, stack trace...");
* JOptionPane.showMessageDialog(someParentComponent, details, "ERROR", JOptionPane.ERROR_MESSAGE);
* @version 1.00 21/05/02
* @author Andy Carter ([email protected])
public class DetailsPanel extends JPanel implements ActionListener
 private static final String MORE_DETAILS = "Details >>";
 private static final String LESS_DETAILS = "<< Details";
 private boolean detailsHidden = true; // default
 private JLabel messageLabel; // used to display a message
 private JButton detailsButton; // used to control whether or not "more details" are visible
 private JTextArea detailsTextArea; // used to display "more details" about the message
 private JScrollPane detailsScrollPane; // used to allow scrolling over the text-area
 private JPanel internalPanel; // used for a better layout
 * Default constructor.
 * Sets up...
 public DetailsPanel()
 super();
 /* Set up the controls: */
 messageLabel = new JLabel();
 detailsButton = new JButton(MORE_DETAILS); // because detailsHidden == true
 detailsButton.addActionListener(this);
 detailsTextArea = new JTextArea();
 detailsTextArea.setEditable(false); // user can copy to clipboard but not edit the text
 detailsScrollPane = new JScrollPane();
 detailsScrollPane.setViewportView(detailsTextArea);
 detailsScrollPane.setVisible(false);
 /* Set the layout for and add all the components: */
 setLayout(new GridBagLayout());
 GridBagConstraints constraints = new GridBagConstraints();
 constraints.anchor = GridBagConstraints.WEST;
 constraints.gridx = 0;
 constraints.gridy = 0;
 add(messageLabel, constraints);
 constraints.gridy = 1;
 add(detailsButton, constraints);
 constraints.gridy = 2;
 add(detailsScrollPane, constraints);
 * Sets the message to be displayed.
 * @param message java.lang.String
 public void setMessage(String message)
 messageLabel.setText(message);
 * Gets the message to be displayed.
 * @return java.lang.String
 public String getMessage()
 return messageLabel.getText();
 * Sets the extra details about the message.
 * displayed by
 * @param message java.lang.String
 public void setMessageDetails(String message)
 detailsTextArea.setText(message);
 * Gets the extra details about the message.
 * @return java.lang.String
 public String getMessageDetails()
 return detailsTextArea.getText();
 * Fired when the an action is performed on the "more details" button.
 * Makes any extra details about the message visible.
 public void actionPerformed(ActionEvent e)
 /* Toggle whether or not details are hidden: */
 detailsHidden = !detailsHidden;
 detailsScrollPane.setVisible(!detailsHidden);
 /* Set the text of the button to indicate the current state: */
 String newButtonText = detailsHidden ? MORE_DETAILS : LESS_DETAILS;
 detailsButton.setText(newButtonText);

Pass in the java.awt.Window reference in the DetailsPanel constructor. Then, when the user clicks the "Details" button, call window.pack( ). This will make the frame/dialog resize.
From your code:
private Window window ;
public DetailsPanel(JFrame window)
super();
this.window = window ;
String newButtonText = detailsHidden ? MORE_DETAILS : LESS_DETAILS;
detailsButton.setText(newButtonText);
window.pack( ) ;
}

User account errors and some work-arounds

1. Migrate multiple users, but second on no set up correctly
I had this when I tried to migrate one user then a second as a subsequent migration. Home directory was created but no user was created in Sys Prefs. Sadly, the user name was created in the system somewhere and I could not re-use.
Workaround. Migrate all users together.
2. Library being duplicated for every user.
My library file is 25Gb, and this is being duplicated for every user. I thought this was a shared resource under Tiger ....? My disk space is taking a hammering.
Workaround: Unknown
3. Delete a user and try to re-add
If you delete a user, and all files etc., you would expect to be able to re-add. Nope. The name remains persistent in some system file(s) somewhere, even after a re-boot.
Workaround: Fresh install. Ugh!
4. Drag-and-drop not working in Finder/Desktop
OK, got drag and drop working on MBP with 10.5.1 and G5 Quad under 10.5.1.
It appears that the second and on users when performing a migrate are not set up properly.
If drag-and-drop isn't working, go into Sys Prefs, Accounts, and create a Group. Add the non-functioning account to the group (I did both).
I ran Repair Permissions (lots of errors that SUID would not fix, to do with frameworks and identities, so I left alone. Many other permissions errors fixed).
Logged out .... btw, intermittent bug where you cannot log out a second account that's running as it doesn't take the name or password. You have to switch user and log it out that way.
Log back to the user with the drag and drop issue. Shutdown and then start back up.
When you log back in, drag and drop should work..... and keep on working whether you switch user etc.
Also, if you now remove the Group from Sys Prefs./Accounts, drag and drop will still continue to work. (I haven't tried a restart to see whether it is persistent though.)
If anyone has better workarounds or - preferably - fixes, please let me know.
Thank you.

Mary,
You do not tell us the method of authentication you have implemented.
If you are having NTIntegrated authentication, you should check if the eliteadm workflow user record contains her nt logon credentials?
You can flag that user as deleted, but before you do, make sure it does not contain any id that you need to use later (such as email or nt account details, if either is used for user identification purposes.)
RE stalling workitem - when you view the details of the stalled record in the 'Stalled workitems' list, you should be able to also read an error message giving you a clue of what went wrong. Either double click on the item to see details in dialog or expand all columns in the console to read details.
Good luck,
Sanna

How to select the data efficiently from the table

hi every one,
i need some help in selecting data from FAGLFLEXA table.i have to select many amounts from different group of G/L accounts
(groups are predefined here which contains a set of g/L account no.).
if i select every time for each group then it will be a performance issue, in order to avoid it what should i do, can any one suggest me a method or a smaple query so that i can perform the task efficiently.

Hi ,
1.select and keep the data in internal table
2.avoid select inside loop ..endloop.
3.try to use for all entries
check the below details
Hi Praveen,
Performance Notes
1.Keep the Result Set Small
You should aim to keep the result set small. This reduces both the amount of memory used in the database system and the network load when transferring data to the application server. To reduce the size of your result sets, use the WHERE and HAVING clauses.
Using the WHERE Clause
Whenever you access a database table, you should use a WHERE clause in the corresponding Open SQL statement. Even if a program containing a SELECT statement with no WHERE clause performs well in tests, it may slow down rapidly in your production system, where the data volume increases daily. You should only dispense with the WHERE clause in exceptional cases where you really need the entire contents of the database table every time the statement is executed.
When you use the WHERE clause, the database system optimizes the access and only transfers the required data. You should never transfer unwanted data to the application server and then filter it using ABAP statements.
Using the HAVING Clause
After selecting the required lines in the WHERE clause, the system then processes the GROUP BY clause, if one exists, and summarizes the database lines selected. The HAVING clause allows you to restrict the grouped lines, and in particular, the aggregate expressions, by applying further conditions.
Effect
If you use the WHERE and HAVING clauses correctly:
There are no more physical I/Os in the database than necessary
No unwanted data is stored in the database cache (it could otherwise displace data that is actually required)
The CPU usage of the database host is minimize
The network load is reduced, since only the data that is required by the application is transferred to the application server.
Minimize the Amount of Data Transferred
Data is transferred between the database system and the application server in blocks. Each block is up to 32 KB in size (the precise size depends on your network communication hardware). Administration information is transported in the blocks as well as the data.
To minimize the network load, you should transfer as few blocks as possible. Open SQL allows you to do this as follows:
Restrict the Number of Lines
If you only want to read a certain number of lines in a SELECT statement, use the UP TO <n> ROWS addition in the FROM clause. This tells the database system only to transfer <n> lines back to the application server. This is more efficient than transferring more lines than necessary back to the application server and then discarding them in your ABAP program.
If you expect your WHERE clause to return a large number of duplicate entries, you can use the DISTINCT addition in the SELECT clause.
Restrict the Number of Columns
You should only read the columns from a database table that you actually need in the program. To do this, list the columns in the SELECT clause. Note here that the INTO CORRESPONDING FIELDS addition in the INTO clause is only efficient with large volumes of data, otherwise the runtime required to compare the names is too great. For small amounts of data, use a list of variables in the INTO clause.
Do not use * to select all columns unless you really need them. However, if you list individual columns, you may have to adjust the program if the structure of the database table is changed in the ABAP Dictionary. If you specify the database table dynamically, you must always read all of its columns.
Use Aggregate Functions
If you only want to use data for calculations, it is often more efficient to use the aggregate functions of the SELECT clause than to read the individual entries from the database and perform the calculations in the ABAP program.
Aggregate functions allow you to find out the number of values and find the sum, average, minimum, and maximum values.
Following an aggregate expression, only its result is transferred from the database.
Data Transfer when Changing Table Lines
When you use the UPDATE statement to change lines in the table, you should use the WHERE clause to specify the relevant lines, and then SET statements to change only the required columns.
When you use a work area to overwrite table lines, too much data is often transferred. Furthermore, this method requires an extra SELECT statement to fill the work area. Minimize the Number of Data Transfers
In every Open SQL statement, data is transferred between the application server and the database system. Furthermore, the database system has to construct or reopen the appropriate administration data for each database access. You can therefore minimize the load on the network and the database system by minimizing the number of times you access the database.
Multiple Operations Instead of Single Operations
When you change data using INSERT, UPDATE, and DELETE, use internal tables instead of single entries. If you read data using SELECT, it is worth using multiple operations if you want to process the data more than once, other wise, a simple select loop is more efficient.
Avoid Repeated Access
As a rule you should read a given set of data once only in your program, and using a single access. Avoid accessing the same data more than once (for example, SELECT before an UPDATE).
Avoid Nested SELECT Loops
A simple SELECT loop is a single database access whose result is passed to the ABAP program line by line. Nested SELECT loops mean that the number of accesses in the inner loop is multiplied by the number of accesses in the outer loop. You should therefore only use nested SELECT loops if the selection in the outer loop contains very few lines.
However, using combinations of data from different database tables is more the rule than the exception in the relational data model. You can use the following techniques to avoid nested SELECT statements:
ABAP Dictionary Views
You can define joins between database tables statically and systemwide as views in the ABAP Dictionary. ABAP Dictionary views can be used by all ABAP programs. One of their advantages is that fields that are common to both tables (join fields) are only transferred once from the database to the application server.
Views in the ABAP Dictionary are implemented as inner joins. If the inner table contains no lines that correspond to lines in the outer table, no data is transferred. This is not always the desired result. For example, when you read data from a text table, you want to include lines in the selection even if the corresponding text does not exist in the required language. If you want to include all of the data from the outer table, you can program a left outer join in ABAP.
The links between the tables in the view are created and optimized by the database system. Like database tables, you can buffer views on the application server. The same buffering rules apply to views as to tables. In other words, it is most appropriate for views that you use mostly to read data. This reduces the network load and the amount of physical I/O in the database.
Joins in the FROM Clause
You can read data from more than one database table in a single SELECT statement by using inner or left outer joins in the FROM clause.
The disadvantage of using joins is that redundant data is read from the hierarchically-superior table if there is a 1:N relationship between the outer and inner tables. This can considerably increase the amount of data transferred from the database to the application server. Therefore, when you program a join, you should ensure that the SELECT clause contains a list of only the columns that you really need. Furthermore, joins bypass the table buffer and read directly from the database. For this reason, you should use an ABAP Dictionary view instead of a join if you only want to read the data.
The runtime of a join statement is heavily dependent on the database optimizer, especially when it contains more than two database tables. However, joins are nearly always quicker than using nested SELECT statements.
Subqueries in the WHERE and HAVING Clauses
Another way of accessing more than one database table in the same Open SQL statement is to use subqueries in the WHERE or HAVING clause. The data from a subquery is not transferred to the application server. Instead, it is used to evaluate conditions in the database system. This is a simple and effective way of programming complex database operations.
Using Internal Tables
It is also possible to avoid nested SELECT loops by placing the selection from the outer loop in an internal table and then running the inner selection once only using the FOR ALL ENTRIES addition. This technique stems from the time before joins were allowed in the FROM clause. On the other hand, it does prevent redundant data from being transferred from the database.
Using a Cursor to Read Data
A further method is to decouple the INTO clause from the SELECT statement by opening a cursor using OPEN CURSOR and reading data line by line using FETCH NEXT CURSOR. You must open a new cursor for each nested loop. In this case, you must ensure yourself that the correct lines are read from the database tables in the correct order. This usually requires a foreign key relationship between the database tables, and that they are sorted by the foreign key. Minimize the Search Overhead
You minimize the size of the result set by using the WHERE and HAVING clauses. To increase the efficiency of these clauses, you should formulate them to fit with the database table indexes.
Database Indexes
Indexes speed up data selection from the database. They consist of selected fields of a table, of which a copy is then made in sorted order. If you specify the index fields correctly in a condition in the WHERE or HAVING clause, the system only searches part of the index (index range scan).
The primary index is always created automatically in the R/3 System. It consists of the primary key fields of the database table. This means that for each combination of fields in the index, there is a maximum of one line in the table. This kind of index is also known as UNIQUE.
If you cannot use the primary index to determine the result set because, for example, none of the primary index fields occur in the WHERE or HAVING clause, the system searches through the entire table (full table scan). For this case, you can create secondary indexes, which can restrict the number of table entries searched to form the result set.
You specify the fields of secondary indexes using the ABAP Dictionary. You can also determine whether the index is unique or not. However, you should not create secondary indexes to cover all possible combinations of fields.
Only create one if you select data by fields that are not contained in another index, and the performance is very poor. Furthermore, you should only create secondary indexes for database tables from which you mainly read, since indexes have to be updated each time the database table is changed. As a rule, secondary indexes should not contain more than four fields, and you should not have more than five indexes for a single database table.
If a table has more than five indexes, you run the risk of the optimizer choosing the wrong one for a particular operation. For this reason, you should avoid indexes with overlapping contents.
Secondary indexes should contain columns that you use frequently in a selection, and that are as highly selective as possible. The fewer table entries that can be selected by a certain column, the higher that columns selectivity. Place the most selective fields at the beginning of the index. Your secondary index should be so selective that each index entry corresponds to at most five percent of the table entries. If this is not the case, it is not worth creating the index. You should also avoid creating indexes for fields that are not always filled, where their value is initial for most entries in the table.
If all of the columns in the SELECT clause are contained in the index, the system does not have to search the actual table data after reading from the index. If you have a SELECT clause with very few columns, you can improve performance dramatically by including these columns in a secondary index.
Formulating Conditions for Indexes
You should bear in mind the following when formulating conditions for the WHERE and HAVING clauses so that the system can use a database index and does not have to use a full table scan.
Check for Equality and Link Using AND
The database index search is particularly efficient if you check all index fields for equality (= or EQ) and link the expressions using AND.
Use Positive Conditions
The database system only supports queries that describe the result in positive terms, for example, EQ or LIKE. It does not support negative expressions like NE or NOT LIKE.
If possible, avoid using the NOT operator in the WHERE clause, because it is not supported by database indexes; invert the logical expression instead.
Using OR
The optimizer usually stops working when an OR expression occurs in the condition. This means that the columns checked using OR are not included in the index search. An exception to this are OR expressions at the outside of conditions. You should try to reformulate conditions that apply OR expressions to columns relevant to the index, for example, into an IN condition.
Using Part of the Index
If you construct an index from several columns, the system can still use it even if you only specify a few of the columns in a condition. However, in this case, the sequence of the columns in the index is important. A column can only be used in the index search if all of the columns before it in the index definition have also been specified in the condition.
Checking for Null Values
The IS NULL condition can cause problems with indexes. Some database systems do not store null values in the index structure. Consequently, this field cannot be used in the index.
Avoid Complex Conditions
Avoid complex conditions, since the statements have to be broken down into their individual components by the database system.
Reduce the Database Load
Unlike application servers and presentation servers, there is only one database server in your system. You should therefore aim to reduce the database load as much as possible. You can use the following methods:
Buffer Tables on the Application Server
You can considerably reduce the time required to access data by buffering it in the application server table buffer. Reading a single entry from table T001 can take between 8 and 600 milliseconds, while reading it from the table buffer takes 0.2 - 1 milliseconds.
Whether a table can be buffered or not depends its technical attributes in the ABAP Dictionary. There are three buffering types:
Resident buffering (100%) The first time the table is accessed, its entire contents are loaded in the table buffer.
Generic buffering In this case, you need to specify a generic key (some of the key fields) in the technical settings of the table in the ABAP Dictionary. The table contents are then divided into generic areas. When you access data with one of the generic keys, the whole generic area is loaded into the table buffer. Client-specific tables are often buffered generically by client.
Partial buffering (single entry) Only single entries are read from the database and stored in the table buffer.
When you read from buffered tables, the following happens:
1. An ABAP program requests data from a buffered table.
2. The ABAP processor interprets the Open SQL statement. If the table is defined as a buffered table in the ABAP Dictionary, the ABAP processor checks in the local buffer on the application server to see if the table (or part of it) has already been buffered.
3. If the table has not yet been buffered, the request is passed on to the database. If the data exists in the buffer, it is sent to the program.
4. The database server passes the data to the application server, which places it in the table buffer.
5. The data is passed to the program.
When you change a buffered table, the following happens:
1. The database table is changed and the buffer on the application server is updated. The database interface logs the update statement in the table DDLOG. If the system has more than one application server, the buffer on the other servers is not updated at once.
2. All application servers periodically read the contents of table DDLOG, and delete the corresponding contents from their buffers where necessary. The granularity depends on the buffering type. The table buffers in a distributed system are generally synchronized every 60 seconds (parameter: rsdisp/bufreftime).
3. Within this period, users on non-synchronized application servers will read old data. The data is not recognized as obsolete until the next buffer synchronization. The next time it is accessed, it is re-read from the database.
You should buffer the following types of tables:
Tables that are read very frequently
Tables that are changed very infrequently
Relatively small tables (few lines, few columns, or short columns)
Tables where delayed update is acceptable.
Once you have buffered a table, take care not to use any Open SQL statements that bypass the buffer.
The SELECT statement bypasses the buffer when you use any of the following:
The BYPASSING BUFFER addition in the FROM clause
The DISTINCT addition in the SELECT clause
Aggregate expressions in the SELECT clause
Joins in the FROM clause
The IS NULL condition in the WHERE clause
Subqueries in the WHERE clause
The ORDER BY clause
The GROUP BY clause
The FOR UPDATE addition
Furthermore, all Native SQL statements bypass the buffer.
Avoid Reading Data Repeatedly
If you avoid reading the same data repeatedly, you both reduce the number of database accesses and reduce the load on the database. Furthermore, a "dirty read" may occur with database tables other than Oracle. This means that the second time you read data from a database table, it may be different from the data read the first time. To ensure that the data in your program is consistent, you should read it once only and then store it in an internal table.
Sort Data in Your ABAP Programs
The ORDER BY clause in the SELECT statement is not necessarily optimized by the database system or executed with the correct index. This can result in increased runtime costs. You should only use ORDER BY if the database sort uses the same index with which the table is read. To find out which index the system uses, use SQL Trace in the ABAP Workbench Performance Trace. If the indexes are not the same, it is more efficient to read the data into an internal table or extract and sort it in the ABAP program using the SORT statement.
Use Logical Databases
SAP supplies logical databases for all applications. A logical database is an ABAP program that decouples Open SQL statements from application programs. They are optimized for the best possible database performance. However, it is important that you use the right logical database. The hierarchy of the data you want to read must reflect the structure of the logical database, otherwise, they can have a negative effect on performance. For example, if you want to read data from a table right at the bottom of the hierarchy of the logical database, it has to read at least the key fields of all tables above it in the hierarchy. In this case, it is more efficient to use a SELECT statement.
Work Processes
Work processes execute the individual dialog steps in R/3 applications. The next two sections describe firstly the structure of a work process, and secondly the different types of work process in the R/3 System.
Structure of a Work Process
Work processes execute the dialog steps of application programs. They are components of an application server. The following diagram shows the components of a work process:
Each work process contains two software processors and a database interface.
Screen Processor
In R/3 application programming, there is a difference between user interaction and processing logic. From a programming point of view, user interaction is controlled by screens. As well as the actual input mask, a screen also consists of flow logic. The screen flow logic controls a large part of the user interaction. The R/3 Basis system contains a special language for programming screen flow logic. The screen processor executes the screen flow logic. Via the dispatcher, it takes over the responsibility for communication between the work process and the SAPgui, calls modules in the flow logic, and ensures that the field contents are transferred from the screen to the flow logic.
ABAP Processor
The actual processing logic of an application program is written in ABAP - SAPs own programming language. The ABAP processor executes the processing logic of the application program, and communicates with the database interface. The screen processor tells the ABAP processor which module of the screen flow logic should be processed next. The following screen illustrates the interaction between the screen and the ABAP processors when an application program is running.
Database Interface
The database interface provides the following services:
Establishing and terminating connections between the work process and the database.
Access to database tables
Access to R/3 Repository objects (ABAP programs, screens and so on)
Access to catalog information (ABAP Dictionary)
Controlling transactions (commit and rollback handling)
Table buffer administration on the application server.
The following diagram shows the individual components of the database interface:
The diagram shows that there are two different ways of accessing databases: Open SQL and Native SQL.
Open SQL statements are a subset of Standard SQL that is fully integrated in ABAP. They allow you to access data irrespective of the database system that the R/3 installation is using. Open SQL consists of the Data Manipulation Language (DML) part of Standard SQL; in other words, it allows you to read (SELECT) and change (INSERT, UPDATE, DELETE) data. The tasks of the Data Definition Language (DDL) and Data Control Language (DCL) parts of Standard SQL are performed in the R/3 System by the ABAP Dictionary and the authorization system. These provide a unified range of functions, irrespective of database, and also contain functions beyond those offered by the various database systems.
Open SQL also goes beyond Standard SQL to provide statements that, in conjunction with other ABAP constructions, can simplify or speed up database access. It also allows you to buffer certain tables on the application server, saving excessive database access. In this case, the database interface is responsible for comparing the buffer with the database. Buffers are partly stored in the working memory of the current work process, and partly in the shared memory for all work processes on an application server. Where an R/3 System is distributed across more than one application server, the data in the various buffers is synchronized at set intervals by the buffer management. When buffering the database, you must remember that data in the buffer is not always up to date. For this reason, you should only use the buffer for data which does not often change.
Native SQL is only loosely integrated into ABAP, and allows access to all of the functions contained in the programming interface of the respective database system. Unlike Open SQL statements, Native SQL statements are not checked and converted, but instead are sent directly to the database system. Programs that use Native SQL are specific to the database system for which they were written. R/3 applications contain as little Native SQL as possible. In fact, it is only used in a few Basis components (for example, to create or change table definitions in the ABAP Dictionary).
The database-dependent layer in the diagram serves to hide the differences between database systems from the rest of the database interface. You choose the appropriate layer when you install the Basis system. Thanks to the standardization of SQL, the differences in the syntax of statements are very slight. However, the semantics and behavior of the statements have not been fully standardized, and the differences in these areas can be greater. When you use Native SQL, the function of the database-dependent layer is minimal.
Types of Work Process
Although all work processes contain the components described above, they can still be divided into different types. The type of a work process determines the kind of task for which it is responsible in the application server. It does not specify a particular set of technical attributes. The individual tasks are distributed to the work processes by the dispatcher.
Before you start your R/3 System, you determine how many work processes it will have, and what their types will be. The dispatcher starts the work processes and only assigns them tasks that correspond to their type. This means that you can distribute work process types to optimize the use of the resources on your application servers.
The following diagram shows again the structure of an application server, but this time, includes the various possible work process types:
The various work processes are described briefly below. Other parts of this documentation describe the individual components of the application server and the R/3 System in more detail.
Dialog Work Process
Dialog work processes deal with requests from an active user to execute dialog steps.
Update Work Process
Update work processes execute database update requests. Update requests are part of an SAP LUW that bundle the database operations resulting from the dialog in a database LUW for processing in the background.
Background Work Process
Background work processes process programs that can be executed without user interaction (background jobs).
Enqueue Work Process
The enqueue work process administers a lock table in the shared memory area. The lock table contains the logical database locks for the R/3 System and is an important part of the SAP LUW concept. In an R/3 System, you may only have one lock table. You may therefore also only have one application server with enqueue work processes.
Spool Work Process
The spool work process passes sequential datasets to a printer or to optical archiving. Each application server may contain several spool work process.
The services offered by an application server are determined by the types of its work processes. One application server may, of course, have more than one function. For example, it may be both a dialog server and the enqueue server, if it has several dialog work processes and an enqueue work process.
You can use the system administration functions to switch a work process between dialog and background modes while the system is still running. This allows you, for example, to switch an R/3 System between day and night operation, where you have more dialog than background work processes during the day, and the other way around during the night.
ABAP Application Server
R/3 programs run on application servers. They are an important component of the R/3 System. The following sections describe application servers in more detail.
Structure of an ABAP Application Server
The application layer of an R/3 System is made up of the application servers and the message server. Application programs in an R/3 System are run on application servers. The application servers communicate with the presentation components, the database, and also with each other, using the message server.
The following diagram shows the structure of an application server:
The individual components are:
Work Processes
An application server contains work processes, which are components that can run an application. Work processes are components that are able to execute an application (that is, one dialog step each). Each work process is linked to a memory area containing the context of the application being run. The context contains the current data for the application program. This needs to be available in each dialog step. Further information about the different types of work process is contained later on in this documentation.
Dispatcher
Each application server contains a dispatcher. The dispatcher is the link between the work processes and the users logged onto the application server. Its task is to receive requests for dialog steps from the SAP GUI and direct them to a free work process. In the same way, it directs screen output resulting from the dialog step back to the appropriate user.
Gateway
Each application server contains a gateway. This is the interface for the R/3 communication protocols (RFC, CPI/C). It can communicate with other application servers in the same R/3 System, with other R/3 Systems, with R/2 Systems, or with non-SAP systems.
The application server structure as described here aids the performance and scalability of the entire R/3 System. The fixed number of work processes and dispatching of dialog steps leads to optimal memory use, since it means that certain components and the memory areas of a work process are application-independent and reusable. The fact that the individual work processes work independently makes them suitable for a multi-processor architecture. The methods used in the dispatcher to distribute tasks to work processes are discussed more closely in the section Dispatching Dialog Steps.
Shared Memory
All of the work processes on an application server use a common main memory area called shared memory to save contexts or to buffer constant data locally.
The resources that all work processes use (such as programs and table contents) are contained in shared memory. Memory management in the R/3 System ensures that the work processes always address the correct context, that is the data relevant to the current state of the program that is running. A mapping process projects the required context for a dialog step from shared memory into the address of the relevant work process. This reduces the actual copying to a minimum.
Local buffering of data in the shared memory of the application server reduces the number of database reads required. This reduces access times for application programs considerably. For optimal use of the buffer, you can concentrate individual applications (financial accounting, logistics, human resources) into separate application server groups.
Database Connection
When you start up an R/3 System, each application server registers its work processes with the database layer, and receives a single dedicated channel for each. While the system is running, each work process is a user (client) of the database system (server). You cannot change the work process registration while the system is running. Neither can you reassign a database channel from one work process to another. For this reason, a work process can only make database changes within a single database logical unit of work (LUW). A database LUW is an inseparable sequence of database operations. This has important consequences for the programming model explained below.
Dispatching Dialog Steps
The number of users logged onto an application server is often many times greater than the number of available work processes. Furthermore, it is not restricted by the R/3 system architecture. Furthermore, each user can run several applications at once. The dispatcher has the important task of distributing all dialog steps among the work processes on the application server.
The following diagram is an example of how this might happen:
1. The dispatcher receives the request to execute a dialog step from user 1 and directs it to work process 1, which happens to be free. The work process addresses the context of the application program (in shared memory) and executes the dialog step. It then becomes free again.
2. The dispatcher receives the request to execute a dialog step from user 2 and directs it to work process 1, which is now free again. The work process executes the dialog step as in step 1.
3. While work process 1 is still working, the dispatcher receives a further request from user 1 and directs it to work process 2, which is free.
4. After work processes 1 and 2 have finished processing their dialog steps, the dispatcher receives another request from user 1 and directs it to work process 1, which is free again.
5. While work process 1 is still working, the dispatcher receives a further request from user 2 and directs it to work process 2, which is free.
From this example, we can see that:
A dialog step from a program is assigned to a single work process for execution.
The individual dialog steps of a program can be executed on different work processes, and the program context must be addressed for each new work process.
A work process can execute dialog steps of different programs from different users.
The example does not show that the dispatcher tries to distribute the requests to the work processes such that the same work process is used as often as possible for the successive dialog steps in an application. This is useful, since it saves the program context having to be addressed each time a dialog step is executed.
Dispatching and the Programming Model
The separation of application and presentation layer made it necessary to split up application programs into dialog steps. This, and the fact that dialog steps are dispatched to individual work processes, has had important consequences for the programming model.
As mentioned above, a work process can only make database changes within a single database logical unit of work (LUW). A database LUW is an inseparable sequence of database operations. The contents of the database must be consistent at its beginning and end. The beginning and end of a database LUW are defined by a commit command to the database system (database commit). During a database LUW, that is, between two database commits, the database system itself ensures consistency within the database. In other words, it takes over tasks such as locking database entries while they are being edited, or restoring the old data (rollback) if a step terminates in an error.
A typical SAP application program extends over several screens and the corresponding dialog steps. The user requests database changes on the individual screens that should lead to the database being consistent once the screens have all been processed. However, the individual dialog steps run on different work processes, and a single work process can process dialog steps from other applications. It is clear that two or more independent applications whose dialog steps happen to be processed on the same work process cannot be allowed to work with the same database LUW.
Consequently, a work process must open a separate database LUW for each dialog step. The work process sends a commit command (database commit) to the database at the end of each dialog step in which it makes database changes. These commit commands are called implicit database commits, since they are not explicitly written into the application program.
These implicit database commits mean that a database LUW can be kept open for a maximum of one dialog step. This leads to a considerable reduction in database load, serialization, and deadlocks, and enables a large number of users to use the same system.
However, the question now arises of how this method (1 dialog step = 1 database LUW) can be reconciled with the demand to make commits and rollbacks dependent on the logical flow of the application program instead of the technical distribution of dialog steps. Database update requests that depend on one another form logical units in the program that extend over more than one dialog step. The database changes associated with these logical units must be executed together and must also be able to be undone together.
The SAP programming model contains a series of bundling techniques that allow you to group database updates together in logical units. The section of an R/3 application program that bundles a set of logically-associated database operations is called an SAP LUW. Unlike a database LUW, a SAP LUW includes all of the dialog steps in a logical unit, including the database update.
Happy Reading...
shibu

AppleScript Error in Creating a New Contact (Help)

I wrote this script w/ variable but I am getting an error on the make contact part of the script. What am I missing?
--User Inputs to get Client details
display dialog "Enter a Name, please:
Please enter Contact's First Name:" default answer "First Name"
set ClientName to text returned of result
display dialog "Please Enter Contact's Last Name:
Please enter Contact's Last Name:" default answer "Last Name"
set LastClientName to text returned of result
display dialog "Please enter Contact's email address:
Please enter Contact's Email:" default answer "[email protected]"
set lastemail to text returned of result
--Add to Outlook
tell application "Contacts"
activate
make new card with properties {first name:ClientName, last name:LastClientName, email:lastemail}
quit
end tell

I now have this and it is working except on Running it I get a Result: Missing value but it works.
make new email at end of every email of person id "0F4D2342-BD28-4D75-8F20-0EFF4B280A69:ABPerson" with properties {label:"Work", value:"[email protected]"}
--> email 1 of person id "0F4D2342-BD28-4D75-8F20-0EFF4B280A69:ABPerson"
save current application
--> missing value
end tell
Result:
missing value
Here is new script.
--User Inputs to get Client details
display dialog "Enter a Name, please:
Please enter Contact's First Name:" default answer "First Name"
set ClientName to text returned of result
display dialog "Please Enter Contact's Last Name:
Please enter Contact's Last Name:" default answer "Last Name"
set LastClientName to text returned of result
display dialog "Please enter Contact's email address:
Please enter Contact's Email:" default answer "[email protected]"
set lastemail to text returned of result
--Add to Address Book
tell application "Contacts"
    set thePerson to make new person with properties {first name:ClientName, last name:LastClientName}
    tell thePerson
        make new email at end of emails of thePerson with properties {label:"Work", value:lastemail}
    end tell
    save
end tell

My FinalCut Wish List

My Valentine's gift to Apple's FCP feedback site was the following Wish List (which I figured I'd also post here just for the heck of it).
Some of these feature requests may only apply to my particular -- some might say peculiar -- workflow, but I suspect a few of them might strike a responsive chord with other FinalCutters. (Whether any of them are on Apple's Do List is of course another question.)
(using FCP 5.1.2 under OX X 10.4.8)
One User's Final Cut Pro Wish List:
(sent to Apple's FinalCut Feedback site, Feb. 14/07)
An Undo History.
If Final Cut can "remember", say, 10 levels of Undos (or whatever that user pref is set to), then why can't it display an Undo History palette, with brief descriptions of each Undoable action - a la Adobe Photoshop?
The fact that even FCP's Edit Menu just says "Undo" and "Redo" -- with no attempt to even say what it is you're about to Undo or Redo, is really pretty sad.
A "Learning Mode".
An easy-to-turn on or off mode in which more detailed Hint Dialogs (like Tool Tips on steroids) appear onscreen -- with definitions, suggested uses, possible workflows, even links to the reference manual. All very context-sensitive, and all designed to hold-your-hand and help you understand a new area of the app.
I'm not the least bit too proud to say I would use that mode a LOT (at least when no-one else was looking!).
Option to Auto Scroll the Timeline while in Play.
Likewise for an audio waveform displayed in the Viewer. Is this feature really that hard to implement?
And while we're on the subject of things people have been requesting for a long time now, let's add another chorus for...
Robust, Reliable, User-Friendly and Intuitive Media Management.
Auto Pitch-Correction Option when doing Speed adjustments.
This seems like a no-brainer: just like the "Frame Blending, yes-or-no" checkbox when you Cmd-J to do a speed adjustment, there should be a "Pitch Correct Audio?" checkbox right in the same dialog. It's really very embarrassing that FinalCut still refuses to do this audio function. This is NOT something you should have to transfer into a whole 'nother app to do, or have to apply a special AU Pitch filter to the clip just to try and get it to sound normal again.
which reminds me...
How about a Round-Tripping to Soundtrack workflow that actually works?
(I've had two Apple Store "Creatives" unable to get it to work properly, and several FCP veterans advise me to just avoid that workflow altogether, at least until it's thoroughly "deflake-ified")
Better Labelling Options.
Would love a way to apply text labels (and color codes) to Timeline Tracks (in the left-side info pane). For example, so I can add the label "Dialog" to tracks A1 and A2, "Narration" to tracks A3 and A4, "Music" to tracks A5 and A6, etc, -- and then maybe even color-code groups of tracks for quick reference.
And how about a much clearer, user-definable indicator to highlight which window (Browser/Viewer/Timeline) is currently active -- a selectable color for the active title bar (or even framing the entire window) -- instead of the current medium-grey vs. light-grey all against a grey background (not the most dynamic visual cue).
And just as I can color-code Browser icons, I would also like to be able to color-code Timeline tabs -- AND change their left-to-right order simply by dragging.
Miscellaneous
A few quirky little things I'd like to be able to at least try:
An Option/Preference for the Timeline to be auto-selected when you drag a clip onto it.
An Option to keep a Timeline Zoom-In centered on the playhead position, rather than on the start of a selected clip.
A Poster Frame option for thumbnails in the Timeline (especially if one's been set in the Browser; as opposed to the current first-frame-or-nothing default)
I'd like the ability to Link multiple video items to a single audio item in Timeline, and create a merged clip from that selection (using the audio clip as the "anchor")
And why does the "Delete All markers" command only delete markers from selected clips where the playhead happens to be -- I still can't find a way to delete clip markers from ALL selected clips, regardless of where the playhead is.
I hope that most of these features have already been incorporated into the next release of FinalCut -- and if not, that you'll give serious consideration to implementing them as soon as possible. Your users will thank you.
John Bertram
Toronto

Hi John
This ones a User to User forum, no Apple reps here
Indeed -- hence the opening line of my post:
"My Valentine's gift to Apple's FCP feedback site was the following Wish List" and
"One User's Final Cut Pro Wish List:
(sent to Apple's FinalCut Feedback site, Feb. 14/07)"
Also why I didn't post the letter as a Question actively seeking help. It's simply offered in the spirit of a Mike-Meyers-as-Linda-Richmond "talk amongst yourselves" moment ("I'll give you a topic: Final Cut is never final, but often cutting. Discuss.")
Nevertheless, thanks for the feedback. Further to which...
A "Learning Mode"
we are our own learning mode right here!
And an invaluable one, to be sure. I just feel that FinalCut could still build in a few extra "stairs" to make its learning curve a bit easier to climb -- stairs which can of course be skipped entirely by the more experienced users.
An Option to keep a Timeline Zoom-In centered on
the playhead position, rather than on the start of a
selected clip.
If there is no selected clip then the zoom centers on
the playhead. If there is a selected clip then the
zoom centers on the selection. Or just use the zoom
tool (z) and zoom wherever you like. They pretty
much have this one covered, its just a case of using
the right tool at the right time, not just adding
more tools/options.
This was a small one -- and perhaps one I shouldn't have bothered including. I just personally wouldn't mind a User Pref to the affect of "Timeline zoom (when using Option+=) always centers on Playhead" (the default for which would be Off, but which I in my own world of weirdness would turn On).
I'd like the ability to Link multiple video items to
a single audio item in Timeline, and create a merged
clip from that selection (using the audio clip as the
"anchor")
Thats called "Nesting". Check out Sequence menu >
Nest Items...
I've actually been having to do a fair bit of Nesting, often of just individual clips -- to the extent that I now have a Nest Item button in my Timeline button bar.*
What I was looking for here is something a bit different: really just the mirror image of when you have several audio clips Linked to a single video "anchor" clip. It would be in situations where I'm using a continuous chunk of audio to which I sync up bits of short video clips. Some of those video clips are from that same (call it the master) take, while others are from different takes in which the actor spoke a phrase in the same rhythm. In certain situations, I just want to be able to Cmd-L Link ALL those video clips on the Timeline to the one Audio clip, while at the same time not linking other interspersed video clips which are simply cutaways. But I still want all the clips to remain separate and un-nested.
* Don't know if that explanation makes any sense, but as to the Nesting issue itself: Is there any way to force a Filter effect to be applied AFTER a Motion tab effect? I'm asking because I have a sequence to which I'm applying a Widescreen Matte filter to each clip. (The filter has to be applied to each clip individually to allow for vertical repositioning using the Offset control.) But some of the clips also require a Scale adjustment under the motion tab, increasing the image size to 105 or 110%, for example. In these cases, I find I have to apply the Scale change, then Nest the Clip, THEN apply the Widescreen Matte filter to the nested clip. If I try to do both in the original unnested clip, the Widescreen matte gets applied first, then that entire matted image is Scaled to whatever % I've chosen -- and that obviously changes the apparent size of the matte onscreen.
While you can easily change the order in which different Filters get applied to a clip, I've yet to find a way to change the order in which Filter effects vs. Motion tab effects are applied. Maybe I'll post this issue as an actual Question in a new thread.
Meantime, I hope that clarifies a couple of the quirkier items on my FinalCut WIsh List.
Cheers,
John Bertram
Toronto

Severe error(s) occurred in phase PREP_INSTALL/SHDINST_OS Last error code set: Process H:\SUM\abap\exe/sapstartsrv.exe exited with -1

Hi Experts ,
Currently performing EHP7 upgrade I have faced error during the configuration phase , below attached was the error screenshot .
error logs shows the below :
Executing module 'PREP_INSTALL'.
Execution of PREPARE module "Installation" begins at 20140302202456
# Starting phase execution with maxpar = 6, scheduled: 14x'-'
CURRENTPHASE PREP_INSTALL/SHDINST_OS
...started at 20140302202456
# Using phase log file 'SHDINST_OS.LOG'.
..finished at 20140302202457 with status ABORTED.
# Error message set: 'Process H:\SUM\abap\exe/sapstartsrv.exe exited with -1, see 'H:\SUM\abap\log\SAPup.ECO' for details'
.begin dialog at 20140302202459
SHDINST_OS log :
1 ETQ399 Possibly the password for user ISNET\SAPServiceDEC entered in phase
1 ETQ399 INITPUT was wrong. You can reset it by calling 'SAPup set stdpar'.
1 ETQ399 Try to execute SAPSTARTSRV.EXE manually using the following syntax:
1 ETQ399 H:\SUM\abap\exe\sapstartsrv.exe -r
1 ETQ399 -p H:\SUM\abap\DEC\SYS\profile\START_DVEBMGS01_SAPECCDV -s DEC -n 01
1 ETQ399 -U ISNET\SAPServiceDEC -P <PASSWORD> -e ISNET\decadm
1 ETQ399 and check if the service SAPDEC_01 can be stopped and restarted.
1EETQ399 Last error code set is: Process H:\SUM\abap\exe/sapstartsrv.exe exited with -1, see 'H:\SUM\abap\log\SAPup.ECO' for details
1EETQ204 Upgrade phase "SHDINST_OS" aborted with severe errors ("20140302202457")
Kindly advice to fix

Hi Mohan,
Solution of your issue is already present in SHDINST_OS.LOG
Possibly the password for user ISNET\SAPServiceDEC entered in phase
1 ETQ399 INITPUT was wrong. You can reset it by calling 'SAPup set stdpar'.
1 ETQ399 Try to execute SAPSTARTSRV.EXE manually using the following syntax:
1 ETQ399 H:\SUM\abap\exe\sapstartsrv.exe -r
1 ETQ399 -p H:\SUM\abap\DEC\SYS\profile\START_DVEBMGS01_SAPECCDV -s DEC -n 01
1 ETQ399 -U ISNET\SAPServiceDEC -P <PASSWORD> -e ISNET\decadm
1 ETQ399 and check if the service SAPDEC_01 can be stopped and restarted.
Read the log carefully.Have you performed the above mentioned steps from SHDINST_OS.LOG file at your end.
Also just give a full restart your server,up all the required services & confirm the execution of the phase.
Thanks,
Gaurav

Problems running Flash Builder 4.6 profiler

Hello,
I have a problem running Flash Builder profiler. When I click "Profile" it starts my web application, but nothing else happens inside Flash Builder itself - no new data appears in Profiler perspective, Flash Builder itself doesn't show any sign of doing something.
My mm.cfg contains the next line: "PreloadSwf=C:/flash builder workspace/.metadata/.plugins/com.adobe.flash.profiler/11/ProfilerAgent.swf?host=localhost &port=9999"
Additional details:
OS: Windows 7
Flash Builder version: 4.6
Tested web browsers: Firefox, IE 8 - the same problem in both of them
Flash player versions: ActiveX/Plug-in Version:11.7.700.169
I made sure that ProfilerAgent.swf indeed exists in the location defined in mm.cfg. In addition, I tried to change port 9999 to other ports (both in mm.cfg and in Flash Builder). I also verified that the location of ProfilerAgent.swf appears in trusted locations of Flash Player.
I would be very grateful if someone could help me to solve this problem.
Thanks,
Valeria

R Grieve wrote:
This sounds like something has gone wrong during installation. CSAR and CSLIBS references should be set up automatically during installation.
There should also be no need to import the Flex SDKs as CS Extension Builder 2.0 ships with them included. It won't do any harm though having the CS Flex SDKs imported.
Can you detail how you installed CS Extension Builder 2.0, please and where you obtained it from?
Here are the installation instructions I would recommend starting from a clean FlashBuilder 4.6 instance:
To install Adobe Creative Suite Extension Builder, download the ZIP file and unzip it into a root location (SDKRoot).
Install Extension Builder in Eclipse with Flash Builder or Flash Builder Standalone:
In Eclipse, choose Help > Install New Software.
In the Install dialog, click Add.
In the Add Site dialog, click Local... to browse to the SDK root folder or enter the URL of the update site.
Name the site CS SDK and click OK to confirm the changes.
Select the new CS SDK site in the "Work with" field.
-- Select all the Adobe Creative Suite Extension Builder components.
-- Click Next to confirm the selection.
In the Install Details review dialog, click Next to confirm that you want to install all the components listed.
Accept the terms of license agreements and click Finish.
Re-start Eclipse as recommended.
I obtained it from Adobe and installed it using the Help > Install software option, but without unzipping it. Maybe that was it.
Now I've done a clean installation and it works perfect. I did it with administrator permissions, don't know if it has anything to do with it, but I read it somewhere and did so just in case!
Thanks a lot!

ADF FACES: jdeveloper hangs on opening a .jspx file

I may not have had this file open since updating to EA13, but I'm not positive. Upon trying to open the file (code below), jdeveloper hangs. It sucks down roughly 50% of the CPU and the memory footprint slowly grows (about 3 MB per minute). As of now, I've tried restarting jdeveloper and then opening the file, but the behavior is the same. I have let it run for nearly 15 minutes and it is still hung (to the point that the display is not redrawn when a window, such as the task manager, is closed after obscuring part of the jdeveloper window).
I'm running jdev version 10.1.3.0.2.223
ADF Faces EA13
On windows 2003 Server
Here's the code:
<?xml version='1.0' encoding='iso-8859-1'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.0"
xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html"
xmlns:af="http://xmlns.oracle.com/adf/faces/EA13"
xmlns:afh="http://xmlns.oracle.com/adf/faces/EA13/html"
xmlns:c="http://java.sun.com/jsp/jstl/core">
<jsp:directive.page contentType="text/html;charset=iso-8859-1"/>
<f:view>
<afh:html>
<afh:head title="Case Details">

<title>
Case Details
</title>
</afh:head>
<afh:script source="js/mwb_gecko.js" rendered="#{clientInfo.gecko}"/>
<afh:script source="js/mwb.js"/>
<afh:body>
<af:form>
<af:panelPage title="Case Details">
<f:facet name="messages">
<af:messages/>
</f:facet>
<f:facet name="brandingApp">
<af:panelGroup>
<af:outputFormatted value="MedCierge Workbench" styleClass="OraHeader"/>
<af:objectImage source="/images/pbs.gif"/>
</af:panelGroup>
</f:facet>
<f:facet name="brandingAppContextual">
<af:outputFormatted value="Flagship Healthcare Management, Inc."
styleUsage="inContextBranding"/>
</f:facet>
<f:facet name="menuGlobal">
<af:menuButtons>
<af:commandMenuItem text="Home" action="agenthome"/>
<af:commandMenuItem text="Logout" action="logout"/>
<af:commandMenuItem text="Help" action="help"/>
</af:menuButtons>
</f:facet>
<f:facet name="infoUser">
<af:outputText value="Logged in as #{sessionScope.agentName}"
styleClass="OraPageStampText"/>
</f:facet>
<f:facet name="actions">
<af:panelButtonBar>
<af:commandButton id="ReturnButton"
textAndAccessKey="&Return to #{pageFlowScope.caseReturnName}"
action="#{nav.returnFromFlow}"/>
</af:panelButtonBar>
</f:facet>
<f:facet name="appCopyright">
<af:outputText value="copyright facet"/>
</f:facet>
<f:facet name="appPrivacy">
<af:commandLink text="privacy facet" action="action.none" />
</f:facet>
<f:facet name="appAbout">
<af:commandLink text="about facet" action="action.none" />
</f:facet>
<af:panelGroup type="vertical">
<af:panelForm labelWidth="5%">
<af:panelLabelAndMessage label="Owner:">
<af:outputText value="#{pageFlowScope.case.owningAgentId}"
styleClass="OraFieldText"/>
<af:outputFormatted value=" [You own this case]"
styleClass="OraFieldText"
rendered="#{pageFlowScope.case.owningAgentId == sessionScope.agentId}"/>
<af:outputFormatted value=" [You do not own this case]"
styleClass="OraFieldText"
rendered="#{pageFlowScope.case.owningAgentId != sessionScope.agentId}"/>
</af:panelLabelAndMessage>
<af:inputText label="Case ID:" value="#{pageFlowScope.case.id}" columns="10"
readOnly="true" shortDesc="Unique ID for this case"/>
<af:inputText value="#{pageFlowScope.case.serviceType}" label="Service Type:"
columns="10" readOnly="true"
shortDesc="Service requested: 'referral' or 'emergency'"/>
<af:inputText value="#{pageFlowScope.case.openDate}" label="Opened:"
columns="10" readOnly="true" shortDesc="Date this case was opened">
<f:convertDateTime pattern="MM/dd/yy HH:mm"/>
</af:inputText>
<af:inputText value="#{pageFlowScope.case.closeDate}" label="Closed:"
columns="10" readOnly="true" shortDesc="Date this case was closed"
inlineStyle="{color: red}"
rendered="#{!(empty pageFlowScope.case.closeDate)}">
<f:convertDateTime pattern="MM/dd/yy HH:mm"/>
</af:inputText>
<af:inputText value="#{pageFlowScope.case.primaryRequest}" label="Primary Request:"
columns="80" readOnly="true"
shortDesc="Short summary of the member's request"/>
<af:inputText value="#{pageFlowScope.case.appointmentPreferences}"
label="Appt. Preferences:" columns="80" readOnly="true"
shortDesc="Member's preferences on appointment times"/>
<af:inputText value="#{pageFlowScope.case.callbackData}" label="Call Back Data:"
columns="40" readOnly="true"
shortDesc="Phone/email to use for calling member back"/>
</af:panelForm>
<af:panelGroup type="vertical">
<af:forEach items="#{pageFlowScope.case.activitiesByDate}" var="act">
<af:objectSpacer height="10" width="0"/>
<af:objectSeparator/>
<af:outputFormatted value="#{act.date}" inlineStyle="{background-color:#cccc99}"/>
<af:objectSpacer height="5" width="1"/>
<af:panelGroup type="horizontal">
<af:panelForm>
<af:inputText label="ID:" value="#{act.id}" readOnly="true"/>
<af:inputText label="Type:" value="#{act.type}" readOnly="true"/>
<af:inputText label="MedCierge:" value="#{act.agentId}" readOnly="true"/>
</af:panelForm>
<af:objectSpacer width="5" height="1"/>
<af:inputText rows="4" readOnly="true" columns="80" value="#{act.notes}"/>
</af:panelGroup>

<af:objectSpacer height="10" width=""/>
<af:panelGroup rendered="#{act.type=='ibcall'}">
<af:commandButton text="Show Call Details" action="dialog:showCall"
partialSubmit="true" rendered="#{!(empty act.call)}"
windowHeight="500" windowWidth="750">
<af:setActionListener from="#{act.call}"
to="#{pageFlowScope.call}"/>
</af:commandButton>
</af:panelGroup>

<af:panelGroup rendered="#{act.type=='ibemail'}">
<af:outputText value="Inbound email #{act.type}"/>
</af:panelGroup>

<af:panelGroup rendered="#{act.type=='obcall'}">
<af:outputText value="Outbound Call #{act.type}"/>
</af:panelGroup>

<af:panelGroup rendered="#{act.type=='obemail'}">
<af:outputText value="Outbound email #{act.type}"/>
</af:panelGroup>
</af:forEach>
</af:panelGroup>
</af:panelGroup>
</af:panelPage>
</af:form>
</afh:body>
</afh:html>
</f:view>
</jsp:root>

Helo there,
I am having exactly the same problem, everytime I include af:forEach tag inside the af:selectOneChoice for example, preview of JSP is not shown and whole developer hangs, in task manager I can see 100% CPU occupation by JDeveloper.
But the code itself is ok, if I run the page while editor is in Source mode Page is properly shown in browser, but when I change editor mode to Design it hangs.
I am using Faces EA17 and JDeveloper 10.1.3
Does anybody else face the same issue?
ferdo

Hp 6110 all-in-one always prints in color on Windows 8

I would like to print some color documents in grayscale. But I am finding that no matter what settings I use in the Print dialog panel, my documents always come out in color. I am in Windows 8.1. For example, in Microsoft Word, if you go to File->Print, the Settings list contains options for which pages to print, one-sided or two-sided, collated, etc., but there is nothing for color vs. grayscale. So, if you then click a "Printer Properties" link, you get the detailed 6110 dialog panel with multiple tabs containing the full range of printer options. Within that, if you select the "Color" tab, you can check the "Print in Grayscale" box. Click "OK" to close the detailed printer dialog, which brings you back to the Microsoft Word printer dialog, where you can then click "Print". Document still comes out in color. I have verified a similar behavior when priting color PDF documents - there is no way to make them come out in grayscale.
I suspect the driver is also not respecting my specification to use "Fast Nornal" print quality.
So, a very clever strategy for HP to sell more ink! Can you please provide a fix?
Thanks

Hi @UsedToWorkInHPL,
Welcome to the HP Forums!
I understand that your HP Officejet 6110 all-in-one always prints in color on Windows 8. I am happy to look into this for you!
According to your printer's specifications found at this website, Printer Specifications for HP Officejet 6100 Printer Series. This printer is only supported for these Operating Systems: Windows 98, Windows 98 SE, Windows 2000, Windows Me, Microsoft(R), Windows XP.
There is no full feature software and drivers for Windows 8.1 for this printer.
One option to try and get around this, is to assign an alternate driver, please see this post, How to Assign Alternate Print Drivers in Different Versions of Windows, by @Shane_R.
Otherwise, I would recommend to please call our phone support at 800-474-6836 for your upgrade options to a printer that has the software and drivers available for Windows 8.1. If you live outside the US/Canada Region, please click the link below to get the support number for your region. Country-language selector.
Hope this information helps, and have a great day!
RnRMusicMan
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" to say “Thanks” for helping!

Cant export worksheet when connected to MS SQL Server 2000

SQL Developer version: 1.5.1
Hello,
I have a connection to an SQL Server 2000 database. I can select data with an "order by" clause but I receive an error when I attempt to do an "Export --> xls" on the worksheet data. I dont think this was a problem prior to SQL Developer 1.5.
No export error occurs if the "order by" cluase is removed.
Here is an example of a select stmt that generates the error.
select LastName, FirstName, EmployeeID
from northwind.dbo.employees
order by LastName, FirstName
Here are the error details:
First dialog box error text: The ORDER BY clause is invalid in views, inline functions, derived tables, and subqueries, unless TOP is also specified.
Second dialog box error text (after clicking Details button):
java.lang.NullPointerException
 at oracle.dbtools.raptor.dialogs.export.ColumnPanel.addColumnsToTree(ColumnPanel.java:85)
 at oracle.dbtools.raptor.dialogs.export.ColumnPanel.showPanel(ColumnPanel.java:61)
 at oracle.dbtools.raptor.dialogs.export.ColumnPanel.<init>(ColumnPanel.java:45)
 at oracle.dbtools.raptor.dialogs.actions.TableExportAction.showPanels(TableExportAction.java:297)
 at oracle.dbtools.raptor.dialogs.actions.TableExportAction.launchDlg(TableExportAction.java:197)
 at oracle.dbtools.raptor.format.ui.ExportContextMenuListener$1.actionPerformed(ExportContextMenuListener.java:137)
 at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
 at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
 at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
 at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
 at javax.swing.AbstractButton.doClick(AbstractButton.java:302)
 at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1000)
 at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1041)
 at java.awt.Component.processMouseEvent(Component.java:5488)
 at javax.swing.JComponent.processMouseEvent(JComponent.java:3126)
 at java.awt.Component.processEvent(Component.java:5253)
 at java.awt.Container.processEvent(Container.java:1966)
 at java.awt.Component.dispatchEventImpl(Component.java:3955)
 at java.awt.Container.dispatchEventImpl(Container.java:2024)
 at java.awt.Component.dispatchEvent(Component.java:3803)
 at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
 at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
 at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
 at java.awt.Container.dispatchEventImpl(Container.java:2010)
 at java.awt.Window.dispatchEventImpl(Window.java:1774)
 at java.awt.Component.dispatchEvent(Component.java:3803)
 at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
 at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
 at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
The table selected from is not a view, inline function, derived table, or subquery (as the error suggests). I can work around the problem by adding "TOP nnnn" to the select statement but this shouldn't be required.
Any suggestions?
Thanks.

I confirmed that this is not a problem in SQL Developer 1.2.1.32.13. It started with 1.5. In 1.5.1.5540 I can successfully run the query and see the output in the Results tab. Only the Export has the error.

Problems during execution of signed JARs applet...

Hi Everyone,
I noticed that AppletViewer used for development allows a wider range of operation not permitted during the execution in browser of a signed JAR.
I would be interested to know if this is caused because I am using a not real certificate (generated for testing). Anyone with a real certificate may tell me if for example URLClassLoader works well with jar applet signed with his real certificate?
Thanks, bye

Thanks, you confirm what I was not anymore able to verify in my browser :)
In fact the very first time I launched my applet in browser, the browser was showing a detailed message dialog pane complaining the untrustable certificate and restricted access privileges, so I thought to accept untrusted certificate as default and I tried to set up some options in security panel of the browser to trust untrusted certificate. Consequentely I was receiving only the untrusted certificate warning without any restriction message warning.
I understood that applets signed with untrusted certificates gives some more privilege than applet not signed, but evidently the security level of untrusted certificate does not give all total priviliges that trusted certificate does.

Auto-start services not running :Shell Hardware Detection in my Health Reports

Recently I've setup up Windows Server 2012 Essentials on my Custom-made Box. All is going well so far except that i have a warning in my generated Health Report such as
Auto-start Services Not Running Shell
Hardware Detection.
I had checked My Services and found out that this particular service is scheduled to start Automatically and it is always started...
Any Advice what might be the problem?

Susan, can you still see the Connect bug? What Product/Program is it under in Connect? I can't see it but I might not be a member of the correct group.
From http://technet.microsoft.com/en-us/library/hh831394.aspx:
"After a server has been added to the Server Manager server pool, service alerts about the Shell Hardware Detection service can be displayed if there are no users logged on to the managed server. This occurs because the Shell Hardware Detection service runs
only when users are logged on to the managed server, or connected to a Remote Desktop session on the managed server. To avoid seeing Shell Hardware Detection service alerts for this case, click
Services in the thumbnails for server groups, including the
All Servers group. In the Services Detail View dialog box, on the
Services drop-down list, clear the check box for Shell Hardware Detection, and then click
OK."
That confirms that it's okay for Shell Hardware Detection not to be running. However the suggested fix--removing it from 2012 alerting--does not keep it off my 2012E Health Report.
Mark Berry
MCB Systems

Details Desplay Dialog

Similar Messages

Maybe you are looking for