Jobs at Mustapharaj Sdn Bhd on. Business improvement solutions. To process business transactions like accounts payable and receivable. View GHANSHAM SHARMA’S. • Handled accounts payable and accounts receivable. • Managing Office and Handling all the payments& Receipt in accounting software.

Success Stories ADVANCE - JAVA I. Introduction 2.

Jdbc Architecture 3. Types of Drivers 4. ResultSet 1.Read Only ResultSet 2.Updatable ResultSet 3.Forward Only ResultSet 4.Scrollable ResultSet 6.

PreparedStatement 7. Connection Modes 8. Batch Updations 10. CallableStatement 11. BLOB & CLOB II.SERVLETS 1.

Introduction 2. Web application Architecture 3. Http Protocol & Http Methods 4. Web Server & Web Container 5. Servlet Interface 6. GenericServlet 7. HttpServlet 8.

Servlet Life Cycle 9. ServletConfig 10. ServletContext 11.

Servlet Communication 1. Servlet-Browser communication 1. SendRedirect 2.

Web-component Communication 1. Include 3.Servlet-Applet Communication 12. Session Tracking Mechanisms 1. HttpSession 2. URL-Rewriting 4. Hidden-Form Fields 13.Filters & Wrappers 14.Listeners 15.Web-Security III.JSP 1.

Introduction 2. Jsp LifeCycle 3. Jsp Implicit Objects & Scopes 4.

Jsp Directives 1.page 2.include 3.taglib 5. Jsp Scripting Elements 1.declaratives 2.scriptlets 3.expressions 6. Jsp Actions 1.Standard Actions 1. UseBean tag 2. SetProperty tag 3.

GetProperty tag 4. Include tag 5. Forward tag 6. Plug-in tag 8. Params tag 9. Fallback tag 10. Directives tag 11.

Scriptlet tag 12. expression tag 2.Custom Actions 1. Classic Tags 2. Simple Tags 7.

JSTL & Tag Library IV. Oracle Copyright @ durgasoft. Ali Unal Kuran Meali Pdf Indirme. com.

Introduction Landscape data and landscape descriptions are the basis for business processes and ALM processes alike.Landscape data is gathered by the SLD and retrieved by the LMDB as a basis of the landscape descriptions in the SAP Solution Manager 7.1. So the LMDB will not work without an SLD – even the software catalog and CIM model /CIM / CR Content) are read from the SLD. There are some updates to topology-recommendations if you use the LMDB. This blog gives an overview of what to take care of when connecting SLD and LMDB. Hi Wolf, Thank you for the information.

We’re in the process of defining our SLD topology and want to get it set up correctlty now to avoid issues down the road. Without going in to too much detail about our system landscape, is it possible to have two LMBD connect to two SLD? From the section above Using More than 1 SLD Connected to 1 LMDB we are wondering if we can (1) connect our development/qa Solution Manager to our non-prod SLD and our production SLD? And (2) connect our production Solution Manager to our non-prod SLD and our production SLD? The two SLD would never sync/share data.

Thanks, Shawn. Dear Shawn, Not having a complete picture, I understand your setup as follows: • SLD (DEV/QA) connected to LMDB (DEV/QA) and LMDB (PRD) • SLD (PRD) connected to LMDB (DEV/QA) and LMDB (PRD) If there is no overlap in SLD data (apart from CR content, which is used from one SLD only if an LMDB has more than one SLD connected), you can use multiple SLD systems as source for the LMDB. I recommend using such a setup only if absolutely necessary, since switching technical systems data suppliers to a different SLD might cause problems I usually recommend keeping things as simple as possible.

One way to achieve a simpler picture, you could forward information between SLD systems and connect just one SLD to each LMDB. Please make sure to follow all requirements in the blog as well I hope that helps, Best Regards, Wolf Hengevoss SAP AG. Hi Wolf, Very informative blog. But I still have a question when we have 3 individual PI local SLD’s running on DEV/QA/PRD and 1 LMDB in the landscape. Also planning to setup one central SLD. *All these 3 SLD’s talk to each other and exchange data – for example if we have to create transport group for source and target business systems we will have to export/import the systems into each other SLD’s. 1) Is it fine if we Export LD data of DEV, QA and Import into PI PRD SLD and then do a full content synch with central SLD and further to LMDB.

But the questions is – it will also bring unwanted SCV’s of some development stuff into production? Alternatively doing Bridge forward will not totally bring PI associations which is again another issue. 2) Or can I connect individual SLD’s directly to central SLD using uni direct content sync and from there further to LMDB.

I’m not sure about this though it is technically possible, SAP states about the unique path principle. In this case, all 3 SLD’s will be exchange data with other which is violation right? Any input is highly appreciated.

Dear These are my thoughts: • If you are using DEV/QA/PRD SLD system, you cannot use full automatic content sync – this mechanism would immediately transport all changes so that there would be no difference between the connected SLDs as you already assume – only using exports you will have the control over the change process (see ) • You’re right, data of the same system/SCV/etc. May not go into one (e.g. The central) SLD via 2 different paths. Especially, merging two or more source SLDs into a target SLD via full automatic sync is not a supported scenario because the unique path principle cannot be fulfilled for SAP CR content. (The sync with more than 1 SLD into the LMDB is possible, because the LMDB filters the CR Content using only one SLD as CR source – this feature is not available in the SLD.) Best Regards, Wolf Hengevoss SAP SE.