Scribd
Upload
383 views12 pages

Mime Repository Tutorial PDF

This document provides steps to configure and run GUIXT scripts from the SAP MIME Repository. Key steps include: 1. Creating the proper folder structure in the MIME Repository and uploading required files like scripts, images, and a new guixt.ini file. 2. Replacing the local guixt.ini file to point to the centralized file in the MIME Repository. 3. Using VersionNumber in scripts to control downloading updates from the Repository. 4. Testing that the scripts run correctly from the Repository on login to SAP.

Uploaded by

Rahul Gaikwad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
383 views12 pages

Mime Repository Tutorial PDF

This document provides steps to configure and run GUIXT scripts from the SAP MIME Repository. Key steps include: 1. Creating the proper folder structure in the MIME Repository and uploading required files like scripts, images, and a new guixt.ini file. 2. Replacing the local guixt.ini file to point to the centralized file in the MIME Repository. 3. Using VersionNumber in scripts to control downloading updates from the Repository. 4. Testing that the scripts run correctly from the Repository on login to SAP.

Uploaded by

Rahul Gaikwad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

This tutorial will explain to you in detail what the steps are that you need to follow to run

your
scripts out of the SAP MIME Repository.

Before you start:

Please make sure that your GuiXT RFC User has the correct authorizations, as explained here:
http://synactive.com/docu_e/doc_rfc.html

Log on to SAP, and navigate to the ABAP Workbench (Transaction SE80)

Depending on your system settings, you may or may not see the option “MIME Repository” in the
Object Navigator.
If you do not see the see the option “MIME Repository” in the Object Navigator, click on
UtilitiesSettings

Click on the check box to activate the MIME Repository


In the Workbench, the Object Navigator should now show the MIME Repository. Click on it.

With the repositories expanded, navigate to SAPBCBSPSAP


Right click on the SAP Folder and choose CreateFolder

On the following screen, create a folder called “GUIXT”. Please note that this is just an example. In
practise, you would create the folder structure according to your own requirements.

Give the folder a logical description, and click on the save icon.

Assign the new MIME Repository that you are creating to a Development Package.
Create a new transport request for the MIME Repository that you just created.

Your structure should now look like this

Repeat the steps as described, to create a structure that looks as follows

Now that you have a directory structure in your MIME Repository, we can upload the script files.
Right click on the “Temp” folder, and choose “Import MIME Objects”
In the browse dialog that appears, navigate to the directory where you saved the sample scripts too,
and select the file “esession.txt”

In the following SAP Dialog, give your file a description, and click on the save icon.
Repeat these steps to upload the files “guixt.XXX.ini”, “images.txt” and
“SAPLSMTR_NAVIGATION.E0100.txt”

Your directory structure should now look like this

Now expand the images folder and upload the file “eric.jpg” into it, and then expand the inputscripts
folder and upload the file “launchtcode.txt” into it.

Your folder structure now looks like this.


Overview of the files in detail

guixt.ini – In this example, we want to store the guixt.ini in the MIME Repository so that all users
have the same ini file. It makes the management of the guixt.ini a lot easier.

To achieve this, we need to replace the local guixt.ini file on the user’s computer, with a new one,
that will point it to the ini file in the repository.

Navigate to your SAP installation directory, typically C:\Program Files\SAP\FrontEnd\SAPgui and


replace the guixt.ini file with the one that you downloaded.

What does the new ini file do?

IgnoreRegistry – forces it to ignore the registry entry for the GuiXT profile, and instead, uses the file
that you just replace.

StartMinimized – Starts the GuiXT window minimized

RFCUser – The username that will be used for RFC Calls to the System

RFCPassword – The password of the RFC User

SwitchTo – Tells GuiXT to change to a ini file that resides in the MIME repository that we just
created. The path is SAP/BC/BSP/SAP/GUIXT/Temp

Note that the name of the ini file is guixt.&database.ini When GuiXT looks for the ini file in the
repository, &database will be the name of your SAP System ID, e.g. DM0, so the file in the MIME
Repository will be called guixt.DM0.ini
esession.txt – The esession.txt file contains a command VersionNumber, which is used by GuiXT to
determine whether it should download a new script from the MIME Repository, or that it should
work with the cached version that was downloaded earlier.

Please refer to the command VersionNumber in the GuiXT Help documentation for more
information on using the command.

In this example, we start at Version 0001.

SAPLSMTR_NAVIGATION.E0100 – This is our screen script, and you should be familiar with GuiXT
Scripts at this point in time.

We are including a file called “images.txt” which is explained below, and then we add a pushbutton
to our screen, giving the user the option to execute a transaction or to stay on the screen. This will
be executed by running an input script.

We are also placing an image on the screen


images.txt – This file is an include file which is called by our GuiXT Screen Script. When accessing
content from the SAP Mime Repository, like html, images, css stylesheets, jscript etc. you will need
to use the OpenFile/CloseFile command for every file.

By adding it in an include file, you can use VersionNumber to determine whether an image, html
page etc. needs to be downloaded again. By default, GuiXT will download every file again.

launchtcode.txt – This file is our InputScript. We are simply going to show the user a message, when
he clicks on the pushbutton that we defined in our screen script. If the user clicks yes, we will
execute the transaction, if the user says no; we will remain on the easy access screen.
guixt.XXX.ini – This is our new guixt.ini file that we want to use. It is stored centrally, in the MIME
repository, and any changes to the ini file will be applied to all users using GuiXT. By doing it this way
you are able to easily mange any changes in your environment.

Please note, your file will be called guixt.XXX.ini where XXX = your SAP System ID.

Directory1 – This points to the MIME Repository that you created

Directory0 – This points to the local directory on your computer, where the scripts are
cached(downloaded) to. For this example, please make sure that you have created the folder
structure C:\GuiXT\Temp\cache

RfcCurrentClient – This is used to determine if the scripts are downloaded via the current client that
you are logged on to.

CacheEncryption – This is used to tell GuiXT whether the downloaded files should be encrypted or
not

Replication – This is used in conjunction with the VersionNumber command to allow you to use
version management on your scripts.
Log off of SAP and then log back in.

If you have followed these instructions correctly, your SAP EasyAccess screen should now look like
this.

Click on the “ABAP Workbench” button. GuiXT Should run the InputScript from the MIME
Repository.

You might also like