Abstract: Methods, apparatuses, devices, and substrates are described. Multiple layers of a substrate may be bonded using a laser beam that is rotating about an axis and while the substrate is laterally translated with respect to the laser beam. Further, a direction of the laser beam may be modified such that the laser beam is incident on a surface of a layer of the substrate at an acute angle with respect to the surface. In such cases, the respective layers of the substrate may be bonded by irradiating the surface with the rotating laser beam, thereby resulting in spiral-shaped bonding lines between the layers. The layers may be bonded when one of the layers is coupled with an element (e.g., a blocking element), and the acute angle of the laser beam may enable irradiation an area that is below the element while leaving the element unaffected by the laser beam.

Abstract: A system comprising a beam source (110) and an optical system (304) comprising first and second portions. The system further comprises first and second torque motors integrated into respective ones of the first and second portions, The first torque motor (420) is configured to rotate first portion (416) around a first axis (434). The second torque motor (426) is configured to rotate second portion (418) around a second axis (436). The first axis is perpendicular to the second axis.

Abstract: A system comprising a beam source (110) and an optical system (304) comprising first and second portions. The system further comprises first and second torque motors integrated into respective ones of the first and second portions, The first torque motor (420) is configured to rotate first portion (416) around a first axis (434). The second torque motor (426) is configured to rotate second portion (418) around a second axis (436). The first axis is perpendicular to the second axis.

Abstract: The present disclosure involves computer-implemented methods, software, and systems for supporting migration of unstructured data stored in enterprise content management systems. A computer-implemented method includes generating a search for content matching at least one content search rule, receiving a list of matched documents, wherein each document in the list of matched documents is associated with at least a source repository identifier and a unique document identifier, calculating a target repository identifier and at least one metadata change instruction for each unique document identifier using at least one migration rule, and modifying metadata for the document associated with each unique document identifier using the calculated at least one metadata change instruction.

Abstract: This disclosure provides various embodiments for archiving a business object. At least one particular business object is identified for archiving. The particular business object has associated data including type data corresponding to a business object type of the at least one particular business object, structured business data, and unstructured attachment data. At least one archive-type object is created corresponding to the particular business object by enriching the unstructured attachment data with type-specific metadata including data identifying at least one attribute of the business object type. The archive-type object is archive-system-independent. The at least one archive-type object is exported to at least one archiving system for storage in at least one memory device of the archiving system.

Abstract: This disclosure provides various embodiments for archiving a business object. At least one particular business object is identified for archiving. The particular business object has associated data including type data corresponding to a business object type of the at least one particular business object, structured business data, and unstructured attachment data. At least one archive-type object is created corresponding to the particular business object by enriching the unstructured attachment data with type-specific metadata including data identifying at least one attribute of the business object type. The archive-type object is archive-system-independent. The at least one archive-type object is exported to at least one archiving system for storage in at least one memory device of the archiving system.

Abstract: This disclosure provides various embodiments for archiving a business object. At least one particular business object is identified for archiving. The particular business object has associated data including type data corresponding to a business object type of the at least one particular business object, structured business data, and unstructured attachment data. At least one archive-type object is created corresponding to the particular business object by enriching the unstructured attachment data with type-specific metadata including data identifying at least one attribute of the business object type. The archive-type object is archive-system-independent. The at least one archive-type object is exported to at least one archiving system for storage in at least one memory device of the archiving system.

Abstract: The present disclosure involves computer-implemented methods, software, and systems for supporting migration of unstructured data stored in enterprise content management systems. A computer-implemented method includes generating a search for content matching at least one content search rule, receiving a list of matched documents, wherein each document in the list of matched documents is associated with at least a source repository identifier and a unique document identifier, calculating a target repository identifier and at least one metadata change instruction for each unique document identifier using at least one migration rule, and modifying metadata for the document associated with each unique document identifier using the calculated at least one metadata change instruction.

Abstract: This disclosure provides various embodiments for archiving a business object. At least one particular business object is identified for archiving. The particular business object has associated data including type data corresponding to a business object type of the at least one particular business object, structured business data, and unstructured attachment data. At least one archive-type object is created corresponding to the particular business object by enriching the unstructured attachment data with type-specific metadata including data identifying at least one attribute of the business object type. The archive-type object is archive-system-independent. The at least one archive-type object is exported to at least one archiving system for storage in at least one memory device of the archiving system.

Abstract: An integrated tracing and logging system for an enterprise network. One embodiment of the integrated logging and tracing system has an object-oriented architecture which includes a controller class with two sub-classes: a tracing sub-class and a logging sub-class. Instances of the tracing sub-class (tracing modules) are associated with specified program code regions of network applications. The tracing modules receive method calls from the network applications and process the method calls based on defined severity levels. Instances of the logging sub-class (logging modules) are associated with specified “categories” related to the enterprise network (e.g., system, database, etc). The logging modules receive and process method calls from network components associated with the categories. The integrated logging and tracing system allows the format of tracing and logging messages to be configured without recompiling any source code.

Abstract: An integrated tracing and logging system for an enterprise network. One embodiment of the integrated logging and tracing system has an object-oriented architecture which includes a controller class with two sub-classes: a tracing sub-class and a logging sub-class. Instances of the tracing sub-class (tracing modules) are associated with specified program code regions of network applications. The tracing modules receive method calls from the network applications and process the method calls based on defined severity levels. Instances of the logging sub-class (logging modules) are associated with specified “categories” related to the enterprise network (e.g., system, database, etc). The logging modules receive and process method calls from network components associated with the categories. The integrated logging and tracing system allows the format of tracing and logging messages to be configured without recompiling any source code.