현재 접속된 서버(AP)를 기준으로 URL이 생성되기 때문에 여러 AP를 도메인 등록 없이 운영하고 Load Balancer만 도메인 등록한 경우 문제가 있습니다. 이럴때는 cl_its_runtime=>get_url 메소드의 파라미터 in_host, in_port 를 L4에 맞게 추가로 주면 됩니다.
This Page is to discuss WD4A Design guidelines which can be used by beginner WD4A developer as a checklist to design quality WD4A applications. Please feel free to Add/Correct/Comment to below WD4A Design guidelines and help novice WD4A developer like me in designing quality WD4A applications.
Performance Optimization:
Use Range Supply Function to load part of data into context node for heavy table performance optimization.
Consider Delta Rendering Optimization while designing WD4A component.
Avoid complex and nested Layouts because it has a big impact on browser or client rendering performance.
Prefer the Row Layout to the Grid or Matrix Layout if horizontal alignment is not needed for better performance.
Number of visible rows in Table or ALV has an impact on performance.
Avoid writing much processing in WDDOMODIFYVIEW() method like initialization and all.
Don't use context of all WD4A component data. Use context for Screen In/Out data only.
Consider the Price Tag of UI elements when designing Web Dynpro Component.
UI Design Practice:
Use Flash Islands as add-on for Web DynPro and avoid using more than 3 Flash Islands on the screen.
Avoid Scrolling and make all information visible at a glance.
Prefer the Matrix Layout to the Grid Layout for Ease of use and consistent layout.
Avoid usage of TransparentContainers inside container UI elements.
Don't misuse Web Dynpro UI elements by setting improper property values.
Exchange default root UI element container with other container UI element to minimize container nesting levels.
Never Use Trays and Panel on same screen to avoid confusion for end users.
Never use a Section header without associating it with a TransparentContainer.
Use Access and Hot Keys for better accessibility.
Use Floorplan Manager for consistency across applications.
Componentization of Web DynPro component for reusability.
Better Development efficiency:
Use Floorplan Manager for the creation of new Web Dynpro ABAP applications to increase development efficiency.
Use Developer Defined Reusable Templates.
Miscellaneous:
Add URL Parameter "sap-wd-stableids=X" to achieve stable HTML IDs for Automated Tests.
Where-used list는 프로그램 분석할 때 참 유용한 기능입니다.
하지만 이 기능이 항상 완벽하지는 않습니다.
예를들어 어떤 스탠다드 함수를 대체하는 함수를 만들기 위해 어디서 사용되고 있는지 찾으려고 합니다.
Where-used list 를 돌려 보면 4개가 나왔다고 합시다. 하지만 이 4개가 전부라고 믿으면 안 됩니다.
전체 Where-used list를 모두 보관하고 있다면 용량이 너무 너무 크기 때문에
SAP에서는 기본적으로 아주 일부분만 보관하고 있습니다.
어떤식으로 활용하는지 분석하는 참고용으로 쓰라는 거죠.
전체를 다 만들면 DB에 10기가 정도 용량이 추가로 필요하다고 하네요.
(참고)
Yuri Software HEdit 3.0
The Hex Editor for Computer Professionals
Yuri Software HEdit 3.0 is a hexadecimal editor for binary files. It allows you to view and modify the contents of any file in either text or binary mode.
Yuri Software HEdit 3.0 offers a rich set of features:
Overwrite, insert, or delete bytes in the file.
Jump to any offset within the file.
Search for data patterns.
Search-and-replace.
Support for files >2 GB in size. Files of any size open instantaneously.
EBCDIC character display.
Integer and floating point numeric displays in little and big endians.