How to create user administrator in SUSE Linux Enterprise Server 11

This document has the purpose of describing how to configure the/etc/sudoers file in order to create users with root privileges.

If you need to create users that perform administrative tasks such start or stop some services (like ssh, ndsd, novell-vmc, novell-tomcat, network , etc), create regular users in the operating system, etc., you can accomplish with the aid of the /etc/sudoers file. That file contains the rules that the user must fulfill when using the sudo command to perform any administrative task.

Additionally, using <sudo> you can have the following advantages:

• Log every movement of the user (when using the sudo command)
• Restrict privileges

Procedure

The first thing to do is to use the visudo command in order to edit the/etc/sudoers file.

Note: You must run the visudo command as a root.

Once you enter the visudo command, you will see the content of the /etc/sudoers file.

As you can see most of the lines are commented, however the very important one is located under the User privilege specification.

This line root ALL=(ALL) ALL indicates that the user root can execute fromALL terminals, acting as a any user in the system and run ALL commands, in other words:

So if you have many system administrators and you want them to have root privileges (without actually using the root account) the only thing to do is to create as many entries in you /etc/sudoers file as administrators you have.

The following example add the bdiaz, dlugo, wvera, jsusunaga, etc accounts as system administrators with full root privileges:

On the contrary, if you need to prevent users to run certain commands, you can accomplish that using the special “!”

In this case we are preventing the users hvaquera, dmontiel and mcalvillo to run the /usr/bin/passwd, /bin/su and /bin/bash commands.

Conclusion

In order to add users into the /etc/sudoers file, the only thing to do is the following:

1. Find where it says “root ALL=(ALL) ALL”.
2. Type “o” to insert a new line below it.
3. Now type what you want to insert, eg “username ALL=(ALL) ALL”.
4. Hit esc to exit insert-mode.
5. Type “:wq!” to save and exit.

: # confirm passwd: password updated successfully localhost:~ #  exit  # logout

[2]	Try to switch from a user that was added above to root account.

localhost login:  suse # input user name password:  # password suse@localhost:~>  su -  # switch to root Password: # root password localhost:~ #  # just switched to root

[3]	Limit users who can execute su commmand. Th example below limits only "root" and "suse".

localhost:~ #  usermod -G wheel root  localhost:~ #  usermod -G wheel suse  localhost:~ #  vi /etc/pam.d/su # line 2: add auth required pam_wheel.so localhost:~ #  vi /etc/pam.d/su-l # line 2: add auth required pam_wheel.so

Step by Step for establishing RFC Connection between SAP-BW & Data Service

There are many descriptive documents, which talks about the RFC Connections between Data Services and BW, but I created this blog thinking that it will be much more helpful if the same is provided with appropriate screen shots.

I assume that before creating the RFC Connections, Data Services is installed and your BASIS has already imported SAP delivered Functions in the SAP BW Server. These functions are provided in the form of two transport files.

Following are the steps:

• Installing Functions on the SAP Server
• Creating RFC Connection in BO Data Services
• Creating RFC Connection in BW
• Install Authorizations

Overview with SAP Provided Diagram

This blog only will focus on the RFC Connection establishment between 2 servers.

Create RFC Connection in Data Services

1. Logon to Data Services Management Console

2. Go to SAP Connections - > RFC Server Interface

3. Click on RFC Service Interface

4. Select Tab RFC Server Interface Configuration

5. Select Add -> Provider necessary server parameters

    Note: In the parameters, the Program ID is the one which you need to provide. You

       can provide any name based on the naming convention your client prefers.

Ex: Program_ID: XX_YYYY

Click on Apply.

The program ID which you are going to define will be used in SAP BW Server ( or any other SAP Server).

6. Select Tab RFC Server Interface Status.

     Now you should be able to view the Server Interface name starts with the Program ID which you have provided.

    

    Select the check box for the Server Interface and click on Start. If all the parameters are appropriate then the server instance will start with a Green status.

With the above step you have created the RFC connection in Data Services. Now remember the Program_ID.  

In the next two steps I will talk about the RFC Connection in SAP BW. 

7. Now logon into the SAP BW.

    Use Transaction SM59 to create the RFC Connection.

Expand TCP/IP Connection, then Select Create.

The Program ID is the one which you have already created in DS Management Console.

Then once you click the Connection Test button you should see the message Connection Successful.

At this point your RFC Connection configuration is ready in both the systems ( DS & BW) and both the systems are ready for data transfer.

Guide to BODS - Repository Creation

Before launching the BODS application and starting actual BODS programming there are three mandatory activities which needs to completed they are –

1. Repository Creation
2. JobServer Configuration
3. Registering Repository with CMC.

Creating a Repository

The first and foremost activity one has to do after installing BODS and database is, creating a local repository. The below mentioned are the step by step process to create it-

1. Log on to your Database (SQL server 2008 Express in this case)

2. Create a new database (Example - DS_LOCAL_TEST in the figure 2.1).This database would be used for Local repository. (This article does not explain how to create database and tables outside BODS.)

Figure 2.1

3. Go to Start menu open SAP BusinessObjects Data Services 4.0 SP1 -> Data Services Repository Manager

4. A screen as shown in the below diagram (Figure 2.2) would popup. Enter the required parameters into the text boxes as stated below -

Figure 2.2

Below are the credentials one would need to fill in the Repository Manager.

Repository type – Local
Database Type – Microsoft SQL Server (in this case)
Database Sever name – This should be the machine/server name where the database is residing. If you have installed database in your local machine the machine name or machine IP has to be provided.
Windows authentication – DONOT check this option .It is always recommended to use password authentication.
User name – The login name of that is used to login to the above mentioned Database residing in the Database server mentioned.
Password - The same password used to login to the above mentioned Database residing in the Database server mentioned for the login id specified.

5. Click on create. The below displayed message could been seen(Figure 2.3), indicating “The local repository was created successfully”. (If you do not get the success message, then, any one of the credentials is incorrect like the database server name or the database name or user id password)

Figure 2.3

6. Close the window

Attaching repository to JobServer

The next step following the creation of repository is attaching the repository to a Jobserver. Only once it is attached to a job server, it can be opened using designer. Below are the steps to associate a repository to Jobserver-

1. Go to Start Menu -> SAP BusinessObjects Data Services 4.0 SP1->Data Services Server Manager. A screen as shown below would be displayed (Figure 2.4)–

Figure 2.4

2. Click on “Configuration Editor” and the screen Figure 2.5 would be displayed.

Figure 2.5

3. Next click on “Add” button and below screen would be displayed (Figure 2.6)

Figure 2.6

4. Click on “Add” button on the “Associated Repositories” label to enable the options in the “Repository Information” label.

5. Enter the credentials as shown in Figure 2.7 and click “OK”.

Figure 2.7

• Job Server name – Enter any name that you wish to assign for the Jobserver. Example in the above figure JobServer_Test in this case.
• Job Server port – By default it is 3500.If there occurs any error assigning the port as 3500, then try to increment the value like 3501 or 3502 or higher.
• Ignore the Check boxes and go to the label “Repository Information”.
• Database type – Select the database in which you created the repository. Microsoft SQL Server in this case.
• Database Server name – Name of the machine/server where database resides.
• Database name – Name of the database which was created for local repository.
• Username and Password – Same user name and password used to log in to SQL Server database in which the local repository database resides.
• Leave the “Default repository” check box as is.

6. Click on “Apply” and screen as shown in Figure 2.8 would be displayed.

Figure 2.8

7. The “Associated Repositories” box would be automatically populated with the concerned repository name.

8. Click on OK. Screen as in figure 2.9 can be seen.

Figure 2.9

9. Click on OK and we get a screen as shown in figure 2.10

Figure 2.10

10. Click "Close and Restart” to finish the JobServer configuration for the repository created. This will restart the BODS Engine and dialog box may be popped confirming it would restart the engine.

Please follow the Steps below:

Step I: First Create Database For e.g: LOCAL_REPO  (In My case Database is SQL SERVER 2008)

Step II: Then go to Data Services Repository Manager and Configure Data Base "LOCAL_REPO"as a Local Repository.

Step III:Then Login in Central Management Console (CMC) in IPS/BI Package.

Step IV: Go to Data Services and Click on Configure a new Data Services Repository

Step V: Now Put the Local Repository Information

Repository Name: Local_Repo

Data Base Type: Microsoft SQL Server

Data Base Server Name: BI4SERVER

Database Name: LOCAL_REPO

User Name: sa

Password:*********

After "Save" it was available in Data Services -> Repository Tab

Step VI: Then Save it and apply the Rights and Security on Local Repository and then Login With Data Services Designer (Using Administrator Credential, You Can create your own ID and apply the Rights & Security on Repository Level and Login)

Then Data Services Designer Window Will Open

Hope this will help you as well.

SAP BASIS & HANA Admin Online Live Interactive Demo On 9th April (Saturday) 8:30 P.M IST

SAP BASIS & HANA Admin Online Live Interactive Demo On 9th April (Saturday) 8:30 P.M IST



Please register for SAP BASIS & HANA Admin Online Live Demo Sessionon Apr 09, 2016 8:30 PM IST at :

https://attendee.gotowebinar.com/register/34746040495439876
Webinar ID: 121-751-139

Faculty: Over 14 years of SAP Experienced and Certified consultant in SAP BW , BOBJ,BODS & HANA

After registering, you will receive a confirmation email containing information about joining the webinar

For Course content click here : http://bit.ly/1Ux8kpq

"We are only expertise in SAP Basis & Hana Admin"
Team ErpKey
Skype Id: erpkey
Phone USA:+1-872-356-6665 || IND : +91 -9032881863
erpkey.com@gmail.com
info@erpkey.com
www.erpkey.com

Blog : https://key2sap.wordpress.com/

The "not quite" secure storage HANA Studio, Reconnect your Studio to HANA Servers!

For a while, I have been seeing people are having issues connecting their HANA Studio to the servers in CloudShare. You have setup your connection, all the icons are green

everything is working and looking good. Next day, you log back in to your account and suddenly it gets invalidated and turns red 

So this is the story, HANA Studio has a feature that basically stores all your connection credentials inside a storage. This storage is secured by a master password that the studio auto generates during the first time you enter your server credentials. You must be already familiar with the following dialog box:

This is when your credentials are "encrypted" inside the secure storage.

However, as much as the encryption goes, when they key got corrupted, you won't be able to decrypt the original information. And this is exactly what happens. For an unknown reason, the key sometimes got corrupted and your login got invalidated. You get "invalid user name / password". This is not because your backend profile was changed, you got a wrong user name / password, you didn't type it correctly, etc, it simply because your decrypt key got corrupted. The corrupted key makes the Studio logs you in with the incorrect information.

So here is the solution:

1. Open the Studio properties. File > Properties
2. On the Database User Logon, click on Secure Storage

3. Click change password. It might give you a pop up saying that decryption key is corrupted. Just say yes to it.

4. You got a new key and you're good to go !!

If it still fails, my colleague Ferry Lianto put together a nice document on how to delete your secure storage entirely and basically reset the whole Studio here.

UPDATE: You can go to Eclipse doc page here for more info about the secure storage itself. Maybe you can find what the root cause is? Easter egg challenge? 

Secure storage is locked

Ok, I just started using HANA studio with the openSAP course and I got the same thing. I think something happened to my default workspace and I couldn't seem to "Unlock" it or go to the properties page to change the database options (because nothing was configured yet).

What I did find that works (and this may be a poor work-around, but it seemed to do the trick for me) is to go Windows -> Open New Window. This created a second instance of HANA studio that didn't have the Locked issue.

Now when I look at the original window it looks like this:

Not sure if that is the correct way to do it or a long term solution. Maybe someone has a better solution. Seem to get this every time I open SAP HANA studio. Did I install it incorrectly?