This document provides instructions for installing the Asset Manager Web client on Linux. It describes downloading and configuring the Java Development Kit (JDK), configuring environment variables, installing Tomcat, configuring the JVM settings for Tomcat, installing the Asset Manager Web client files, and editing configuration files.
MySQL is an open-source relational database management system that was created to be very fast, reliable and easy to use. It discusses how to install and configure MySQL, describes basic data management commands like creating databases and tables, inserting and querying data. The document also covers advantages of MySQL like being multi-threaded and some disadvantages like not supporting stored procedures initially.
MySQL is a database management system where data is stored in tables which consist of columns and rows. The document provides instructions on installing MySQL on Linux using RPM files and setting the root password. It also describes some basic MySQL concepts like queries, creating/modifying tables, and joining tables.
The document describes steps to identify and repair a block corruption in an Oracle database:
1. Use RMAN's Data Recovery Advisor to list, analyze, and repair the corruption. It identified a corrupted block in the USERS tablespace datafile and recommended restoring it from backup with block media recovery.
2. Verify the corruption using DBVERIFY and validate the tablespace with RMAN backup. Both tools confirmed the single corrupted block.
3. Restore the corrupted block using RMAN block recovery to fix the issue, and revalidate that the tablespace is no longer corrupted.
This document discusses managing and processing processes in a system. It explains that every running program is a separate process with a unique process ID. It describes how to obtain information on running processes, start new processes, and end processes through various commands. It also covers job control in UNIX, allowing users to start, suspend, resume, and kill groups of processes associated with a job.
The document provides steps for installing MySQL on Windows, describes basic SQL commands like CREATE, SELECT, INSERT, UPDATE and DELETE. It also covers how to create databases and tables, grant user privileges, and includes examples of various SQL statements.
This document provides instructions on installing and configuring MySQL on Linux. It discusses downloading and installing the MySQL RPM package, setting the root password for security, starting the MySQL server and client, and running basic queries to test the installation. It also covers additional MySQL commands and configurations including user privileges, database design, backups, and restoring data.
This document provides instructions and examples for using the MySQL database system. It discusses MySQL concepts like database, tables, rows, and columns. It also demonstrates common SQL commands like CREATE, SELECT, INSERT, UPDATE, DROP. Examples show how to create databases and tables, insert and query data, use functions, conditions and wildcards. Script files demonstrate populating tables with sample data.
This document provides summaries of commands and configuration files for system administration tasks in Debian GNU/Linux. It covers topics such as system configuration files in /etc/, managing services and daemons, installing and managing packages with APT, managing packages with dpkg, configuring the network, setting up a web server and database, and getting help.
MySQL is an open-source relational database management system that was created to be very fast, reliable and easy to use. It discusses how to install and configure MySQL, describes basic data management commands like creating databases and tables, inserting and querying data. The document also covers advantages of MySQL like being multi-threaded and some disadvantages like not supporting stored procedures initially.
MySQL is a database management system where data is stored in tables which consist of columns and rows. The document provides instructions on installing MySQL on Linux using RPM files and setting the root password. It also describes some basic MySQL concepts like queries, creating/modifying tables, and joining tables.
The document describes steps to identify and repair a block corruption in an Oracle database:
1. Use RMAN's Data Recovery Advisor to list, analyze, and repair the corruption. It identified a corrupted block in the USERS tablespace datafile and recommended restoring it from backup with block media recovery.
2. Verify the corruption using DBVERIFY and validate the tablespace with RMAN backup. Both tools confirmed the single corrupted block.
3. Restore the corrupted block using RMAN block recovery to fix the issue, and revalidate that the tablespace is no longer corrupted.
This document discusses managing and processing processes in a system. It explains that every running program is a separate process with a unique process ID. It describes how to obtain information on running processes, start new processes, and end processes through various commands. It also covers job control in UNIX, allowing users to start, suspend, resume, and kill groups of processes associated with a job.
The document provides steps for installing MySQL on Windows, describes basic SQL commands like CREATE, SELECT, INSERT, UPDATE and DELETE. It also covers how to create databases and tables, grant user privileges, and includes examples of various SQL statements.
This document provides instructions on installing and configuring MySQL on Linux. It discusses downloading and installing the MySQL RPM package, setting the root password for security, starting the MySQL server and client, and running basic queries to test the installation. It also covers additional MySQL commands and configurations including user privileges, database design, backups, and restoring data.
This document provides instructions and examples for using the MySQL database system. It discusses MySQL concepts like database, tables, rows, and columns. It also demonstrates common SQL commands like CREATE, SELECT, INSERT, UPDATE, DROP. Examples show how to create databases and tables, insert and query data, use functions, conditions and wildcards. Script files demonstrate populating tables with sample data.
This document provides summaries of commands and configuration files for system administration tasks in Debian GNU/Linux. It covers topics such as system configuration files in /etc/, managing services and daemons, installing and managing packages with APT, managing packages with dpkg, configuring the network, setting up a web server and database, and getting help.
This document provides information about Linux commands and system administration. It begins with an overview of command syntax and usage. It then covers topics such as:
1. Commands for managing users and groups, processes, services, and networking. Specific commands discussed include w, id, ps, service, netstat, ifconfig.
2. Commands for working with files and directories, including cat, cp, mv, rm, find, locate, chmod.
3. Commands for viewing system information, such as uptime, free, df, du, uname.
4. Commands for managing the filesystem, permissions, and ownership of files using chown, chmod, umask, lsattr.
Using MySQL without Maatkit is like taking a photo without removing the camera's lens cap. Professional MySQL experts use this toolkit to help keep complex MySQL installations running smoothly and efficiently. This session will show you practical ways to use Maatkit every day.
Oracle applications 11i hot backup cloning with rapid cloneDeepti Singh
This document provides instructions for cloning an Oracle Applications 11i production system (PRODSERVER) to a test system (TESTSERVER) using Rapid Clone hot backup methodology. It outlines 7 stages: 1) prerequisites, 2) prepare source, 3) backup database, 4) copy apps files, 5) copy files to target, 6) configure target database, 7) configure target app tier. Key steps include applying patches, running preclone scripts, putting source database in backup mode, copying files, recovering database on target, and configuring target system.
Oracle applications 11i hot backup cloning with rapid cloneDeepti Singh
This document provides instructions for cloning an Oracle Applications 11i environment from a production system called PRODSERVER to a test system called TESTSERVER using Rapid Clone hot backup methodology. It involves 7 stages: 1) preparing the source system, 2) putting the database in backup mode and copying files, 3) copying application files, 4) copying files to the target, 5) configuring the target database, 6) configuring the target application tier, and 7) finishing tasks like updating profiles. Key steps include applying required patches, running preclone scripts, copying database and application files, recovering the database using the backup control file, and configuring the cloned application and database tiers.
Unix was first developed in 1969 by four programmers at Bell Labs. It was originally written in assembly language, then converted to C language in 1972-1973. Linux was created in 1991 by Linus Torvaldes as a kernel for his new operating system. Some key principles of Linux include treating everything as a file/directory, small single-purpose programs, ability to chain programs together, avoiding captive user interfaces, and storing all configuration data in text files.
Test: DML with NOLOGGING
NOLOGGING: Oracle will generate a minimal number of redo log entries in order to protect
the data dictionary, and the operation will probably run faster. Logging can be disabled at
the table level or the tablespace level.
1. The document provides examples of common Linux commands and their usage including tar, grep, find, ssh, sed, awk, vim, diff, sort, export, xargs, ls, ifconfig, uname, ps, free, top, df, kill, rm, cp, mv, cat, mount, chmod, chown, passwd, mkdir, ifconfig, uname, whereis, whatis, and locate.
2. Examples shown include how to create, extract, and view tar archives, search files with grep, find files, login remotely with ssh, edit files with vim, compare files with diff, view processes with ps, check storage usage with df, terminate processes with kill, manage files
The document discusses various topics related to Ruby on Rails including SQLite3-Ruby, ERb, and Rack. It provides an overview of how SQLite3-Ruby works with Rails as the default database adapter. It also discusses how to use SQLite3-Ruby outside of Rails, including establishing connections, making queries, and preparing statements. The document then summarizes how ERb works as the template language in Rails and how to use it outside Rails. It ends with a brief mention of Rack.
Unix was first developed in 1969 by four programmers at Bell Labs. It was initially written in assembly language, then converted to C language in 1972-1973. Linux was created in 1991 by Linus Torvaldes as the kernel of an open source operating system. Key principles of Linux include treating everything as a file/directory, using small single purpose programs, and storing all configuration data in text files. This document provides an overview of Linux commands and concepts related to users, groups, permissions, backups, processes and more.
The document discusses using SQLite as an embedded SQL database in Adobe AIR applications. SQLite allows storing data in a single file without a separate server. Key features covered include connecting to a SQLite database, executing SQL queries and statements, handling results, and using transactions. The document also provides examples of basic usage and links to additional SQLite resources.
Process Address Space: The way to create virtual address (page table) of user...Adrian Huang
Process Address Space: The way to create virtual address (page table) of userspace application.
Note: When you view the the slide deck via web browser, the screenshots may be blurred. You can download and view them offline (Screenshots are clear).
The document contains code snippets for configuring Spring Batch jobs and steps using Java configuration. It defines beans for a tasklet step, item readers, item processors, item writers, and more. It also includes code for configuring the database schema for metadata tables and running jobs from the command line.
This document summarizes PL/Java, which allows writing server-side functions in Java for PostgreSQL. It discusses how to define and deploy Java functions, configure PL/Java, handle parameters and return types, use JDBC from functions, and write triggers in Java. While compatible with Oracle's SQL/JRT standard, PL/Java has some limitations around memory usage and performance. It works best on Linux and is a stable option for adding Java code to PostgreSQL databases.
- perl provides many command line switches to control how a Perl script is executed or the input/output behavior. Some key switches include -n, -p, -l, -e, -M, -I, -V, and -E.
- Special variables like $. and eof can be used to access the current line number or detect the end of input files when iterating over lines.
- Modules can be loaded at startup using -M to enhance functionality, and %INC shows where modules were loaded from.
- Various quoting mechanisms like qq can be used to specify strings without interpolation.
This document discusses whether it is possible to edit an Oracle database dump file. It explains that dump files are binary files, so editing them in a text editor will corrupt the file format. While it may be possible under some circumstances, it is not reliable. The document recommends alternative approaches like using import to extract DDL statements into a text file, editing that, and running it as a SQL script instead of directly editing the binary dump file.
This document provides instructions for installing MapServer, PHP MapScript, and their dependencies on Linux. It describes downloading and compiling GD, PROJ.4, GEOS, GDAL, CURL, and PostGIS. It also explains recompiling PHP as a CGI to enable MapScript support. Finally, it details compiling MapServer and copying its executables, installing the PHP MapScript extension, and testing the MapServer and PHP MapScript installations.
How to make debian package from scratch (linux)Thierry Gayet
- The document discusses two methods for creating Debian packages: using dpkg-deb or dpkg-buildpackage.
- It provides step-by-step instructions for creating the package directory structure, metadata files, building and installing the package, and verifying installation.
- An alternative method using dh_make is also presented, which simplifies the process by automatically generating basic packaging files and directories.
Linux Commands mentioned here includes basic as well advanced linux commands which we use on a daily basis. These commands can also help you to crack interview.
The document provides instructions on installing Linux including collecting hardware information beforehand, preparing disk partitions, installing from a CD-ROM, installing additional packages, and basic Linux commands. It also discusses uninstalling software using the synaptic graphical tool or apt-get command line tool and describes common Linux commands like mkdir, cd, ls, cp and their usage.
This document provides information about Linux commands and system administration. It begins with an overview of command syntax and usage. It then covers topics such as:
1. Commands for managing users and groups, processes, services, and networking. Specific commands discussed include w, id, ps, service, netstat, ifconfig.
2. Commands for working with files and directories, including cat, cp, mv, rm, find, locate, chmod.
3. Commands for viewing system information, such as uptime, free, df, du, uname.
4. Commands for managing the filesystem, permissions, and ownership of files using chown, chmod, umask, lsattr.
Using MySQL without Maatkit is like taking a photo without removing the camera's lens cap. Professional MySQL experts use this toolkit to help keep complex MySQL installations running smoothly and efficiently. This session will show you practical ways to use Maatkit every day.
Oracle applications 11i hot backup cloning with rapid cloneDeepti Singh
This document provides instructions for cloning an Oracle Applications 11i production system (PRODSERVER) to a test system (TESTSERVER) using Rapid Clone hot backup methodology. It outlines 7 stages: 1) prerequisites, 2) prepare source, 3) backup database, 4) copy apps files, 5) copy files to target, 6) configure target database, 7) configure target app tier. Key steps include applying patches, running preclone scripts, putting source database in backup mode, copying files, recovering database on target, and configuring target system.
Oracle applications 11i hot backup cloning with rapid cloneDeepti Singh
This document provides instructions for cloning an Oracle Applications 11i environment from a production system called PRODSERVER to a test system called TESTSERVER using Rapid Clone hot backup methodology. It involves 7 stages: 1) preparing the source system, 2) putting the database in backup mode and copying files, 3) copying application files, 4) copying files to the target, 5) configuring the target database, 6) configuring the target application tier, and 7) finishing tasks like updating profiles. Key steps include applying required patches, running preclone scripts, copying database and application files, recovering the database using the backup control file, and configuring the cloned application and database tiers.
Unix was first developed in 1969 by four programmers at Bell Labs. It was originally written in assembly language, then converted to C language in 1972-1973. Linux was created in 1991 by Linus Torvaldes as a kernel for his new operating system. Some key principles of Linux include treating everything as a file/directory, small single-purpose programs, ability to chain programs together, avoiding captive user interfaces, and storing all configuration data in text files.
Test: DML with NOLOGGING
NOLOGGING: Oracle will generate a minimal number of redo log entries in order to protect
the data dictionary, and the operation will probably run faster. Logging can be disabled at
the table level or the tablespace level.
1. The document provides examples of common Linux commands and their usage including tar, grep, find, ssh, sed, awk, vim, diff, sort, export, xargs, ls, ifconfig, uname, ps, free, top, df, kill, rm, cp, mv, cat, mount, chmod, chown, passwd, mkdir, ifconfig, uname, whereis, whatis, and locate.
2. Examples shown include how to create, extract, and view tar archives, search files with grep, find files, login remotely with ssh, edit files with vim, compare files with diff, view processes with ps, check storage usage with df, terminate processes with kill, manage files
The document discusses various topics related to Ruby on Rails including SQLite3-Ruby, ERb, and Rack. It provides an overview of how SQLite3-Ruby works with Rails as the default database adapter. It also discusses how to use SQLite3-Ruby outside of Rails, including establishing connections, making queries, and preparing statements. The document then summarizes how ERb works as the template language in Rails and how to use it outside Rails. It ends with a brief mention of Rack.
Unix was first developed in 1969 by four programmers at Bell Labs. It was initially written in assembly language, then converted to C language in 1972-1973. Linux was created in 1991 by Linus Torvaldes as the kernel of an open source operating system. Key principles of Linux include treating everything as a file/directory, using small single purpose programs, and storing all configuration data in text files. This document provides an overview of Linux commands and concepts related to users, groups, permissions, backups, processes and more.
The document discusses using SQLite as an embedded SQL database in Adobe AIR applications. SQLite allows storing data in a single file without a separate server. Key features covered include connecting to a SQLite database, executing SQL queries and statements, handling results, and using transactions. The document also provides examples of basic usage and links to additional SQLite resources.
Process Address Space: The way to create virtual address (page table) of user...Adrian Huang
Process Address Space: The way to create virtual address (page table) of userspace application.
Note: When you view the the slide deck via web browser, the screenshots may be blurred. You can download and view them offline (Screenshots are clear).
The document contains code snippets for configuring Spring Batch jobs and steps using Java configuration. It defines beans for a tasklet step, item readers, item processors, item writers, and more. It also includes code for configuring the database schema for metadata tables and running jobs from the command line.
This document summarizes PL/Java, which allows writing server-side functions in Java for PostgreSQL. It discusses how to define and deploy Java functions, configure PL/Java, handle parameters and return types, use JDBC from functions, and write triggers in Java. While compatible with Oracle's SQL/JRT standard, PL/Java has some limitations around memory usage and performance. It works best on Linux and is a stable option for adding Java code to PostgreSQL databases.
- perl provides many command line switches to control how a Perl script is executed or the input/output behavior. Some key switches include -n, -p, -l, -e, -M, -I, -V, and -E.
- Special variables like $. and eof can be used to access the current line number or detect the end of input files when iterating over lines.
- Modules can be loaded at startup using -M to enhance functionality, and %INC shows where modules were loaded from.
- Various quoting mechanisms like qq can be used to specify strings without interpolation.
This document discusses whether it is possible to edit an Oracle database dump file. It explains that dump files are binary files, so editing them in a text editor will corrupt the file format. While it may be possible under some circumstances, it is not reliable. The document recommends alternative approaches like using import to extract DDL statements into a text file, editing that, and running it as a SQL script instead of directly editing the binary dump file.
This document provides instructions for installing MapServer, PHP MapScript, and their dependencies on Linux. It describes downloading and compiling GD, PROJ.4, GEOS, GDAL, CURL, and PostGIS. It also explains recompiling PHP as a CGI to enable MapScript support. Finally, it details compiling MapServer and copying its executables, installing the PHP MapScript extension, and testing the MapServer and PHP MapScript installations.
How to make debian package from scratch (linux)Thierry Gayet
- The document discusses two methods for creating Debian packages: using dpkg-deb or dpkg-buildpackage.
- It provides step-by-step instructions for creating the package directory structure, metadata files, building and installing the package, and verifying installation.
- An alternative method using dh_make is also presented, which simplifies the process by automatically generating basic packaging files and directories.
Linux Commands mentioned here includes basic as well advanced linux commands which we use on a daily basis. These commands can also help you to crack interview.
The document provides instructions on installing Linux including collecting hardware information beforehand, preparing disk partitions, installing from a CD-ROM, installing additional packages, and basic Linux commands. It also discusses uninstalling software using the synaptic graphical tool or apt-get command line tool and describes common Linux commands like mkdir, cd, ls, cp and their usage.
Cmake is a cross-platform build system generator that allows users to specify platform-independent build processes. It generates native makefiles and workspaces that can be used in the compiler IDE of choice. Cmake supports interactive and non-interactive modes to configure projects. It provides options to control code generation, set variables, and obtain help documentation for commands, modules, and other aspects of Cmake.
This document provides 50 examples of common Linux/Unix commands organized by command name. It begins with tar, grep, find, ssh, sed, awk, vim, diff, sort, and export examples. The document is intended as a quick reference for users to learn practical uses of fundamental Linux commands.
Ant is a Java library and command-line tool. Ant's mission is to drive processes described in build files as targets and extension points dependent upon each other. The main known usage of Ant is the build of Java applications. Ant supplies a number of built-in tasks allowing to compile, assemble, test and run Java applications. Ant can also be used effectively to build non Java applications, for instance C or C++ applications. More generally, Ant can be used to pilot any type of process which can be described in terms of targets and tasks.
Ant is written in Java. Users of Ant can develop their own "antlibs" containing Ant tasks and types, and are offered a large number of ready-made commercial or open-source "antlibs".
Ant is extremely flexible and does not impose coding conventions or directory layouts to the Java projects which adopt it as a build tool.
Software development projects looking for a solution combining build tool and dependency management can use Ant in combination with Ivy.
This document provides 50 examples of common Linux/Unix commands along with brief explanations and usage examples for each command. Some of the commands highlighted include tar, grep, find, ssh, sed, awk, vim, diff, sort, and ls. The examples cover a wide range of tasks from compressing/extracting files to searching/editing text to managing processes and permissions.
This document provides 50 examples of common Linux/Unix commands along with brief explanations and usage examples for each command. Some of the commands highlighted include tar, grep, find, ssh, sed, awk, vim, diff, sort, export, xargs, ls, pwd, cd, gzip, bzip2, unzip, shutdown, ftp, crontab, service, ps, top, df, kill, rm, cp, mv, cat, mount, chmod, chown, passwd, mkdir, ifconfig, and uname. The document is intended to give readers a quick start on frequently used commands.
The document discusses Autoconf and Automake, which are tools used to automatically generate Makefiles and configure scripts from simple descriptions of a project's build requirements. Autoconf generates configure scripts that can build software on different systems by checking for features like libraries, headers, and functions. Automake generates Makefiles from simple descriptions of build targets and dependencies in Makefile.am files. Together, these tools help developers more easily build portable software projects across a variety of Unix systems.
The document discusses batch file programming and various ways batch files can be used to create utilities, funny programs, and viruses that harm Windows machines. It provides examples of batch file code that can create undeleteable folders, continuously restart a system, corrupt files using for loops, and more. The document also covers basic batch file structure, operators, and ways to prevent virus attacks through batch files.
2005_Structures and functions of MakefileNakCheon Jung
The document discusses the structure and functions of the Linux kernel Makefile. It describes the top-level Makefile and how it builds the kernel image (vmlinux) and modules. It explains the roles of the .config file, architecture Makefiles, Script/Makefile and various Kbuild Makefiles. Key files like obj-y, obj-m and lib-y goals are identified. The document provides an overview of who develops different parts of the kernel build system and lists some important Kbuild files.
This document provides instructions for setting up the Berkeley parser on a Windows 7 64-bit system with a Java environment. It describes downloading the Java Development Kit (JDK), installing it, configuring environment variables, testing with a Hello World program, downloading the Berkeley parser files and an English grammar file, preparing a sample input file, and running the parser on the sample file to generate output. It also provides commands for training an English grammar on the WSJ corpus and testing the trained grammar.
This document discusses using Docker containers without Docker. It provides a Vagrantfile configuration to set up a virtual machine environment for experiments. The Vagrantfile configures a Ubuntu 18.04 virtual machine with Docker, Go, and other tools installed. The document then covers mounting namespaces and how to isolate the root filesystem of a process to emulate containers without Docker.
The document describes the standard Linux filesystem hierarchy, including the purpose and some examples of the contents of the top-level directories like /bin, /boot, /dev, /etc, /home, /lib, /media, /mnt, /opt, /proc, /root, /sbin, /usr, and /var. Many directories contain essential system files and programs needed for booting, administration, and operation of the system, while others provide variable storage and mounting points for removable devices. The filesystem layout separates core operating system, user, and variable files for security and manageability.
55 best linux tips, tricks and command linesArif Wahyudi
This document provides 55 tips, tricks, and Linux command lines contributed by readers. It begins with instructions for backing up and restoring Thunderbird emails manually by copying the profile folder. It then offers examples of using SSH to execute commands on remote Linux machines. The tips cover a wide range of Linux tasks like scheduling commands to run after reboot, commenting out config file lines, replacing newlines in files, checking installed shell types, using advanced LS commands, checking for rootkits, finding and replacing text with SED, backing up MySQL databases, and cutting/joining MP3 files.
How To Set a Vagrant Development SystemPaul Bearne
This document provides instructions on how to set up a Vagrant development environment. Vagrant allows developers to run development environments that match production by creating virtual machines. Key points:
- Vagrant uses VirtualBox to run virtual machines and configure project isolation and version control.
- The basic workflow involves initializing a Vagrantfile configuration, running "vagrant up" to launch the virtual machine, and "vagrant destroy" to wipe it out.
- Additional commands like "vagrant suspend" pause the virtual machine. The document demonstrates configuring ports, shared folders, and provisioning scripts.
- Benefits of Vagrant include no need to install web servers locally, matching production
Apache Ant is a Java-based build tool similar to make. It uses XML configuration files and allows tasks to be executed based on targets. Key features include being cross-platform, extensible via Java, and using XML for configuration. Ant provides tasks to compile code, create archives, execute tests and more.
A character device typically transfers data to and from a user appli.pdfaptind
A character device typically transfers data to and from a user application — they behave like
pipes or serial ports, instantly reading or writing the byte data in a character-by-character stream.
They provide the framework for many typical drivers, such as those that are required for
interfacing to serial communications, video capture, and audio devices. The main alternative to a
character device is a block device. Block devices behave in a similar fashion to regular files,
allowing a buffered array of cached data to be viewed or manipulated with operations such as
reads, writes, and seeks. Both device types can be accessed through device files that are attached
to the file system tree. For example, the program code that is presented in this article builds to
become a device /dev/ebbchar, which appears on your Linux system as follows:
molloyd@beaglebone:~/exploringBB/extras/kernel/ebbchar$ lsmod
Module Size Used by
ebbchar 2754 0
molloyd@beaglebone:~/exploringBB/extras/kernel/ebbchar$ ls -l /dev/ebb*
crw-rw-rwT 1 root root 240, 0 Apr 11 15:34 /dev/ebbchar
A straightforward character driver that can be used to pass information between a Linux user-
space program and a loadable kernel module (LKM), which is running in Linux kernel space. In
this example, a C user-space application sends a string to the LKM. The LKM then responds
with the message that was sent along with the number of letters that the sent message contains.
Later in the article I describe why we need to solve synchronization problems that arise with this
approach, and I provide a version of the program that uses mutex locks to provide a solution.
Before describing the source code for the driver in this article, there are a few concepts that need
to be discussed, such as device driver major and minor numbers, and the File Operations data
structure.
Major and Minor Numbers
Device drivers have an associated major and minor number. For example, /dev/ram0 and
/dev/null are associated with a driver with major number 1, and /dev/tty0 and /dev/ttyS0 are
associated with a driver with major number 4. The major number is used by the kernel to identify
the correct device driver when the device is accessed. The role of the minor number is device
dependent, and is handled internally within the driver. You can see the major/minor number pair
for each device if you perform a listing in the /dev directory. For example:
molloyd@beaglebone:/dev$ ls -l
crw-rw---T 1 root i2c 89, 0 Jan 1 2000 i2c-0
brw-rw---T 1 root disk 1, 0 Mar 1 20:46 ram0
brw-rw---T 1 root floppy 179, 0 Mar 1 20:46 mmcblk0
crw-rw-rw- 1 root root 1, 3 Mar 1 20:46 null
crw------- 1 root root 4, 0 Mar 1 20:46 tty0
crw-rw---T 1 root dialout 4, 64 Mar 1 20:46 ttyS0
…
Character devices are identified by a ‘c‘ in the first column of a listing, and block devices are
identified by a ‘b‘. The access permissions, owner, and group of the device is provided for each
device. Regular user accounts on the BeagleBone are members of some of these .
A character device typically transfers data to and from a user appli.pdfaptind
A character device typically transfers data to and from a user application — they behave like
pipes or serial ports, instantly reading or writing the byte data in a character-by-character stream.
They provide the framework for many typical drivers, such as those that are required for
interfacing to serial communications, video capture, and audio devices. The main alternative to a
character device is a block device. Block devices behave in a similar fashion to regular files,
allowing a buffered array of cached data to be viewed or manipulated with operations such as
reads, writes, and seeks. Both device types can be accessed through device files that are attached
to the file system tree. For example, the program code that is presented in this article builds to
become a device /dev/ebbchar, which appears on your Linux system as follows:
molloyd@beaglebone:~/exploringBB/extras/kernel/ebbchar$ lsmod
Module Size Used by
ebbchar 2754 0
molloyd@beaglebone:~/exploringBB/extras/kernel/ebbchar$ ls -l /dev/ebb*
crw-rw-rwT 1 root root 240, 0 Apr 11 15:34 /dev/ebbchar
A straightforward character driver that can be used to pass information between a Linux user-
space program and a loadable kernel module (LKM), which is running in Linux kernel space. In
this example, a C user-space application sends a string to the LKM. The LKM then responds
with the message that was sent along with the number of letters that the sent message contains.
Later in the article I describe why we need to solve synchronization problems that arise with this
approach, and I provide a version of the program that uses mutex locks to provide a solution.
Before describing the source code for the driver in this article, there are a few concepts that need
to be discussed, such as device driver major and minor numbers, and the File Operations data
structure.
Major and Minor Numbers
Device drivers have an associated major and minor number. For example, /dev/ram0 and
/dev/null are associated with a driver with major number 1, and /dev/tty0 and /dev/ttyS0 are
associated with a driver with major number 4. The major number is used by the kernel to identify
the correct device driver when the device is accessed. The role of the minor number is device
dependent, and is handled internally within the driver. You can see the major/minor number pair
for each device if you perform a listing in the /dev directory. For example:
molloyd@beaglebone:/dev$ ls -l
crw-rw---T 1 root i2c 89, 0 Jan 1 2000 i2c-0
brw-rw---T 1 root disk 1, 0 Mar 1 20:46 ram0
brw-rw---T 1 root floppy 179, 0 Mar 1 20:46 mmcblk0
crw-rw-rw- 1 root root 1, 3 Mar 1 20:46 null
crw------- 1 root root 4, 0 Mar 1 20:46 tty0
crw-rw---T 1 root dialout 4, 64 Mar 1 20:46 ttyS0
…
Character devices are identified by a ‘c‘ in the first column of a listing, and block devices are
identified by a ‘b‘. The access permissions, owner, and group of the device is provided for each
device. Regular user accounts on the BeagleBone are members of some of these .
Similar to Instalacion ambiente web am en linux red hat (20)
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Full-RAG: A modern architecture for hyper-personalizationZilliz
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
Infrastructure Challenges in Scaling RAG with Custom AI modelsZilliz
Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
1. PREREQUISITOS INSTALACIÓN DEL CLIENTE ASSET MANAGER WEB EN LINUX
Instalar JDK
Si debemos desinstalar una versión anterior de JDK comando para desinstalar java Yum remove
java-1.8.0-openjdk-1.8.0.65-3.b17.el7.x86_64 o eliminar la carpeta de instalación directamente
Descargamos el archivo de JDK correspondiente de la página de Oracle en este caso jdk-8u65-linux-
x64.tar.gz y lo copiamos en el directorio /usr/java
Descomprimimos el archivo tar.gz con el comando tar zxvf jdk-8u65-linux-x64.tar.gz
Ejecutamos el comando java – version para verificar que el JDK quedó instalado.
Configurar variable JAVA_HOME que apunte a la carpeta de instalación del JDK
Configurar la variable LD_LIBRARY_PATH=/home/bsmucmdb/Software/Asset/AssetManager/x64
en el bash_profile para que Asset Manager encuentre las librerías .so
Igualmente configuramos la variable ORACLE_HOME para que apunte a la carpeta de instalación
del cliente Oracle y la añadimos al PATH y al LD_LIBRARY_PATH
En la ruta /etc/ld.so.conf.d con usuario root creamos el archivo AssetManager-x86_64.conf lo
editamos colocando la misma ruta que en la variable LD_LIBRARY_PATH y ejecutamos el comando
ldconfig --verbose para actualizar la caché.
2. Configuración de JVM para Tomcat
Tenemos dos instalaciones de tomcat 1 para el Asset Manager y otra para el Asset Manager Web
Service.
Buscamos el archivo setenv.sh para editar los parámetros en este caso la ruta es /opt/tomcat-
Amwebservice/bin
3. Con comando vi setenv.sh editamos los parámetros de JVM Para Asset Manager Web así:
JAVA_OPTS="$JAVA_OPTS -Djava.awt.headless=true -Xms2048M -Xmx2048M -XX:+UseTLAB -
XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:SurvivorRatio=2 -XX:NewSize=256M -
XX:MaxNewSize=256m -XX:+UseBiasedLocking -server"
Copiar el archivo del servidor de la base de datos tnsnames.ora a la carpeta
$ORACLE_HOME/network/admin
INSTALACIÓN DEL CLIENTE ASSET MANAGER WEB EN LINUX
1. Copiamos instaladores a una carpeta dentro del sistema linux
4. 2. Descomprimimos el archivo .zip
3. Buscamos el archivo am-linux_UNICODE_9.60.13086_es.tgz lo dejamos fuera de la carpeta
Unix, en la carpeta de instalación.
4. Descomprimimos el archivo am-linux_UNICODE_9.60.13086_es.tgz
Vemos que el usuario con el que estamos renga los permisos para descomprimir, si no los tiene le
damos el comando: chmod 777 am-linux_UNICODE_9.60.13086_es.tgz y creamos un directorio con:
mkdir Asset.
A continuación pasamos el archivo am-linux_UNICODE_9.60.13086_es.tgz al directorio creado y le
damos el comando para descomprimir: tar xzvf am-linux_UNICODE_9.60.13086_es.tgz
5. 5. Editamos el archivo package.propierties que en esta instalación se encuentra en la ruta
/home/bsmucmdb/Software/Asset/AssetManager/websvc
Las propiedades que se encuentran en el archivo son las que vienen para una instalación
por defecto de Asset manager en Windows, para este caso cambiamos las propiedades
teniendo en cuenta que se está realizando una instalación en Linux Red Hat de 64 bits y
nos conectaremos a una base de datos Oracle 12C.
Con el comando Cat vemos las propiedades actuales del archivo así: cat package.properties
Con el comando: nano package.properties editamos las propiedades del archivo. Con las siguientes
propiedades:
6. cambios en package.Properties
AssetManager.UserLogin=Admin
AssetManager.UserPwd=
DB.Engine= Oracle
DB.library.path=/home/bsmucmdb/Software/Asset/AssetManager/x64/
libaamapi96.so
arch=64
#Library.Extension=so
#Library.Prefix=lib
DB.datasource=ASSET
DB.login=Admin
DB.password=c:/temp/secret1.txt
DB.owner=Admin
Y queda:
# Possible values and their translations for the path to the dll/so library
Library.Architecture.Path=${arch}=32:bin,${arch}=x86:bin,${arch}=x64:x64,${arch}=64:x64
# the extension of the library files - "dll" for Windows, "so" for *nix
# this is set by the deploy shell script and included here only for reference purposes
#Library.Extension=so
# the prefix prepended to the library name (empty for windows, lib for *nix).
# this is set by the deploy shell script and included here only for reference purposes
#Library.Prefix=lib
# property names that should not be reported as not being changed if they are not present in this file
# the properties would normally be properties that configure a certain version of Asset Manager for
# proper functioning rather than customer preferences. Property names must be surrounded by
colons (:)
internalProperties=
# location of the ant task jars needed for the deployment script. Only relevant in the
# primary properties file. If you specify this setting on the command line you must prefix the
7. # property name with "PRI." due to ant task library loading constraints.
# For example: -DPRI.ant.tasks.dir=lib
ant.tasks.dir=lib
# The name of the first file which stores the first part of PBKDF2 password. Make sure this file is
secure.
# Example: c:secret-sharesecret1.txt, or c:/secret-share/secret1.txt.
PBKDF2.Password.First.File=/home/bsmucmdb/Software/Asset/AssetManager/deploy/secret-
share/secret1.txt
# The name of the second file which stores the second part of PBKDF2 password. Make sure this file
is secure.
# Example: c:secret-sharesecret2.txt, or c:/secret-share/secret2.txt.
PBKDF2.Password.Second.File=/home/bsmucmdb/Software/Asset/AssetManager/deploy/secret-
share/secret2.txt
# Configurations for push adapter monitor
# Whether the monitor push adapter monitor is enabled
PushAdapter.Monitor.Enabled=false
# The UCMDB Server Host name
UCMDB.Server.Host=bpnt373bta.porvenir.net
# The UCMDB Server Port
UCMDB.Server.Port=8443
# The UCMDB Server log in User
UCMDB.Server.User=admin
# The UCMDB Server log in password
# The promptForPwd and encrypt parameters apply to this property,
# so this value may be overridden by a value input at deploy time and/or encrypted.
UCMDB.Server.Password=
8. 6. Editamos los parámetros del archivo package.Properties de Asset Manager Web Tier que
está en la ruta:
Archivo que por
defecto viene con los siguientes valores:
# The html string to display for counts that are not known (not yet counted and greater than the
# list paging size. Use {0} to place the paging size. The defaults display nothing.
# examples: "> {0}" results in "> 20", "{0}+" results in "20+", "??" results in "??"
Lists.Count.Unknown.Label=
# Open a new tab window for detail is editing status for linkedit, sublist, one2manylinkedit
Lists.DetailEditable.OpenNewTab=false
# Display a button that applies a filter without losing current selections in the list
Lists.Filter.Selections.Maintainable=false
# Default value of user preference for the maximum number of documents to show per page in a list
# The user can change this value themselves in the User Preferences screen, but this is the default.
Lists.Paging.Count.Maximum.Default=20
# List toolbar is to be displayed at the top or bottom. Recognized values are "both", "header" and
# "footer".
Lists.Toolbars.Display=both
# Default value of user preference to display the statistics combo box in lists.
# The user can change this value themselves in the User Preferences screen, but this is the default.
Lists.StatisticComboBox.Displayed=true
# Maximum number of documents to show child nodes in a tree list
Lists.Tree.ChildNode.Count.Maximum=200
# Remove the link name of remote field in list header
# Note: customized field label which end with brackets will be trimmed if this option is set to true,
# example: field label Asset(Computer) will be trimmed to Asset if this option is set to true.
Lists.RemoveLinkNameInHeader=false
# Comma-separated list of module to deactivate.
9. # example : Cable,HelpDesk,SAM
Navigation.DisabledModules=Cable
#==================================================================== ======
=========================
# This section defines the type of deployment and password handling
#
# These properties are read from the primary properties file only, the one specified on the
# command line. Properties from other sections are combined with the properties from the secondary
# properties file (specified by properties.file2) to create a combination ear if
# combination.ear=true in the primary properties file.
#==========================================================================
=========================
# path to the webtier war that is to be directly modified for a war deployment and/or
# copied and modified for use in an ear deployment
war=../webtier/AssetManager.war
# the type of deployment(s) to perform. War deployments alter the war specified above. Ear
# deployments create a copy of the above war for modification and inclusion in the ear specified
# below
war.deployment=true
ear.deployment=false
#==========================================================================
=========================
# This section defines the deployment information needed for creating the ears
# for weblogic and websphere deployments
#==========================================================================
=========================
# the ear that is to be created during an ear deployment
ear=../weblogic/AssetManager.ear
# whether the created ear is to contain both the webtier and webservice (true) or not (false)
combination.ear=true
10. # path to the webtier transformation properties file, used when combination.ear=true
properties.file2=../websvc/package.properties
# the context root to specify in the application.xml of the ear
context.root=AssetManager
# the application display name to specify in the application.xml of the ear
display.name=AssetManager
# the classpath to set in the manifest of the ear
manifest.classpath=
# additional files to place in the ear, separated by spaces
addl.files.root=..
addl.files=
# a space-delimited list of files to remove from the war that is placed within the ear - typically
# used for deployment on WebSphere 7
remove.war.files=
#==========================================================================
=========================
# This section contains Asset Manager settings that are less frequently modified
#==========================================================================
=========================
# Whether or not to show a confirmation screen before launching a script action
Actions.Scripts.Launch.Confirmation=false
# Whether to show budget alert messages. For CCS only.
BudgetAlert.Show=false
# Maximum number of items to display on a Business Home Page
BusinessHomePages.Items.Count.Maximum=6
# Maximum number of statistical breakdowns to display on a Business Home Page
BusinessHomePages.Statistics.Count.Maximum=10
# Currencies refresh interval in seconds (21600 seconds = 6 hours)
Cache.Currencies.Refresh.Interval=21600
# DbTables refresh interval in seconds (86400 seconds = 24 hours)
Cache.DbTables.Refresh.Interval=86400
11. # Opened ItemizedList values refresh interval in seconds (1200 seconds = 20 minutes)
Cache.OpenedItemizedLists.Refresh.Interval=1200
# The idle time of cache of opened ItemizedList values (unit:seconds)
Cache.OpenedItemizedLists.timeToIdleSeconds=1200
# The live time of cache of opened ItemizedList values (unit:seconds)
Cache.OpenedItemizedLists.timeToLiveSeconds=1200
# Workflow refresh interval in seconds (86400 seconds = 24 hours)
Cache.Workflows.Refresh.Interval=86400
# Max number of categories (e.g. bars) to display on a chart
Charts.Categories.Count.Maximum=20
# Colors to be used in bars or pie segments when generating charts
Charts.General.Colors=#4FC1E9;#AC92EC;#A0D468;#5D9CEC;#FC6E51;#FFCE54;#EC87C
0;#CCD1D9;#ED5565;#48CFAD;#F5F7FA;#656D78
# General statistics chart height (pixels)
Charts.General.Height=500
# General statistics chart width (pixels)
Charts.General.Width=625
# Statistics chart height in Dashboards (pixels)
Charts.Dashboards.Height=500
# Statistics chart width in Dashboards (pixels)
Charts.Dashboards.Width=625
# Statistics chart height in Statistics screens (pixels)
Charts.StatisticsScreens.Height=600
# Statistics chart width in Statistics screens (pixels)
Charts.StatisticsScreens.Width=750
# Statistics chart height in Wizards (pixels)
Charts.Wizards.Height=600
# Statistics chart width in Wizards (pixels)
Charts.Wizards.Width=750
# Max number of items per dashboard
Dashboards.Items.Count.Maximum=6
# Whether or not to globally permit documents to be opened within the browser window
12. Documents.Downloads.OpenInBrowser.AllowAll=false
# Which file types to allow being opened within the browser window. This value is only used
# if Documents.OpenInBrowser.AllowAll=false
Documents.Downloads.OpenInBrowser.AllowedFileTypes=txt|pdf|png|gif|jpg|jpeg
# Whether extjs charts will be enabled
Extjs.Charts.Enabled=true
# For color choosers, the color value is displayed in white for darker colors.
# This parameter determines the minimum darkness (0-1) at which the color value
# is displayed in white rather than black (0 is darkest, 1 is lightest).
Fields.ColorChooser.Font.White.ColorDarknessLevel=0.7
# Enable or disable full text search
FullTextSearch.Enabled=false
# Full text search server url
FullTextSearch.Server.URL=
# Show dashboard as welcome page
Welcome.ShowDashboard=false
#For canvas caption font
Workflows.Diagrams.Captions.Font=Arial
# Web service used for authentication
WebService.Service.Authentication=Core
# Dashboard service provider - Uses the amDashboardItem screen in the amDashboardItem table
WebService.Service.Dashboard=Administration
# Functional Domain Homepage object - Uses the amDashboardItem screen in the
amDashboardItem table
WebService.Object.Dashboard=Action
# DateAlarm service provider - Uses the amDateAlarm screen in the amDateAlarm table
WebService.Service.DateAlarm=Administration
# File upload/download service provider - Uses the amDocBlob screen in the amDocBlob table
WebService.Service.DocBlob=Administration
# Functional domain service provider - Uses the FuncDomainHomePage screen in the
amFuncDomain table
WebService.Service.FunctionalDomainHomePage=Core
13. # Functional Domain Homepage object - Uses the FuncDomainHomePage screen in the
amFuncDomain table
WebService.Object.FunctionalDomainHomePage=FuncDomDisplay
# Functional domain service provider - Uses the amFuncDomain screen in the amFuncDomain table
WebService.Service.FunctionalDomain=Administration
# Mail service provider - Uses the amMail screen in the amMail table
WebService.Service.Mail=Administration
# Profile service provider - Uses the amMasterProfile screen in the amMasterProfile table
WebService.Service.Profile=Administration
# Read mail wizard service provider - Uses the sysCoreReadMsg wizard
WebService.Service.ReadMailWizard=Core
# Reports service provider - Uses the amReports screen in the amReports table
WebService.Service.Reports=Administration
# Workflow schema service provider
WebService.Service.WorkflowSchema=Administration
# Location of Global HTML Help index page
globalHelpUrl=
# An alternate or custom theme. The standard theme is "am"
alternateTheme=am-default
# The layout type to list-detail(Horizontal or Vertical), The default value is Horizontal
ListDetail.layout=Horizontal
#==========================================================================
=========================
# This section defines debugging values that should only be modified at the request of technical
# support personnel. Changing these values could have severe impact on performance!
#==========================================================================
=========================
# Whether additional debugging info should be displayed on all pages
Debug.Display.State=false
14. # Whether the javascript source files should be the developer versions, where available
Debug.Javascript.Source=false
# Whether the constructed JSPs should be written to disk for debug purposes
Debug.JSP.WriteToDisk=false
# Path to which to write debugging JSPs, if enabled with Debug.JSP.WriteToDisk
Debug.JSP.Path=c:/jsp_out
#==========================================================================
=========================
# This section defines miscellaneous values that are needed for the deployment process and will
# likely never need to be edited.
# Note that passwords are not currently used by the webclient itself.
#==========================================================================
=========================
# message to display at the end of a war deployment
war.message=CAUTION: the parameters just set in the web.xml may be overridden in then
AssetManager.xml (or corresponding file) if you aren using tomcat as an application server!
# message to display at the end of a ear deployment
#ear.message=
# property names that should not be reported as not being changed if they are not present in this file
# the properties would normally be properties that configure a certain version of Asset Manager for
# proper functioning rather than customer preferences. Property names must be surrounded by
colons (:)
internalProperties=:PowerButtons.Unsupported:Wizards.CommandButtons.Disabled:Fields.All.Refr
eshOnChange:
# location of the ant task jars needed for the deployment script. Only relevant in the
# primary properties file. If you specify this setting on the command line you must prefix the
# property name with "PRI." For example: -DPRI.ant.tasks.dir=lib
ant.tasks.dir=lib
helpUrl=/AssetManagerDoc/index.htm
15. tenantUrl=/Administration/sysMTChangePrimaryTenant/wizard.jsf
# Shortcuts to New button
Accesskey.button.new=w
# Shortcuts to Delete button
Accesskey.button.delete=e
# Shortcuts to Cancel button
Accesskey.button.cancel=c
# Shortcuts to Modify button
Accesskey.button.modify=m
# Shortcuts to Duplicate button
Accesskey.button.duplicate=u
# Shortcuts to Save button
Accesskey.button.save=s
# Shortcuts to Yes button
Accesskey.button.yes=y
# If csrfguard filter is enabled. Enable it for security, disable it for performance.
org.owasp.csrfguard.Enabled=true
# The name of the first file which stores the first part of PBKDF2 password. Make sure this file is
secure.
# Example: c:secret-sharesecret1.txt, or c:/secret-share/secret1.txt.
PBKDF2.Password.First.File=
# The name of the second file which stores the second part of PBKDF2 password. Make sure this file
is secure.
# Example: c:secret-sharesecret2.txt, or c:/secret-share/secret2.txt.
PBKDF2.Password.Second.File=
# Delay mask display, default value is set to 3 seconds
maskMessageDelay=3
16. # set the session timeout (in minutes)
sessionTimeout=30
# set the maximum file size when uploading (k/m/g)
# eg: 1m/1g/100k
uploadMaxFileSize=1m
Editamos los valores que haya que editar:
WebService.EndPoint.RS=http://localhost:8080/AssetManagerWebService/rs
WebService.Version=Asset Manager 9.60
FullTextSearch.Enabled=true
FullTextSearch.Server.URL=http://<hostname>.<domain>:<AssetManagerWebServicePort>/quicks
earch/search
PBKDF2.Password.First.File=c:/temp/secret1.txt
Documents.Downloads.OpenInBrowser.AllowedFileTypes=txt|pdf|png|gif|jpg|jpeg|xls|xlsx
uploadMaxFileSize=20m
7. Editamos los valores del quicksearch.properties que se encuentra en la carpeta de de
instalación / websvc y que por defecto trae los siguientes valores:
[bsmucmdb@VPLX36BTA websvc]$ cat quicksearch.properties
# File for setting the <env-entry> values found in the webservice's web.xml
#
# NOTE: Whitespace is not trimmed from the values specified here. Do not add whitespace after
the
# equals sign (=) or at the end of the line if you do not intend the whitespace to be part of
# the value!
#
# Values not specified in this file or on the command line are not changed in the web.xml.
# Values specified in this file that have no value (eg. Name=) delete the env-entry-value of
# the corresponding env-entry in the web.xml
17. #=======================================================================
============================
# This section contains settings normally or frequently modified for a particular installation.
# Less frequently modified settings can be found further down in this file.
#=======================================================================
============================
# Asset Manager user login to be used by the WebService
AssetManager.UserLogin=Admin
# Asset Manager user password to be used by the WebService
AssetManager.UserPwd=
# The database engine that is used by this installation of Asset Manager. Can be one of Generic,
# MSSQL, Oracle or DB/2. If Generic is specified, the connection string used is that specified by
# the datasource (DB.datasource)
DB.engine=MSSQL
# The name of the database (e.g. 16.157.134.163/myAmDb or AMDemo96en)
DB.datasource=AMDemo96en
# The database engine login id
DB.login=itam
# The password corresponding to this login. The promptForPwd and encrypt parameters apply
to this
# property, so this value may be overridden by a value input at deploy time and/or encrypted.
DB.password=password
# Whether the DB cache is enabled
DB.cache.enabled=true
# The cache directory
DB.cache.dir=/tmp
# The cache size in KB (1048576 = 1GB)
DB.cache.size=1048576
# The owner of the DB
DB.owner=
# The path to the aamapiXX library. The variable @{Library.Architecture.Path}@ can be used
and will be
18. # automatically replaced by either "bin" or "x64" depending on which version of deployment is
# specified (32 bit or 64 bit). The AssetManager.InstallPath and Library.Extension parameters
# are passed in from the deployment script if they can be determined. If the path to the library
# is different from that found in the installation directory this setting MUST be modified (though
# if desired the @{Library.Architecture.Path}@ variable can still be used in the value.
# e.g. DB.library.path=/opt/lib/aamapiXX.so or DB.library.path=D:/libs/aamapiXX.dll
DB.library.path=${AssetManager.InstallPath}/@{Library.Architecture.Path}@/${Library.Prefix}aa
mapi${AssetManager.Version.Short}.${Library.Extension}
DB.expand.typedlinks=|amDocument|amWfWorkItem|amHistory|amReconcProposal
# The following two options are newly added and the useage should be documented
DB.auth.type=
DB.ws.address=
DB.passphrase=
# Set the fetching size for each query result
DB.FetchingArraySize=101
# Comma-separated list of Web Services to load on startup
# example : Head/Administration, Head/* , R50/*
WebService.LoadOnStartup=Head/*
# Full text record search dll path
AssetManager.ApiPath=${AssetManager.InstallPath}/@{Library.Architecture.Path}@/${Library.
Prefix}aamapi${AssetManager.Version.Short}.${Library.Extension}
# Full text record search index directory
AssetManager.RecordSearchIndexDir=c:/index
# Asset Manager service tag name for full text search
AssetManager.ServiceTag=Head
# Comma-separated list of modules to deactivate, example : Cable,HelpDesk,SAM
AssetManager.DisabledModules=Cable
# Full text indexing scheduler configuration
AssetManager.CronConfig=0 0 1 * * ?
19. # Max number of sections displayed in a single search result page
AssetManager.TopTreeNumber=10
# Max number of records under a single section
AssetManager.TreeRecordsNumber=100
# Max number of indexed results
AssetManager.IndexRsNumber=5000
# Lightweight SSO
LWSSO.domain=asiapacific.hpqcorp.net
LWSSO.userNameHeaderName=SM_USER
LWSSO.initString=lwsso-shared-encryption-key
#=======================================================================
============================
# This section defines the type of deployment and password handling
#
# These properties are read from the primary properties file only, the one specified on the
# command line. Properties from other sections are combined with the properties from the
secondary
# properties file (specified by properties.file2) to create a combination ear if
# combination.ear=true in the primary properties file.
#=======================================================================
============================
# path to the webservice war that is to be directly modified for a war deployment and/or
# copied and modified for use in an ear deployment
war=../websvc/quicksearch.war
# the type of deployment(s) to perform. War deployments alter the war specified above. Ear
# deployments create a copy of the above war for modification and inclusion in the ear specified
# below
war.deployment=true
ear.deployment=false
# whether to ask for passwords during the deployment process.
20. # setting to true will cause any value provided for a password field in this file or on the command
# line to be ignored, and you will be prompted to provide the value.
promptForPwd=true
#=======================================================================
============================
# This section defines the deployment information needed for creating the ears
# for weblogic and websphere deployments
#=======================================================================
============================
# the ear that is to be created during an ear deployment
ear=../weblogic/quicksearch.ear
# whether the created ear is to contain both the webtier and webservice (true) or not (false)
combination.ear=false
# path to the webtier transformation properties file, used when combination.ear=true
properties.file2=../webtier/package.properties
# the context root to specify in the application.xml of the ear
context.root=quicksearch
# the application display name to specify in the application.xml of the ear
display.name=QuickSearch
# the classpath to set in the manifest of the ear
manifest.classpath=/am-jni-${AssetManager.Version.Short}.jar /am-constants-
${AssetManager.Version.Short}.jar
# additional files to place in the ear, separated by spaces
addl.files.root=..
addl.files=@{Library.Architecture.Path}@/${Library.Prefix}aamapi${AssetManager.Version.Shor
t}.${Library.Extension}
@{Library.Architecture.Path}@/${Library.Prefix}amjni${AssetManager.Version.Short}.${Library.
Extension} websvc/lib/am-constants-${AssetManager.Version.Short}.jar websvc/lib/am-jni-
${AssetManager.Version.Short}.jar
21. #=======================================================================
============================
# This section contains Asset Manager settings that are less frequently modified
#=======================================================================
============================
# Asset Manager Jaas configuration file
acws.jaas.config.location=
#=======================================================================
============================
# This section defines miscellaneous values that are needed for the deployment process and will
# likely never need to be edited.
#=======================================================================
============================
# message to display at the end of a war deployment
war.message=CAUTION: the parameters just set in the web.xml may be overridden in then
AssetManagerWebService.xml (or corresponding file) if you aren using tomcat as an
application server!
# message to display at the end of a ear deployment
#ear.message=
# property names that specify passwords.
# these properties will be dealt with according to the other values in this section and if
# the promptForPwd property is set to true, a prompt for input of all of these fields will be
# generated. Property names must be surrounded by colons (:)
pwdEntries=:AssetManager.UserPwd:DB.password:
# DB name connection property to set, constructed from the other properties given above
dbNameProperty=AssetManager.DB.Name
# the connection string pattern for all but the Generic db engine
# possible components are listed in the first section of this file:
# @DB.cache.enabled@
# @DB.cache.dir@
# @DB.cache.size@
# @DB.datasource@
22. # @DB.engine@
# @DB.library.path@
# @DB.login@
# @DB.owner@
# @DB.password@
# @DB.ws.address@
# @DB.auth.type@
# @DB.passphrase@
dbConnectionPattern=[@DB.engine@;@DB.datasource@;@DB.auth.type@;@DB.ws.address
@;@DB.passphrase@;@DB.login@;@DB.password@;@DB.cache.enabled@;@DB.cache.dir
@;@DB.cache.size@;@DB.owner@AmApiDll='@DB.library.path@';ExpandTypedLinks='@DB.
expand.typedlinks@';FetchingArraySize=@DB.FetchingArraySize@]
# names of tokens in the connection pattern that are optional and must not be included if a value
# is not provided. Token names must be surrounded by colons (:)
dbConnectionPattern.optional.token=DB.owner
# string(s) to place before and/or after an optional parameter that is included in the connection
string
dbConnectionPattern.optional.token.prefix=Owner=
dbConnectionPattern.optional.token.suffix=;
# The short version number used in various files and settings
AssetManager.Version.Short=96
# The architecture of the deployment targetted. Valid value are:
# 32 or x86 for 32bit architecture, and
# 64 or x64 for 64bit architecture
arch=32
# Possible values and their translations for the path to the dll/so library
Library.Architecture.Path=${arch}=32:bin,${arch}=x86:bin,${arch}=x64:x64,${arch}=64:x64
# the extension of the library files - "dll" for Windows, "so" for Linux/Unix
# this is set by the deploy shell script and included here only for reference purposes
23. #Library.Extension=dll
# the prefix prepended to the library name (empty for windows, "lib" for Linux/Unix).
# this is set by the deploy shell script and included here only for reference purposes
Library.Prefix=
# property names that should not be reported as not being changed if they are not present in this
file
# the properties would normally be properties that configure a certain version of Asset Manager
for
# proper functioning rather than customer preferences. Property names must be surrounded by
colons (:)
internalProperties=
# location of the ant task jars needed for the deployment script. Only relevant in the
# primary properties file. If you specify this setting on the command line you must prefix the
# property name with "PRI." due to ant task library loading constraints.
# For example: -DPRI.ant.tasks.dir=lib
ant.tasks.dir=lib
# The name of the first file which stores the first part of PBKDF2 password. Make sure this file is
secure.
# Example: c:secret-sharesecret1.txt, or c:/secret-share/secret1.txt.
PBKDF2.Password.First.File=
# The name of the second file which stores the second part of PBKDF2 password. Make sure
this file is secure.
# Example: c:secret-sharesecret2.txt, or c:/secret-share/secret2.txt.
PBKDF2.Password.Second.File=
[bsmucmdb@VPLX36BTA websvc]$ nano quicksearch.properties
GNU nano 2.3.1 File: quicksearch.properties
Modified
# File for setting the <env-entry> values found in the webservice's web.xml
#
# NOTE: Whitespace is not trimmed from the values specified here. Do not add whitespace after
the
24. # equals sign (=) or at the end of the line if you do not intend the whitespace to be part of
# the value!
#
# Values not specified in this file or on the command line are not changed in the web.xml.
# Values specified in this file that have no value (eg. Name=) delete the env-entry-value of
# the corresponding env-entry in the web.xml
#=======================================================================
============================
# This section contains settings normally or frequently modified for a particular installation.
# Less frequently modified settings can be found further down in this file.
#=======================================================================
============================
# Asset Manager user login to be used by the WebService
AssetManager.UserLogin=Admin
# Asset Manager user password to be used by the WebService
AssetManager.UserPwd=
# The database engine that is used by this installation of Asset Manager. Can be one of Generic,
# MSSQL, Oracle or DB/2. If Generic is specified, the connection string used is that specified by
# the datasource (DB.datasource)
DB.engine=Oracle
# The name of the database (e.g. 16.157.134.163/myAmDb or AMDemo96en)
DB.datasource=AMDemo96en
# The database engine login id
DB.login=itam
# The password corresponding to this login. The promptForPwd and encrypt parameters apply
to this
# property, so this value may be overridden by a value input at deploy time and/or encrypted.
DB.password=password
# Whether the DB cache is enabled
DB.cache.enabled=true
25. # The cache directory
DB.cache.dir=/tmp
# The cache size in KB (1048576 = 1GB)
DB.cache.size=1048576
# The owner of the DB
DB.owner=
En este caso editamos algunos valores así:
LWSSO.domain=http://localhost:8080/AssetManagerWebService
PBKDF2.Password.Second.File=/home/bsmucmdb/Software/Asset/secret1.txt
PBKDF2.Password.First.File=/home/bsmucmdb/Software/Asset/secret1.txt
AssetManager.UserLogin=Admin
AssetManager.UserPwd=
DB.Engine= Oracle
DB.library.path=/home/bsmucmdb/Software/Asset/AssetManager/x64/
libaamapi96.so
arch=64
Library.Extension=so
Library.Prefix=lib
DB.datasource=ASSET
DB.login=Admin
DB.password=
DB.owner=Admin
# The UCMDB Server Host name
UCMDB.Server.Host=bpnt373bta.porvenir.net
# The UCMDB Server Port
UCMDB.Server.Port=8443
# The UCMDB Server log in User
UCMDB.Server.User=admin
# The UCMDB Server log in password
# The promptForPwd and encrypt parameters apply to this property,
# so this value may be overridden by a value input at deploy time and/or encrypted.
26. UCMDB.Server.Password=
8. Generamos los archivos de claves ejecutando el archivo generate-password.sh que se
encuentran en la ruta /AssetManager/deploy
Con comando sh ejecutamos el archivo.sh
Archivo tools.jar
/home/bsmucmdb/Software/jdk1.8.0_121/lib
Find type f –name tools.jar
Averiguamos cuál es la ruta de instalación de JDK con el comando: sudo update-alternatives --config
java y para saber la versión de java instalada usamos el comando: java –version
JAVA_HOME=/usr/java/jdk1.8.0_65
9. Editamos la variable bash de JAVA_HOME poniendo la ruta de instalación de JDK
Comando para editar la variable de entorno Bash: vi ~/.bash_profile
27. Editamos dando i
Salimos guardando cambios con :x
Aplicamos los cambios realizados con el comando source ~/.bash_profile
Vemos como quedó la variable de entorno con el comando echo $JAVA_HOME
Ahora añadimos la variable JAVA_HOME a las variables de entorno con el comando sudo vi
etc/environment
Y ejecutamos ./studio.sh para lanzar el programa
10. Hacemos el despliegue
sh deploy.sh -ws8
/home/bsmucmdb/Software/Asset/AssetManager/websvc/package.properties
11. Borrar archivo Catalina de tomcat: rm -rf Catalina
Y borrar los logs de tomcat en la ruta opt/tomcat/logs y ejecutamos rm -rf *
12. Copiar archivos.war al webapps del tomcat con el comando: cp <archive.war>
/opt/tomcat/webapps
28. Y verificamos así:
13. Subimos servicios del tomcat ejecutando los archivos catalina.sh de cada una de las dos
instancias instaladas una para Asset Manager Web Tier y otra para Asset Manager web
Service