Your Android device may be reporting your recent location data and velocity (are you moving and if yes, how fast are you moving) back to Google servers. Head over to the Google Maps website to see your entire location history and you also have the option to export this data as KML files that can be viewed inside Google Earth or even Google Drive.
Android/smart phones has become part and parcel of our life.
Many times while installing apps/accessing websites we do give access to our
gmail accounts to many websites/apps in android and IOS which may be dangerous
and sometimes there might be some spam sent to/from your mail ids. Follow below procedure to revoke access to access.
Many of you might know this already, just wanted to share in
case any of you doesn’t know this. During refresh of ABAP system, we do have to
delete and recreate all strust certificates (system, ssl, nfe, snc etc) as part
of post refresh steps. Here is a small tip for that; we can take backup of all
folders in Strust. Below is the procedure for the same.
NOTE: Please read the full description of the procedure before
executing.
Export a PSE from STRUST
Select the PSE to be exported by
double-clicking
Attention when working on the PSE "SSL server Standard": this
PSE typically is a collective PSE, consisting of the default SSL Server
PSE (selected when doubleclicking the SSL Server PSE node in the
navigation tree on the left hand side) and the application server specific
PSEs (selected when doubleclicking the application server entries visible
when opening the SSL Server PSE node)
Verify, that the PSE to be exported is
displayed on the right hand side of transaction STRUST
Execute the menu item "PSE --> Save
as..."
From the appearing popup, select the entry
"File (Export PSE)"
Select a distinctive file name to save your
PSE file on your local workstation (PC)(*)
Press the green tick mark button (Input) or
the "Enter" key
Import a simple PSE into STRUST
Keep in mind, that the PSEs you overwrite need to
be backed up first if you plan to reuse them!
Doubleclick the icon "File" from the
navigation tree on the left hand side of transaction STRUST (**)
Select the PSE file to be imported from your
local workstation (PC) and open it (*)
Verify, that the PSE to be imported is
displayed on the right hand side of transaction STRUST
Execute the menu item "PSE --> Save
as..."
From the appearing popup, select the entry
representing the PSE type that you want to replace in your system:
For SSL Client PSEs, select the actual client identity to be replaced.
For WSS PSEs, select the actual PSE to be replaced. (not available in all
releases)
For SSF application PSEs, select the actual SSF application to be
replaced.
For SSL Server identities different from 'DFAULT', select the respective
server identity. (not available in all releases)
The procedure for the PSE "SSL server Standard" (DFAULT) is
described below
Press the green tick mark button (Input) or
the "Enter" key
Save the PSE by clicking the "Save"
button (diskette symbol)
Import the PSE "SSL Server Standard" into
STRUST
Keep in mind, that the PSEs you overwrite need to be backed up first if
you plan to reuse them! The PSE "SSL server Standard"
typically consists of multiple simple PSEs, which in the following are referred
to as 'SSL Server PSE'.
The full import procedure consists of three parts, which are shown
seperately for improved readability.
Preparation 1: Investigate the PSEs' SubjectNames
Make sure, that you have available all SSL
Server PSEs that you want to import
Open notepad or another editor of your choice
Repeat the following steps (4..8) for each SSL
Server PSE to be imported:
Doubleclick the icon "File" from the
navigation tree on the left hand side of transaction STRUST
Select the PSE file to be imported from your
workstation (PC) and open it (*)
From the right hand side, copy the
Distinguished Name (DN) of the PSE's own certificate
Paste the DN into your open notepad, using new
lines for the DN of each SSL Server PSE
Keep track, which DN refers to which PSE
(default, application server specific)
Preparation
2: Create a "dummy" PSE with the required SubjectNames
Attention - during these steps, an existing "SSL Server PSE"
will be replaced.
Click the node "SSL server Standard"
with the right mouse button
Select "Replace" and confirm that
you want to replace the current PSE with a new one
In the popup appearing, click the
"pen" button (Revise DN)
Replace the proposed DN with the DN of the
default SSL Server PSE (from the notepad)
If you have no default SSL Server PSE to import, the system proposed DN
will be OK.
Press the green tick mark button (Input) or
the "Enter" key
In the second popup, replace the DNs of the
application server specific PSEs with the respective DNs from your
notepad.
Assure, that you enter the correct DN to the
respective application server.
Press the green tick mark button (Input) or
the "Enter" key
Processing: The actual import
Repeat the following steps (2..7) for each SSL
Server PSE to be imported:
Doubleclick the icon "File" from the
navigation tree on the left hand side of transaction STRUST (**)
Select the PSE file to be imported from your
workstation (PC) and open it (*)
Execute the menu item "PSE --> Save
as..."
From the appearing popup, select the entry
"SSL Server PSE" (DFAULT)
Press the green tick mark button (Input) or
the "Enter" key
Confirm, that you want to replace the PSE of
the same DN
Save the PSE by clicking the "Save"
button (diskette symbol)
Remarks:
(*) Export and Import for the time being is only available to/from your
client workstation (PC).
(**) At this step, don't use the menu item "PSE --> Import"
for opening the PSE to be imported. This would lead to importing the wrong PSE
in the following steps.
OS/DB Migration - CMD. STR, TOC, EXT, R3load, DDLDBS.TPL and more
Tools - R3load, R3ldctl and R3szchk
R3ldctl creates STRucture files, TemPLate files by reading the technical settings for table/indexes in SAP data dictionary. R3szchk calculates the database size object sizes (EXTent files) for the target system based on the STR files created by R3ldctl. The EXT and STR files can be later split into smaller groups.
The most crucial tool R3load is responsible for unloading and loading data from the database. R3load uses the files created by R3ldctl and R3szchk and dumps the data into compressed binary format as .001, .002 .. files. It uses cmd files to achieve the task. If the cmd files are not present, it creates on its own.
Files
Command files*.cmd are created in the installation directory by R3load process if they are not already present. The command files contain path to database independent structure file (*.STR), database dependent template files (*.TPL), directory file (*.TOC) containing contents of dump files and directory containing data dump files.
DB independent structure files *.STR are created by R3ldctl. Together, these files describe every table and index recognized in the SAP data dictionary. The TABART (class) and TABKAT (category) are read from the technical settings of the tables/indexes defined in DD09L.
DB dependent template files DDL<DBS>.TPL contain the database specific syntax which are used for creating tables and indexes. By carefully adjusting the template file, certain import steps can be made to run fast and certain potential errors can be avoided.
In case of Oracle database, DDLORA.TPL contains the mapping of tablespaces with the table classes (TABART) and table category to extent definitions.
Extent parameter files *.EXT contain the initial sizes of the tables/indexes. The default values of the initial extents are 16KB for Oracle database.
During export, the initial extent sizes of large tables are limited to 1.7 GB. This may be small and is very likely to pose a problem during import. Find all occurrence of 1782579200 in EXT files and increase them to a large value (say 10GB 10000*1024*1024 = 10485760000)
Data dump files *.001, *.002 etc are the binary data files created by R3load while unloading the data from the database. These files are highly compressed. As a rule of thumb, the total size of the dump files may be about 10% of the database. It may be smaller if the tables are highly fragmented (for example as a result of data archiving). The dump files should not be edited.
Content directory files *.TOC contain the number of rows, which portion of the dump file holds which table and the timestamp of unload. You should never edit TOC files.
DB size template DBSIZE.TPL contains how the datafiles are layed out accross the sapdata file systems. The source database may have had datafiles arrnaged in disorderly fashion. Editing DBSIZE.TPL before tablespace creation helps you control how big and where the datafiles are created.
You have to ensure that you are not exceeding the FS size and the summations at the bottom of the file match. You can use the following command to do the check for each SAPDATA
R3SETUP Control files *.R3S orchestrate the export and import process. DBEXPORT.R3S controls export and DBMIG.R3S controls the database (only) migration.
There is no practical need to edit DBEXPORT.R3S, but DBMIG.R3S may need editing to insert exit routines.
Insert a line in the [EXE] section. If you find some activities in the import phase that can be performed before export completes, you may wish to run them while export is in progress to reduce downtime. Before the data loading is started by R3load, you should exit the import program. This can be achieved by adding an exit routine before DBR3LOADEXECDUMMY_IND_IND step starts.
Search for DBR3LOADEXECDUMMY_IND_IND in the DBMIG.R3S file. Just before that line, add <previous line number + 5>=EXITSAPNWNEBWIE_IND_IND to exit before the R3load process begins.
By adding the line you have specified another step to be executed by R3SETUP, but the definition of that step is not added yet.
Note that the steps in R3S file [EXAMPLELABEL_OS_DB] are sorted in alphabetical order. Therefore the new exit section should follow the alphabetical sequence.
EXITSAPNWNEWBIE... section is alphabetically ordered between EXITORA.. and EXITSTARTR3...
Tail for Win32 - the Windows version of the UNIX
'tail -f' command.
Tail for Win32 is used to monitor changes to files; displaying the changed
lines in realtime. This makes Tail ideal for watching log files.
Tail has a plugin architecture, which allows notifications to occur when
certain keywords are detected in monitored files. At the moment a MAPI plugin is
available, and work is in progress on an SMTP version.
Features
A few features of Tail:
Watch multiple files in realtime
Detect keyword matches, and highlight occurences
Send mail notifications on keyword matches by SMTP or MAPI
Plugin architecture allows you to write specialised handlers
Can process files of any size on all types of drive (local or
networked)
Standard forms also tend to have standard answers, such as a day of the week, or a month, so a drop-down box with pre-filled selections would be useful.
Assume that you have an input cell in which the user is supposed to enter a day of the week: Monday, Tuesday, Wednesday etc.
Enter the items for your drop-down list into a list on the worksheet, one item per cell. In this example, I'll assume that the month names start in cell G1 and extend down to G7, but normally you would put them outside of the readable area. In Excel terminology, a rectangular group of cells (such as G1 to G7) is called a range.
Select the cell that will contain the drop-down list. If you'd like more than one cell to display the same list, just select them all now rather than setting them up one at a time. (Click and drag to select a range; hold down Ctrl while you click to select non-adjacent cells.)
Select the cell where you want the drop-down list.
On the Data tab, in the Data Tools group, click Data Validation
Excel Data validation
In the Allow box, click List.
To specify the location of the list of valid entries, enter a reference to your list in the Source box in this case it's (=$G$1:$G$7) or click in the Source box and then select your list in the current spread sheet to populate the reference automatically.
Make sure that the In-cell dropdown check box is selected.
To specify whether the cell can be left blank, select or clear the Ignore blank check box.
You can go one stage further and display an input message when the cell is clicked.
Click the Error Alert tab, and make sure that the Show error alert after invalid data is entered check box is selected.
Select one of the following options for the Style box:
To display an information message that does not prevent entry of invalid data, click Information.
To display a warning message that does not prevent entry of invalid data, click Warning.
To prevent entry of invalid data, click Stop.
Type the title and text for the message (up to 225 characters).
Adding an input box to a drop down list in Excel
Note If you don't enter a title or text, the title defaults to "Microsoft Excel" and the message to: "The value you entered is not valid. A user has restricted values that can be entered into this cell."
After performing these steps, you'll see a drop-down arrow whenever any of the drop-down cells you just defined is "active" (that is, selected and awaiting input). Click the arrow and choose a month from the list. If you try to type something else into the cell, you'll get scolded in the form of a pop-up message.
If you'd like to provide your own wording for invalid entries, use the Error Alert tab in the Data Validation dialog box, and enter your own text in the 'Error message' field.
If your list of items is relatively small, you can enter the list items directly into the Source field. Just separate each list item with a comma.