Showing posts with label sap netweaver. Show all posts
Showing posts with label sap netweaver. Show all posts

January 12, 2014

SAP NETWEAVER TUTOR FILES



SAP NETWEAVER TUTOR(SIMULATOR) FILES :-



Sap Tutor Player:-    Click Here



Please find the links for Netweaver sim files below....



LINK  BuildingWebServicesWithJavaPart2

LINK  BuildingWebServicesWithJavaPart3   

LINK  BuildingWebServicesWithJavaPart4 

LINK  Business Communication-Telephony Integration

LINK  Business Services-IntroductionToSAP Alert Management

LINK  Creating A Dynamic Form For Printing UsingThe Adobe Designer

LINK  Database Indexes And Table Buffer InTheJava Dictionary

LINK  Enabling SSL Support OnThe SAP WAS 6.20

LINK  Enabling SSL Support OnThe SAP WAS 6.20 CreatingThe SSLServer PSE

LINK  Enabling SSL Support OnThe SAP WAS 6.20 Creating The SSL Client PSEs

LINK  Enabling SSL Support On The SAP WAS 6.20 Configuring The Use Of SSL For User Authentication

LINK  Enabling SSL Support On The SAP WAS 6.20 Testing The Connections

LINK  Java Applications Link JDBC Data Sources 

LINK  Modify A DatabaseTable InThe Java Dictionary

LINK  Overview eBusiness Security-Identifying Users

LINK  Overview Of eBusiness Security-Authorizations And Network Security

LINK  Overview Of eBusiness Security-Establishing Obligation And Non-Repudiation Plus Auditing And Logging

LINK  Overview Of eBusiness Security-Establishing Trust Relationships

LINK  Overview Of eBusiness Security-Introduction To Basic Security Concepts

LINK  Portable Data Types In The Java Dictionary

LINK  SAP .Net Connector

LINK  SAP Web Application Server-J2EE Security

LINK  Security Provider Service

LINK  Shared Objects Basics For SAP Netweaver WAS 6.40

LINK  Single Sign-On To SAP Enterprise Portal Using SAP Passports

LINK  SQLJ In The Spot light

LINK  User Management in the Enterprise Portal User Interface

LINK  User Management in the SAP WAS 6.40 UME User Interface

LINK  XI 3.0-BPM Click-Through1

LINK  XI 3.0-BPM Click-Through2

LINK  NW DS-Define A DatbaseTable

LINK  NW GP-How to Create a Guided Procedure for Employee Leave Requests

LINK  NW GP-How To Use Exceptions in GP

LINK  NW GP-Overview End User Design time

LINK  NW-How To Create a Content Package Object

LINK  NW-How to Create a Process for Searching SAP Web Pagesusing Guided Procedures  

LINK  NW-PO Create using DS  




December 13, 2013

SAP BASIS INTERVIEW QUESTIONS & ANSWERS 6


SAP BASIS INTERVIEW QUESTIONS & ANSWERS :-


Support :-

Q) What are the steps involved in stopping SAP system?
A) Before stopping SAP system we need to check the status of the following
• Check if there are any logged on users. Use Transaction Code – SM04
• Check if there are any Background process is to define – SM36
• Check if there are any Background processing is going on. Use TC – SM37
• Check if there is any Batch input session. Use TC – SM35
• Check if there are any update processes running. Use TC – SM13

Client Copy :-

Q) Why do we need to perform a test run?
A) Test run determines which tables are to be changed.

Q) What is the amount of storage space a client will occupy?
A) client without application data needs approximately 150-200 MB of storage space in a DB

Q) Why do we need to do client copy?
A) To create new clients.

Q) Do we need to transport clients between systems (or) what is the procedure for copying clients between systems?
A) We no longer require to transport clients instead we make a remote client copy.

Q) Why should we not transport the client data?
A) this is explained with the help of a scenario. In target system, we have set up clients whose data must not be affected. The cross client data must not be imported into the system from outside, since the cross client data overwrites existing data so that customizing data of other clients in the target system no longer effects.

Q) what default user has all the authorizations?
A) SAP*. This is the reason for locking this user in different environments.

Spool :-

Q) How to identify how many spool work process are setup in a particular application server?
A) Trans-Code SM51 and select the application server.
   Go to SM50 and count the number of work process with SPO

Q) How many spool processes are configured in out entire SAP system?
A) SM66 and check for SPO work process. In select process by choosing Type = Spool and Status = Wait

Q) Can we change number of spool work process by operation mode switching?
A) No. Only background and dialog work process can be modified.

Q) How to identify how many spool servers are available in your SAP system?
A) SM51 or SM66 and check for application server with at least one spool workprocess.

Q) How to make setting for an individual SAP user so that an output request is not created immediately for a spool request?
A) SU3 go to Default tab and ensure that output immediately option is not checked.

Q) How to find which printer is defined at OS level of your server?
A) Go to start -> Settings -> Printers (Revisit)

Transport :-

Q) What is a transport group?
A) SAP systems that share a common transport directory tree form a transport group.

Q) What is transport domain controller?
A) R/3 system with the reference configuration is called as the transaction domain controller.

Q) What is transport domain?
A) All R/3 systems that are planned to manage centrally using TMS form a transport domain.

Q) What are the two editor modes in which we can configure the transport routes?
A)     1. Graphical Editor
         2. Hierarchical Editor   

Q) What are the various configuration methods available in STMS?
A)     1. Single system configuration
         2. Development and Production systems
         3. Three systems in a group

Q) What is a standard transport layer?
A) This describes the transport route that the data from the development systems follows.

Q) What is SAP transport layer?
A) It is a predefined transport layer for DEV classes of SAP standard objects

Q) What are the three approval steps you need to follow as a part of approval procedure in QAS?
A)     1. To be approved by system administrator
         2. To be approved by department
         3. To be approved by request owner

Q) What are the various qualifier option or what are the various import options?
A) There are six import options
    1. Leave transport request in queue for later import
    2. Import transport request again
    3. Overwrite originals
    4. Overwrite objects in unconfirmed repairs
    5. Ignore unpermitted transport type
    6. Ignore predecessor relations   


October 19, 2013

SAP NetWeaver 7.0 Dual Stack Refresh Procedure -8




SAP NetWeaver 7.0 Dual Stack Refresh Procedure -Part 8


 8.4 Reinstall Application Server

8.4.1 Uninstall Existing Dialog Instance 

 

 Back up the profiles of the existing instance.

Start sapinst (as root)

export DISPLAY=<IP address>:0.0

export SAPINST_JRE_HOME=/usr/lib64/jvm/java

cd /qbi2install/master/IM_LINUX_X86_64

./sapinst





 Remove the instance, but keep the OS users on the system.


 Uncheck the box for “Uninstall database (or parts of the database)” since we will be reinstalling later.




 8.4.2  Install Dialog Instance


Create symlinks in /sapmnt/SB1 for exe, profile, and global

ln -s /sb13/exe/nuc/linuxx86_64 exe
ln -s /sb13/profile
ln -s /sb13/global

Start sapinst (as root)

export DISPLAY=<IP address>:0.0

export SAPINST_JRE_HOME=/usr/lib64/jvm/java

cd /qbi2install/master/IM_LINUX_X86_64

./sapinst



 Choose the Custom option to customize the options before running the install.







 If this error appears, LDAP is not fully disabled.






Click Cancel. The saplocales package will have to be dealt with at a separate time if this message is still appearing.







Consider which of the items above should be selected, depending on where the kernel is coming from, the patch level, and if the link is set up properly as recommended at the beginning of the install above.




Error /db2/db2qbi/sqllib exists. Move to backup and retry.

Catalog database error. Shouldn’t need to run that. Hack keydb.xml and restart.


 Update the kernel.

Start instance.


 8.5 Close the system

Remove any transports that were created during the refresh. These cannot move to another system!

Update SCC4 appropriately again once all tasks are completed. Turn the system over to the GCOE.



 Appendix



END..............



SAP NetWeaver 7.0 Dual Stack Refresh Procedure -7




SAP NetWeaver 7.0 Dual Stack Refresh Procedure -Part 7


8.3.2  Java Stack

Remove any Wily configuration lines from the server node(s) via the configtool before working with the Java stack. Most likely, the Java stack will not start initially until the Wily configuration is removed anyway.

Run JSPM and ensure all packages are up to date








 Ensure all packages are up to the proper level. Apply any updates that are available. These were most likely missed while the system was outside of the production support path.

Apply any JSPM updates first, and restart JSPM before applying any further missing packages.

Following any JSPM updates, apply any kernel updates separately from any other packages.

Check the Key Storage service in the Visual Administrator. The entries should reflect the ABAP stack, and any other systems needing connections.

In most cases, the SAPLogonTicketKeypair certificate will need to be recreated. Use the DSA algorithm and change the expiration date to somewhere around 2037. Import the certificates if they have been previously exported. The private key will have a previous page extension.

 


Check the Security Provider service in the Visual Administrator. From the Runtime tab, select the Policy Configurations tab, and the Authentication tab. Entries for the “ticket” and “evaluate_assertion_ticket” may need to be updated following the refresh.


 Update the SLD configuration in the Visual Admin tool through the SLD Data Supplier service.



 
Update the settings under the JCo RFC Provider service in Visual Administrator.


 Update the settings for the FP_ICF_DATA* web services in the Destinations service in Visual Administrator


Verify the Licensing Adapter has the correct license installed. This is required for some functionality within Solution Manager, and the correct information must be reported to the various SLD systems as well as Solution Manager.



Double check the Java parameters via configtool

For BI system – check BI Diagnostics and Support Desk Tool (Note 937697) for Java validation
http://<server>:<port>/irj/servlet/prt/portal/prtroot/com.sap.ip.bi.supportdesk.default

During the SBI refresh, there was an issue where the BI Master system was not recognized. This appeared as an issue with the SBICLNT100 system object, however it turns out was an error in the UME configuration.


 From System Administration --> System Configuration, select UME Configuration and review all of the tabs. The error with SBI was on the User Mapping tab. Once this was modified to read SBICLNT100 instead of DB1CLNT100, the BI support desk tool was happy with the BI master system once again.

From the ABAP side, run the program RSPOR_SETUP from SE38. This will validate the portal configuration from the ABAP to the Java side.

If the BI support desk tool reports errors with the Webdynpro JCO destinations, log in to the Web Dynpro maintenance and open the Content Administrator



 Create or Maintain the connections as necessary.

Remove the Source System related System Objects in the same tree from the System Components that will be imported based on the export taken during the preparation steps. Be sure not to delete any of the portal content other than the system objects that establish connection to the other systems.

Import the exported system configuration including the system objects.


The EPA file exported during the presteps is in the /sapmnt/<SID>/global/pcd/Export directory. This file needs to be in /sapmnt/<SID>/global/pcd/Import. Once copied there, log in to the portal as J2EE_ADMIN and navigate to System Administration --> Transport --> Import







From the portal, log in as J2EE_ADMIN and navigate to System Administration --> System Configuration. In the System Landscape, expand the tree as shown in the screen capture below.


 Update the system object entries by changing any reference to the source system or source system connections to the target system or target system connections.

Update passwords in the Basis password store as appropriate depending on the user master data restored to the system being refreshed.

Redeploy SMD/Wily as necessary.




 Will update soon... Check next post...