B2B SOA Infra Tables

Please find the below tables to get the details of B2B instances from SOA INFRA dehydration store.

To get the Business Message details use the below table.
select * from b2b_business_message order by created desc;

To get the Wire Message details use the below table.
select * from b2b_wire_message;

To get the B2B EDI files from the storage.
select * from b2b_data_storage;

Advertisements

How to configure DB user accounts or passwords to never expires?

Most of the time we will encounter our database passwords used to expire after 180 days.

If we don’t have any security constraint then by using the below approach we can make them never expire.

Using profile, you can enforce a limit on resource utilization using resource limit parameters Also you can maintain database security by using password management feature.  Using the below query we can know ,which profile is used by each user account:

SQL> SELECT USERNAME, PROFILE FROM DBA_USERS;

sqlnoexpire.JPG

You can see all my SOA related user accounts are using “DEFAULT” profile.

To know all the details imposed on DEFAULT profile we have to use the below query.

SQL> select resource_name, limit from dba_profiles where profile=’DEFAULT’ and resource_type=’PASSWORD’;

RESOURCE_NAME                                            LIMIT
——————————–                           —————————————-
FAILED_LOGIN_ATTEMPTS                           10
PASSWORD_LIFE_TIME                                 180
PASSWORD_REUSE_TIME                             UNLIMITED
PASSWORD_REUSE_MAX                              UNLIMITED
PASSWORD_VERIFY_FUNCTION                 NULL
PASSWORD_LOCK_TIME                              1
PASSWORD_GRACE_TIME                            7

As shown above all our passwords will expire in 180 days. So for setting them to never expire we have use the below query.

SQL> alter profile DEFAULT limit PASSWORD_LIFE_TIME UNLIMITED;
Profile altered.
Now we can verify the seeing by running the below query.
SQL> select resource_name, limit from dba_profiles where profile=’DEFAULT’ and resource_type=’PASSWORD’;
sqlnoexpire1

Using SYS_retries property in ESS job definition- SOA Suite 12.2.1.0.0

In this post we will see how to use retry in ESS job definitions.

ESS provides the retry functionality through parameter SYS_retries and retry will happens when ever any system or other error occurs during the processing of ESS job request. By default, the value is set to 0 and it mean no retries will be done.

We can set the value of this property while submitting the request or while creating the job definition .

essretry1

After setting the property in Submit job definition , you will find the value like below.

essretry.JPG

Once after submitting the job we can see the no of retries in search job request window like below.

essretry2

B2B Listening Channel not Pulling Files from SFTP Folder After server downtime.

Issue –> B2B listening channel is not pulling the files from SFTP server after downtime.

Error –> Closing Client.

Cause –> B2B has automatically disabled the listening channel because it is not able to reconnect to the SFTP server.

If an SFTP server goes down, B2B makes 3 attempts to reconnect. If unsuccessful, the listening channel is disabled, and remains disabled even after the SFTP server is brought back up.

Solution –> 

The fix introduces new property b2b.listening_channels.continue_reconnect. When it is set to true (default is false) B2B will make continuous attempts to reconnect to the SFTP server.

Set the parameter using the following instructions:

1) Log on to the EM Console.
2) Go to SOA -> soa-infra (right-mouse click) -> SOA Administration -> B2B Server Properties -> More B2B Configuration Properties.
3) Click Operations tab and then addProperty.
4) Add the property as follows, including comments (optional):

key: b2b.listening_channels.continue_reconnect
value: true
comments: continuous SFTP server reconnection attempts

5) Click Invoke to set the property and Return.
6) Restart the SOA server to make B2B aware of the new property setting.

The sequence named [TEST_SEQ] is setup incorrectly. Its increment does not match its pre-allocation size.

If we have used Native sequencing in DB adapter and default increment size of  sequence does not match with DB adapter outbound connection pool then we will get the below error.

Error –>

The sequence named [TEST_SEQ] is setup incorrectly. Its increment does not match its pre-allocation size.

Solution –>

To resolve the issue we have to update the db adapter connection pool property “SequencePreAllocationSize” to sequence increment size, in our case it is 1.

Navigation –>

Navigate to Deployments->dbAdapter -> Click on Configuration’s Tab-> Click on your Outbound Connection Pools and then click on Connection Factory name -> Open Properties Tab

Change ‘sequencePreallocationSize’ property’s value to 1. Press ENTER to actually change the value. Click on Save button.

seqpreallocationsize

How to use Oracle Sequence in Database Adapter

In this post we will see how to use a oracle sequence in database adapter.

In some cases where you want to use the database adapter for inserts data in to a database table , you may want to use native sequencing to populate a primary key for some field.

I have created a below table and sequence in oracle database and i wanted use this table and sequence from SOA using database adapter.

CREATE TABLE TEST_SEQ_TAB (“ID” VARCHAR2(4000 BYTE) NOT NULL ENABLE,
“SOURCE” VARCHAR2(4000 BYTE) NOT NULL ENABLE,
“TARGET” VARCHAR2(4000 BYTE) NOT NULL ENABLE,
“REASON” CLOB,
“CREATE_TIME” TIMESTAMP (6) NOT NULL ENABLE,
“ATTRIBUTE1” VARCHAR2(250 BYTE),
“GUID” VARCHAR2(400 BYTE)
) ;

CREATE SEQUENCE TEST_SEQ INCREMENT BY 1 START WITH 1 NOMAXVALUE MINVALUE 1;

Now i have created a Database adapter to use this sequence.

For using this sequence we have to use “native sequencing” in DB adapter in primary key column.

testseq.JPG

You can see the primary key column in the table is linked with sequence in the mappings file .

seqprimarykey

testseqprimaryid.JPG